Design Docs Review #2

[jliversi]

Here are my notes on your backend and frontend routes:

BACKEND ROUTES
Tags:

• What is the motivation for the get route for your tags? If you have a good reason, I’m okay with it, but you may not need it.
• Your route which gets the notes for a specific tag should probably be a nested route (“tags/:tag_id/notes”)
• Your create and delete routes for tags should be nested with a :note_id (you’ll only ever be creating or removing tags on a specific note).

Taggings:

• You probably don’t need any of these routes as this functionality will be handled by the note and tag routes

FRONTEND ROUTES

• Include routes for specific notebooks (“notebooks/:notebook_id) and specific notes (“notebooks/:notebook_id/notes/:note_id”)
• Flesh out your components with all the components you’ll need. For example, your NotesIndex should probably include NoteIndexItem components. Your NoteShow component will need to include your RichTextEditComponent. Etc. Really think these through as these will be your roadmap as you build out your frontend.