A structured collection of official documentation, handbooks, style guides, references, and curated insights from the Ruby on Rails, Hotwire, and Kamal ecosystems — plus community style guides from RuboCop. All official sources are aggregated as git submodules for local reference. Curated insights from blogs, books, talks, and courses complement the official documentation.
Useful as an input source of knowledge for AI coding agents (e.g. Claude Code, Agent OS), food for your Second Brain, or just for offline access.
- Comprehensive: Combines official documentation, handbooks, style guides, and curated insights in one place.
- Structured: Clear separation between official references and manually curated insights.
- Updatable: Git submodules allow for easy updates from official sources while maintaining attribution.
- Agent-Friendly: Organized structure and unified index make it easy for AI agents to consume and reference knowledge.
├── .git-submodules/ # Upstream git submodules (auto-managed, not materialized in sparse checkout)
├── insights/ # Curated knowledge from blogs, books, talks (manually authored)
│ ├── 37signals/ # Insights from 37signals blogs, books, talks, podcasts, etc.
│ ├── architecture/ # Cross-cutting architecture topics
│ ├── deployment/ # Deployment and operations
│ ├── hotwire/ # Cross-project Hotwire topics
│ ├── kamal/ # Kamal-specific insights
│ ├── performance/ # Performance optimization
│ ├── rails/ # Rails-specific insights
│ ├── stimulus/ # Stimulus-specific insights
│ ├── testing/ # Testing strategies & patterns
│ └── turbo/ # Turbo-specific insights
│
├── references/ # Official docs (auto-extracted from .git-submodules/)
│ ├── hotwire-native/
│ │ ├── overview/ # How it works, navigation, path config, bridge components, native screens
│ │ └── reference/ # Bridge installation, navigation, path config, bridge components
│ ├── kamal/ # Official Kamal documentation (deployment, configuration, CLI reference, etc.)
│ ├── rails/
│ │ └── guides/ # Official Rails guides (models, views, controllers, configuration, testing, etc.)
│ ├── stimulus/
│ │ ├── handbook/ # Origin, introduction, hello stimulus, building, resilience, state, external resources, installing
│ │ └── reference/ # Actions, controllers, CSS classes, lifecycle, outlets, targets, TypeScript, values
│ ├── strada/
│ │ ├── handbook/ # Introduction, how it works, web, iOS, Android, installing
│ │ └── reference/ # Attributes, components, elements
│ └── turbo/
│ ├── handbook/ # Introduction, drive, page refreshes, frames, streams, native, building, installing
│ └── reference/ # Attributes, drive, events, frames, streams
│
├── style-guide/ # Community conventions (auto-extracted)
├── index.yml # Unified index across all sections
├── Makefile
└── README.md
Stored as git submodules under .git-submodules/ to keep the official source repositories separate from the extracted references and insights. Each submodule points to an official upstream repository, allowing for easy updates and attribution.
| Submodule | Source |
|---|---|
rails |
rails/rails |
hotwire-native-site |
hotwired/hotwire-native-site |
stimulus-site |
hotwired/stimulus-site |
turbo-site |
hotwired/turbo-site |
strada-site |
hotwired/strada-site |
kamal-site |
basecamp/kamal-site |
ruby-style-guide |
rubocop/ruby-style-guide |
rails-style-guide |
rubocop/rails-style-guide |
rspec-style-guide |
rubocop/rspec-style-guide |
minitest-style-guide |
rubocop/minitest-style-guide |
capybara-style-guide |
rubocop/capybara-style-guide |
packaging-style-guide |
rubocop/packaging-style-guide |
Running make references extracts handbook, reference, and overview documentation from each submodule into the references/ directory.
The insights/ directory contains curated knowledge extracted from blogs, books, talks, podcasts, and courses. Unlike references/, this content is manually authored and committed directly.
Each insight file should use YAML frontmatter for metadata. To add a new insight, copy insights/_template.md into the appropriate subdirectory.
Running make style-guide extracts community style guides from RuboCop into the style-guide/ directory.
git clone <this-repo>
make # Initialize and fetch all submodules, then extract references and style guidesmake help # Show all available commands
make fetch # Fetch updates for all submodules
make pull # Pull latest changes for all submodules
make references # Copy documentation from submodules into references/
make style-guide # Copy style guides from submodules into style-guide/
make clean # Remove extracted references/ and style-guide/ directoriesIf you want to include this repository as a submodule in your own project without recursively cloning all the source repos in .git-submodules/, use a sparse checkout to include only the extracted references/, insights/, and style-guide/ directories.
git submodule add https://github.com/romansklenar/rails-codex <path>By default, git submodule add does not recursively initialize nested submodules, so the repos inside .git-submodules/ won't be cloned. Just make sure you never run git submodule update --init --recursive on this submodule — use the non-recursive form instead:
# Suggestion: use .git-submodules as path and then symlink directories where needed
git submodule update --init <path>To skip checking out the .git-submodules/ directory entirely (saving disk space and avoiding empty submodule directories):
cd <path>
git sparse-checkout init --cone
git sparse-checkout set references insights style-guideThis tells git to only materialize the references/, insights/, and style-guide/ directories (plus root files like README.md and index.yml). The .git-submodules/ directory won't appear in your working tree at all.
git submodule update --remote <path>