...
| Each step in the instructions has its own page, which breaks down the task required for the overall sewing projects into smaller steps that are more manageable for a beginning sewer. Before seeing any of the individual tasks, an overview instructions page is show, so users can look over all of the steps involved in the project before beginning. |
High-Level Implementation
When we translated our code from pure front-end to a backend supported system we did not move all of our code (especially because we focused on the front end).
The search for projects and sewing help topics uses front end javascript. The project search terms for those pages and the various variables are stored in javascript. We do not allow users to upload projects, so this solution works for us for now. User accounts are backed by a backend.
When a person clicks to save a project the step after the current is saved. When a user later checks the project page if the current step is less than the saved step they see a checked off symbol.
If a user is logged in they can add notes. Notes record what section of what project they're in and who made them among others.
Pages that users are not allowed to access have been blocked off from the back end (for example a list of all users).
