Rails Inside is a small editorial journal for senior Ruby on Rails developers. Three long-form pieces, no marketing language, no SaaS pitch. Code blocks are first-class.
The site covers the parts of a Rails codebase that take real engineering judgment to get right: which gems to standardize on, how to refactor a legacy app without a rewrite, and how to keep the security baseline intact under deadline pressure. The audience is engineers who have shipped Rails to production and now have to maintain it.
Posts are not chasing news cycles. The aim is reference-grade material that holds up across Rails minor versions.
Rails Inside is written and maintained by the editorial team. Bylines on individual posts will appear as the contributor list grows.
This site is plain HTML and CSS. No framework, no build pipeline, no JavaScript on the public pages. The typeface is IBM Plex (Sans, Sans Condensed, and Mono) loaded once from Google Fonts. Hosting is Cloudflare Pages. There are no analytics, no cookies, no third-party trackers, no comments. Email the editorial team if you want to suggest a topic or correction.
Reach the editorial team at [email protected]. Reader corrections are welcome and will be folded into the relevant post with a dated update note.