Morning session resulted in adding content loading indicators to profile + journal pages for the first view while they are being built in the background. A nice touch that makes it less of a janky flash of loading text jumping before you see real content.
I've also investigated using a pre-built slate-superset editor a bit. Its tempting to take a shortcut as it would save me a lot of development time for the baseline editor functionality. On the other hand it would lead to a bigger JS bundle being shipped because it uses a different CSS-in-JS solution (styled-components) than what I'm using (theme-ui + emotion). As I do build custom logic on top regardless I'm afraid any investment made on top would be wasted time if I suddenly realise I need to build on the core Slate editor package.
I will probably try to integrate it and see if I can build the custom plugins easily on top and if the terminology and interfaces for those plugins are similar enough to plain Slate that it would be portable if I need to switch around. For a MVP it makes a lot of sense to save as much development time as I can so my gut feeling is to run with slate-plugins-next and bite the bullet if it hits me later.
Short update. Managed to wire up the early access form on the home page. Now emails are stored in the db with some meta data. Still lacking receipt email but its a good step towards MVP state for the email capturing.
Good late night hack session to encapsulate a lot I've been working on the last couple of days. In summary I'm getting a lot clearer picture of the framing of the final MVP. Trying to summarize the things that have just fallen in place:
As the framing and layout is more in place now I expect to get back to focus on the editor experience and finally work on the killer features of M1: Data!