rethink how I will build the MVP
I only realize it now, but Writing Startup is way more than I can chew tech-wise: my coding skills aren't up-to-par yet. What I'm going to do instead:
- Work on tiny minimum viable products (One MVP = one architectural or functional aspect of WritingStartup)
- Refactor the code into microservices, then publish the work to get quick feedback for the end-product and go past my current technical limitations
- THEN assemble Writing Startup after improving each modular part
- Work on tiny minimum viable products (One MVP = one architectural or functional aspect of WritingStartup)
- Refactor the code into microservices, then publish the work to get quick feedback for the end-product and go past my current technical limitations
- THEN assemble Writing Startup after improving each modular part
start working on the ssg feature
a writer will be able to prerender webpages with a top reading experience
text editor - implement offline autosave
start working on the text editor
project board - add drill-down feature https://www.youtube.com/watch?v=cucvr8zCa1E
A user can drill down the writing project structure to easily navigate through big content like books.
project board - a user can change the title of any project node
project board - a user can change the project title
finish Board view CRUD
A user can add/remove docs and nested subdocs for a given writing project.
work on CRUD
Ditching the RxDB library (poor doc) to use barebone PouchDB with plugins.
push landing page to prod 🎉 https://writingstartup.com
more landing page work
work on landing page launch tomorrow
project dashboard - more CRUD work
work on list board UI
