Ok, here’s the situation: you’ve started your project, currently your team has frontend developers and backend developers. Everyone is happy and doing their parts.
What happens when the pages are ready for implementation?
You guessed it, it goes to the hands of the backend developers who will do their magic: create the components for choose your favourite CMS here.
At this point we’re still happy, everything is working just fine and the project will be delivered on time.
A couple of days have passed and some JIRA tickets have been raised: we need to fix something in the frontend.
No problem, the frontend developer will open up the HTML files and do the proper edits.
Iteration two hundred seventy six
At some point between revision 1 and revision 276 someone updated the backend CMS component and not the HTML static file. Probably the change was simple enough, there was no need to involve any frontend dev.
That is actually fine! It’s way cheaper, project-wise, and faster to develop.
Now, be careful, that decision might cause a lot of trouble in the future, when new major features will need to be added. An out of date slices will force us to download source files from production. We all know those files can be messy, with random ID’s everywhere, extra empty divs, inline styles, uncommented code…
So, what’ the proper way of applying frontend changes?
Also, if the project has enough budget to have a frontend developer on board, the above workflow is useless. Just send everything to the frontend dev.
Try finding balance!
This best practices should not be a burden, if you get used to it I think you’ll get real benefits. If someone is capable of changing a component’s markup, is also capable of editing plain HTML files.
You should always keep your static HTML files up to date. Not with content changes but markup. I’m not saying it’s easy or cheap but it’s the right way to iterate. Not all projects will have the budget or client will to maintain this code standards. We, as professional, need to advice and convince our clients this is mandatory. In the end, it will probably save them money.
I hope now you have better insight of how you can be more productive and have a better future-proof code in your projects.
Have something to add? Leave a comment down below.