/
Architecture documentation
Architecture documentation
Editor MVP (Iteration 1)
The current iteration of the editor MVP includes 4 main steps in the process for changes to be reflected for a specific document (blog page) in the frontend of the website.
Step 1- HTTP Request
A Publish button click is triggered on the CMS website for a specific document in which is being edited. This as a result sends a HTTP (Iteration1) POST request to the backend.
Step 2&3- Update in DB
As a result the document JSON object which is sent from the CMS frontend will then replace the existing object stored inside the DB
Step 4 - Subsequent fetches reflect change
The Document JSON object will be the result when fetched from the Actual frontend, i.e. when the blog post is being fetched from the user, it will now be updated.
, multiple selections available,
Related content
General Deployment Documentation
General Deployment Documentation
Read with this
Back-end Design Document
Back-end Design Document
More like this
Backend - Editor technical guide
Backend - Editor technical guide
More like this
Code style and standards
Code style and standards
Read with this
Websites 2023 Vision, Principles and Goals
Websites 2023 Vision, Principles and Goals
Read with this
UNSW CSESoc