11 minute reading time; ~2120 words<\/p>\n\n\n\n
Welcome and hello!<\/p>\n\n\n\n
In this post, we’re going to touch on the overall lessons from the series so far, and then dive into delivering the ability to actually edit a template.<\/p>\n\n\n\n
If you haven’t read the previous posts, I’d suggest you start at An App From Scratch: Part 1 \u2013 What To Build<\/a>. You can also find all the related documents and code here: Building Tailgunner<\/a>.<\/p>\n\n\n\n In between the last post and this one, I made a few small changes to address some housekeeping notes from the work I’ve done.<\/p>\n\n\n\n So far in this series we’ve explored what it takes to get from an overall idea down to an actual functional user feature. Along the way, we talked about how to explore the idea, and break it down into smaller and smaller pieces, until we reached a point where an engineer can actually execute and deliver the functional product, incrementally building in a way that always left us with something we could use.<\/p>\n\n\n\n One of the biggest reflections I have is how much work is involved in both making a change and also breaking down the change and documenting every piece of it. It’s something I’d forgotten, because I’ve spent so much time over the last two years reasoning about the documentation part, freeing up the developers on my team to focus on building it.<\/p>\n\n\n\n Hopefully through this series so far, you’ve gained a new appreciation for the parts of the process that you didn’t know well, be it on the product design and planning side, or the building side of the fence. For every hour of code I’ve written, I’ve spent at least twice that time talking about it.<\/p>\n\n\n\n Now that we’ve completed the ability to add templates, we’re going to zoom out and tackle more of the workflows we previously identified for US1<\/a>.<\/p>\n\n\n\n US1: Workflows<\/strong><\/p>\n\n\n\n This is a much larger piece of work in a single post, so I’m going to only dive into specific pieces of the work I’ve done.<\/p>\n\n\n\n I wanted to add some iconography to the site, so I installed FontAwesome, using their guide<\/a>. <\/p>\n\n\n\nSome Housekeeping<\/h2>\n\n\n\n
\n
Reflections \/ Lessons<\/h2>\n\n\n\n
Expanding The Functionality<\/h2>\n\n\n\n
\n
Defining the metadata of a new template, including title.<\/mark><\/li>\n\n\n\n
Changing the metadata for a template.<\/mark><\/li>\n\n\n\n
Adding, editing, re-ordering, and deleting the fields in the form.<\/mark><\/li>\n\n\n\n
Adding, editing, re-ordering, and deleting the options in a dropdown.<\/mark><\/li>\n\n\n\n
Persisting all changes to a template.<\/mark><\/li>\n\n\n\n
Duplicating a template, with a new name.<\/li>\n\n\n\n
Permanently removing a form template from the system.<\/li>\n<\/ul>\n<\/div>\n\n\n\nInteresting Changes<\/h2>\n\n\n\n
Font Awesome Icons<\/h3>\n\n\n\n