An end-to-end look at the development of a simple blog app using a modified Agile workflow and Ruby on Rails. This is meant to provide you with a high level overview of the entire process used to create real applications.
beginning to end, something most beginners haven’t seen before. 2. Get you exposed to some of the tools and processes we’ll be learning later on in the program. 3. This is just an overview and is NOT meant to teach you code or everything about the tools!
might take to build an application for yourself or a client, where you’re doing it all on your own. • If you were in a larger team, roles would be divvied up but the process wouldn’t be too much different. • So, basically, anyone should ﬁnd this useful.
a Mockup of our site 3. Break the mockup into bite-sized Stories. For each story: I. Determine and set up required Data Architecture II. Build the Back End of the story III. Build the Front End! 4. Refactor, iterate and then Ship the site to production.
edit or delete posts — they’re up there for good. II. The post creator can ﬁll in their own name 2. The ability to comment on posts. I. No need to edit or delete comments either. II. The comment creator can ﬁll in their own name 3. No logins required — this is all honor-system. 1. Figure out User Needs
bite-sized pieces based on very speciﬁc user needs, for example: ✴ “As an [author], I want to [publish posts on the site] so that I can [put my thoughts on the web],” ✴ “As a [reader], I want to [easily view the most recent posts] so that I can [stay up to date]” ✴ “As a [reader], I want to [write a comment on that post] so that I can [offer my thoughts on a post]” • Then prioritize the stories to tackle ﬁrst and get started
comments • Comments need fields for content, author, and the parent post’s ID • A post can have many comments Post Comment Comment Comment Comment ! content (string, 140 max) author (string, 20 max) post_id (integer)