The way the choices are made between going to setup, start, page creation etc. Also, the Backbone.History is being started once but in multiple places which is a bit confusing.

Create user, set Siteify properties to indicate the setup is complete and create first home page.

Make sure the password is encrypted before sending it to the server. Don't send the password over unprotected 💃

Look in to this. It's commented out currently in user.js

Sending the correct messages to the front end for error handling. This also needs attention on the api controllers

Better for scoping and strategies for 3rd party api's like Google, FB etc

Instead of the email which it currently is. Although both are unique, I want to be able to change the email address of a user.

Check out why i've decided to pass the context in to the router init. I think it might be due to packages sharing the router.

The refresh token should have expired after an hour. Investigate.

Take the page change stuff out of SiteifyModel and make the PageModel the owner of this asset.

If user 1 turns of SiteifyLive and User 2 who is the owner adds pages, when user 1 turns SiteifyLive back on and adds pages, user 2 doesn't see the other updated ones, sort of thing. . . 🍶

Just if you remove a page, theres no point in keeping the relationship there also

Implement refresh tokens and test by setting expiry to very short. Already half done.

Have to figure this out still. Will the user save HTML blobs, create templates? Move the admin or siteify templates to another place other than in templates.

Can have multiple pages the same name. Although this isn't a problem, it could still cause problems.

Each page will have it's path and route dynamically created before save in Mongo. Although it would be bad to have the same name at the same level for example :

www.siteify.io/about
www.siteify.io/about

It's not a problem to have :

www.siteify.io/customer
www.siteify.io/people/customer

As the routes would be different. . . .

The solution for now would be to add unique : true to the page model in Node and also to save wasting a request, check if the page title is unique in the pages collection.

Various issues around implementation still need to be worked through : https://github.com/OptimalBits/node_acl#isAllowed

Don't expect the folder name and the filename to be the same.

Create the users management list and crud options for the site owner.

Store the template in one property and map that content to the templates to be resolved on the frontend.

The mongo documents will look something like this :

pageDocument : {
  contentTemplate: "<h1>{{na37hn37a3rhn7a3rhn7a}}</h1><p>{{38ncrw37irgnw37rwngc37}}</p>",
  contentMap : {
    na37hn37a3rhn7a3rhn7a : "Page Title",
    38ncrw37irgnw37rwngc37 : "This is my nice paragraph text"
  }
  other props ...
}

Once the user registers for the first time, redirect to login and return to the user that they created the account.

res.redirect('login?registered=1');
if (req.param('registered') === '1') {
messages = flash('Congratulations, your account was created!', null);
}