Infrastructure #92
closedfrontend overhaul
0%
Description
The frontend code here has multiple frontend frameworks, and refers to API entities/routes that have been revamped to the point where a ground-up rebuild would be faster than refactoring.
alpine is our js interactivity toolkit, bulma is our CSS framework.
"semantic ui" display code exists in the codebase, and needs to be removed.
Updated by Sam Pearson 3 months ago · Edited
In this "webapp refactor" branch/pr:
https://github.com/SamPearson/catchlist_todo/pull/43
The webapp has been stripped down to just a launcher, auth pages, a landing page and a dashboard.
There's now a documentation page in the engineering wiki about the patterns for the frontend.
Updated by Sam Pearson 3 months ago · Edited
Task component demo page in this PR
https://github.com/SamPearson/catchlist_todo/pull/44
remaining component demo pages:
- projects
- calendars
- routines
- sessions
- reports
- tags
- principles
Updated by Sam Pearson 2 months ago
Ordering component demo pages:
tags
principles
projects
sessions
reports
routines
calendars
tags and principles will use basically the same components
then those need to be embedded into the task components
projects will need to be integrated with tasks (as well as tags/principles)
sessions can be done in kind of a standalone way, but will open the door to creating a report component
then we can wrap up with sessions and calendars, after which we hook the frontend up to the API.
Updated by Sam Pearson 2 months ago
- Target version set to V2.2 - Webapp Component Demos
Updated by Sam Pearson 2 months ago
I think we can call this done as of v2.1.1 - the webapp has been refactored and we have a good framework.
Filling out the demos and pages is a different task. Component demos in v2.2 , hooking up the API and building functional pages in v2.3