Suggestions

[rglassett]

Nice proposal, Timur. Evernote is a good clone with a lot of nice functionality. Here are some suggestions to get you started:

1. Notebooks already have an owner_id. Do notes really need an author_id? Shouldn't they have a notebook_id instead?
2. Since note bodies can get quite long, I would use a text column rather than a string for those.
3. Your JSON API isn't really a phase that adds a feature to your app. Remove this phase and build your API endpoints when they're needed (during the implementation of Notebooks or Notes)
4. You will likely want to build separate NotesIndexItem and NoteShow views.
5. Markdown formatting is pretty easy to implement and will make your app much cooler to use/demo. Try to add this as part of phase 4, before tagging. Do a search for WYSIWYG Markdown editors--Bootstrap Markdown is a pretty good one.

That should get you started. Looking forward to seeing the finished product!

[TimurM]

Thanks Ryan, this is really great feedback. I'll make appropriate updates.

Timur,

On Mon, Feb 2, 2015 at 2:37 PM, Ryan Glassett notifications@github.com
wrote:

Nice proposal, Timur. Evernote is a good clone with a lot of nice
functionality. Here are some suggestions to get you started:

1. Notebooks already have an owner_id. Do notes really need an
   author_id? Shouldn't they have a notebook_id instead?
2. Since note bodies can get quite long, I would use a text column
   rather than a string for those.
3. Your JSON API isn't really a phase that adds a feature to your app.
   Remove this phase and build your API endpoints when they're needed (during
   the implementation of Notebooks or Notes)
4. You will likely want to build separate NotesIndexItem and NoteShow
   views.
5. Markdown formatting is pretty easy to implement and will make your
   app much cooler to use/demo. Try to add this as part of phase 4, before
   tagging. Do a search for WYSIWYG Markdown editors--Bootstrap Markdown is a
   pretty good one.

That should get you started. Looking forward to seeing the finished
product!

—
Reply to this email directly or view it on GitHub
#1.