Admin.Js Technical Specification

[Caleb-Cohen]

Summary

Admin.Js is an open-source library for building admin panels. This tech spec is assessing the potential functionality of Admin.Js in regards.

Scope

• Create Admin.Js repo and hosting
• Simple UI for viewing events in the DB
• Ability to approve or delete events

Data Model

The ability to approve or delete events will impact the events model.

User Stories

Admin team is notified of a newly created event. They access admin.js, review the event, and approve it being added to calendar. Event now becomes viewable in the calendar.

Implementation Details

• Create Admin.Js UI
• Add pending to newly created event objects with together
• Link Admin.Js to a test DB with event models matching Together project
• Ensure Admin.Js is capable of replacing pending fields to approved
• Have Together only render approved evens

APIs

Admin.Js will need to query the DB for events and then update those events specified. I'm not sure if that's considered a new API.

Security/Privacy

Admin.Js needs to be accesibly by only verified members of the Together project.

Additionally, with updating the event models we need to ensure that Admin.Js does not have the ability to destroy or adversely mutate event objects.accessible

Testing

I'm not familier with testing over multiple repos. Testing is certainly something that should be considered more in-depth, but not something I'm equipped to answer at this moment.

Open Questions

No response

Deployment

As we're deploying a middleware admin feature to an already functioning application and DB any changes to production should be carefully considered and timed.