I'm building SaaS and documenting the process. Day 23: verified user and publishing posts
This is the twenty-fourth episode in the reality show about the development SaaS app from scratch. The previous episodes:
Open SaaS development from scratch: why and what
Day 1: requirements and UI wireframes
Day 2: admin pages
Day 3: user pages
Day 4: database models, database update, and a couple of new wireframe pages
Day 5: started API and made changes to the database models
Day 6: created the admin board and new problems
Day 7: board settings page
Day 8: board settings page, more details and tabs
Day 9: board settings page, more tabs
Day 10: finished all 4 meta lists for board settings page
Day 11: experimenting with subdomains
Days 12 & 13: subdomains, separate apps, and user interface
Day 14: end-user UI for creating and editing posts
Day 15: end-user UI - bug fixes and list of user's posts with paging
Day 16: the skeleton of public page with the list of posts
Day 17 & 18: working on the public page
Day 19: Post view and voting
Day 20: finished voting functionality and started comments
Day 21st: finished comments, improved voting, and started board admin panel for user mngment
Day 22nd: finished board admin user management
Forced break and the startup idea for those who want new ideas
After the forced break, I came back to the project. What I was doing was allowing a board admin to mark users as verified. It may be very useful if you need to filter the real paid users using your application from others - lurkers and those on a free plan. In the future it probably would be done automatically somehow, but for now it's just a manual action - at least to see if a board admin would use it at all.
Another thing I was doing was adding some data validation on saving a post. There are 2 different set of requirements: one is for just saving a draft, and the second one is before publishing. When you have a draft it doesn't matter if you added a title of a type of question - you just need to not to excess the strings' lengths. But to be published, a post should have all mandatory attributes: title, content, category, and type. I did it on the frontend using a simple React code, and on the backend, using Marshmallow schemas - it allows to provide the validation pretty easy and quickly.
Time spent: 1 hour
Total time spent so far: 56.5 hours
Thanks! Stay tuned!
