zhenrulo / simplycms Goto Github PK

• Login page
• Base, side bar, center general responsiveness
• Content manager page
• Media page
• Database page
• Profile page

• Side navigation bar
• Left panel bar (page options menu, optional buttons/functions, etc)
  - [ ] Right panel bar (version control)
• Notification bar
• Download and upload progression call-out box
• Animation
• Header (TBD)
• Footer (TBD)

Split each different section to a separate files to ease the development

Postgresql database does not read/create the database inside the container.
Instead, the local machine SQL server is used.

• Decide the workflow for development and deployment (e.g.: Users are able to migrate data after the schema is set?)
• Improve the logic of the content status in the backend (to decouple and make it reusable for all scenarios in the future when comparing the database before and after modification is made)

Content creation-

• Create content with given display and route name (display for frontend and route name for backend)
• Communication between the content page and builder page
• Data flow between pages after content created
• Datatable to record every database created
• Delete and edit initial table settings
• Content type editor

Content modification-

• Content builder page design
• Content builder page function
• INTEGER
• TEXT
• BOOLEAN
• CHARACTER
• DATE
• LOCATION
• MEDIA
• JSON
• RELATIONSHIP
• Column Modification
  Issues-
• #28
• Save button now made changes to all schemas as only one database exist ( Fixed this with either finding a solution to migrate certain schemas or fix the workflow in #28 )
• Save button now will run data migration for all schemas instead of specific schemas. [Solved]
• The migration doesn't work in celery task. [Solved]

- Main function:

• Home page - #24
• Dynamic content(database) creation/modification - #23
• Admin function to manage user database
• Dashboard for visual statistic overview
• Media/file library
• Version control/History management to track each change made to the content
• Communication/comment between content managers using the website.

- Account management:

• Login/Logout (Without breaking the access control)
• Registration
• Forget password
• Change password
• Additional feature: 2-factor Authentication: email TOTP, etc
• Picture

- Security:

• CSRF prevention
• Authentication and Authorization validate
• emphasize protection against XXS
• Permission control (ex: Flask principal)
• Website admin account hashing with salt
• Cookie configuration, SSL self-signed certificate, Server-side session, etc

• Move the home page out to the index page
• Redesign home page
• Account related function (login, register) will be accessible from the home page