Orientation and setup readiness
0/2
- See the finished app and the criteria it must meet10 min
You will build one Rails application from an empty directory to a live URL: a small blog with articles, comments, a search box, user accounts, and an automated test suite. No JavaScript framework, no containers — Rails as it ships, run part-time over roughly 6–8 weeks.
This only works if you build it, not read it. Every phase below ends with something running on your machine or in production, not a paragraph you agreed with.
CRUD resource /articles supports create, edit, delete through a real form, not the console Association An article has many comments; the relation works from the Rails console and on the show page Search A search box on the articles index filters by title Authentication Sign-up and login work at /sign_up and /login; writing requires login, reading does not Automated tests bin/rails test passes: model, controller and one system test Deployment The app is reachable on a public URL, accepts sign-ups and creates articles in production What the finished app must do — the criteria the last phase checks it against - Week 1Environment: Mise, Ruby, Rails, first server
- Weeks 2–3MVC core: scaffold, request cycle, search, comments
- Weeks 4–5Authentication and per-user data
- Week 6Tests: model, controller, system
- Weeks 7–8Deploy to Render and go live
A realistic part-time pace — adjust to your own week To do
These are what the final deployed app is judged against — nothing here is invented at the end.
OptionalWhenever a graded check later in this guide catches you out, add a row here: what you got wrong, and the misconception behind it. The closing step reads this back.
Row number What you got wrong The misconception behind it Remove
0/3 done