Product: CMS API
Sprint Summary

Daily Objectives

Notes

I’ve basically written what I needed for the Data Design sections in Notes29, so I just need to copy that into the actual Software Design Document.
I still need to make the Lucid Charts for the User Roles section and Update the Architecture one to include a separate item for ‘Content Management’. Also I think it’d be cool to include an example diagram for what link listing a PageEntry would look like.
For the Software Design Document specifically, I need to figure out the actual structure. Since the database models/tables are gonna be very similar to the actual API resources, I’ll just talk about the API rather than the database, but with small references about how they’d be different. For the User Roles section though, I can go ahead and talk about it in reference to the database.

  1. Data Design
    • Introduction
    • API Design
    • User Roles Models

Model URI’s
Base url: /app/v1/

Restricted URI’s

I need to flesh out what exactly the project schema is? ProjectPage doesn’t need to have a schema since each pageEntry won’t have a set format. Page entries need a name though and a type, entry item will list what kind of type it is with a string or number of what it is or whatever type it is. Need to make a model for each entry type.
PageEntries have no knowledge of other sibling entries by the way, but CollectionEntries may have next or prev for querying purposes.

Objectives Completed