Dlayer, v1.00

Earlier today I merged in the final pull request and packaged up release v1.00 of Dlayer. It took a little while to release, and during the release, I found a couple of bugs, inevitable, but finally, after lots of work, it is now out there.

Today is just the beginning, over the next few weeks I will create a set-up process, a reset process and finish polishing the base of the Content manager, I will also start reintegrating the deleted designers, the first to return will be the Form builder.

Please visit Dlayer.com to try the demo.

Twelve stories left before v1.00

Unless I find a way to create additional stories within Pivotal Tracker, as of today there are only twelve stories left to complete. Back in October, I posted a list of some of the stories still to do, I’ve ticked off a few of those along with lots of additional tasks that I deemed necessary.

Since October I have created a few alpha release but have yet to release them at http://demo.dlayer.com, I’m so close to the official beta release that I am holding off with any releases until then.

Below is a list of changes since October:

  • Added a Typography sub tool, allows the use to change the font family for the text content item
  • Added live preview for Typography sub tool changes
  • Added an app and error log, site and identity level logs
  • Cleaned up generated HTML, columns and rows not included if they are going to be empty
  • Added helper links to empty page, columns and rows when selected, guide the user
  • Fixed a bug with the toolbar showing the incorrect tool
  • Added a simple HTML tool, a user can add HTML content items until additional tools and widgets are in place
  • Fixed a bug with colour history storing blank values
  • Added Styling sub tool to Form, Text, Heading, Image and Jumbotron content item
  • Added a live preview for background colour changes
  • Added Styling sub tool to Rows, Columns and the Page itself
  • Page, row and column selectors now clear the background colours of child items to make it easier for the user to see what they are selecting
  • Refactoring, UX improvements and bug fixes

I don’t want the release of v1.00 to go into next year, over the next couple of weeks I am going to try and complete the twelve stories remaining and possibly even push some of them to v1.02, v1.03. v1.01 is all about scripts to setup the app and reset the app and create initial sample data; this will make it easier to test after the official v1.00 beta release,

v1.01 is all about scripts, a script to setup the app, another to reset and possibly one or two to create users and set initial test data,

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