My humble beginnings as a writer combining engineering knowledge to tell stories.

Log 001

Tuesday was the day my new life as a part-time blogger began after multiple code deployments. I spent hours experimenting with its aesthetics and functionality, words and formatting appearing and disappearing with every new sandbox test. What was the culprit? GitHub's relative paths. After setting up the repository structure for the blog section, file paths like assets/css/custom.css vanished before my eyes. Apparently, the file path needed one more "/" in front of "assets" and things started working again.

This wasn't just a typical styling and code fix; it was reprogramming of one's mindset. Seeing the difference between the code working on one aspect and then seeing it work anywhere is one characteristic of this change. It's not only good coding practice for front-end web development. It will sustain the website blog's skeleton for a better user experience. Being aware of how multiple aspects come together-- SEO, web hosting, repository organization, etc. -- is the key to understanding some foundations of systems engineering.

A few guardrails that every writer building a website should know are:

• Use root-relative file paths to make sure shared assets show on your website.

• Keep header/footer HTML in sync across all website pages without changing it.

• Never launch code without previewing it with GitHub Desktop or VS (Visual Studio) Code with the Live Server extension.

• When you're stuck look for extra code that shouldn't be there; misspelled fields; anything that deviates from the code pattern, or go to DevTools → Network in your web browser for additional troubleshooting.

Today's Win: I created my first blog post and can reuse the template for future logs.