I have some stuff I built for TicHelper we can use for this. Essentially want to build an un-styled home with login, logout and user self-edit page. Would like to keep bootstrap restricted to the admin console.

End-user login should be just email account and password. When time allows I want to expand this to include base implementation for logging in with Twitter, Facebook, and possibly Google on top of email or in place of.

End-user data structure should have dates array and be initially filled with signup date object. ex.) {"signup": new Date()}.

Once end-user is registered and logged into the home page they can view member only content. ex.) Basic div with some text as placeholder. Then they can either logout or click on a link to their profile page where they can initially make edits to email and password. Maybe some basic fields so they can fill in something like name and location. Also option to cancel account with warning modal.

EmailJS needs to be implemented into end-user and admin-user account registration. Generate UUID and email url with verification route. User can log in un-verified, but cannot make any account profile changes or cancel account. Flag should exist in user data object on whether verified or not so it can be used for extending future project specifications.

This will need to be implemented in order to resolve the other enhancement issue of allowing end-users to cancel their account.

Need to add site-pages list page to the admin console. With add and edit page modals. Pages just need to have 'title', '/url', 'htmlContent', 'activeBool', 'template_name(basicPage/blogPost/etc)', and 'dates : [ ]' array starting with posted date. So simple modal will do the job for the basic page edit mode.

Once this is in place I want to merge what I built for Chromemote.com blog where I have live page editing with in-browser code editor. This way you see the page as it will look when posted as you change the code in a window floating over the page.

So in the site-pages list you can choose to make page active or inactive with a slider toggle button. Also you will have two buttons to edit the page in basic or advanced mode.

The routes for the CMS generated pages will be after the primary public routes. This way important static pages' urls dont break. If no route is caught before 404, then db will be checked for the URL. If it exist, then render page. If doesnt exist, then next() to move on to 404 route.