Back to MVP

A week ago I gave myself two options, one, ignore the code smells and work to release v1.00, two, accept what I have been trying to tell myself and hit the DELETE key, I opted for option two.

After the big Content manager rework of 2016 I was left with a code base at odds with itself. When I looked at it more rationally, the Content manager was easily the module that was both the most complete and the one I was the most happy with. For the rest,the order was Form builder, Web site manager and Image library. The Image library and Web site manager were a pain to add modular tool support to and then I looked and thought why am I bothering, the Web site manager is a preview from when the app was a closed source project and the Image library only had one functional tool, upload……DELETE, after that I aimed my trigger finger at the Form builder, DELETE.

The modules haven’t gone; they will be back very soon, the problem is they were stopping progress elsewhere, you can rewrite an app forever to make it a perfect design, I need to ship and iterate.

The Form builder will be the quickest to return, it doesn’t have many issues, I need to update the Javascript to use data selectors and review the model code for the tools but that will be a pleasure when it is part of an iterative task and not a refactor.

Listed below are the titles for the pivotal tickets that need to be completed before I can ship v1.00.

  • Initial work on styling sub tools
  • Add to colour history
  • Nesting support exposed correctly
  • Suggested size for content items
  • Raw HTML content tools
  • Simple nav bar tools
  • Updated tool help tabs
  • Clean up database
  • Apply UX guidelines to Content manager