Skip to content

Dev site maintenance and GitHub connection

Last updated on June 6, 2026

Today I completed a long‑overdue maintenance pass on my dev site, bringing it back in sync with my main site in both structure and workflow.

Content cleanup & structure fixes

  • Reorganized the homepage sections: Pages (The Engine), Current Tasks (Posts), Demystifying Code (Chapters), Guides & Unrelated (Chapters), and Completed Tasks (Chapters).
  • Moved all completed tasks to the bottom of the page to reduce clutter while preserving documentation for future reference.
  • Ensured that task posts remain usable for writeups and documentation even if they don’t warrant full articles.
  • Finalized the new category‑based structure for displaying and sorting chapter content by relevance and priority.

Theme repo connection to GitHub

Connected my dev site’s child theme to GitHub by:

  • Initializing a new Git repository directly in the theme directory.
  • Creating a clean, purpose‑built .gitignore.
  • Committing all theme files and linking the directory to a new GitHub repo under the same account as my main theme.

This means both the main and dev themes are now versioned independently, with no conflicts — each is tied to its own private repo, but both remain accessible from the same GitHub login.