Reordered the homepage so the Daily_Blog sits right below the console and header. Renamed the blog to Captain's Log and the skill grid to Skill_Tracker.

Pulled the Project Matrix off the main page onto its own dedicated page, and replaced it with a Cookie-Clicker-style news ticker that scrolls through my projects. Pinned it as a sticky strip just under the header so it's always visible, and added a ticker terminal command to toggle it on and off.

Also cleaned up the terminal — fixed the auto-scroll so it jumps to the newest output, tidied the title bar, and gave the skill cards a subtle hover-lift. Decluttered the top nav now that the ticker handles project access.

Also researched the simplest safe way to authenticate Git pushes from a scheduled task; settled on Git Credential Manager with a GitHub PAT — no secrets in the script, no SSH key juggling, and it works reliably under the same Windows user.

The automation is starting to come together. Still tweaking the formatting from the AI API call. Working well enough to start and afterwards I can edit it, don't have to worry about syncing it works once a day, but I can also trigger it through the GUI. Just got images working too!!

Hosting and Publishing a Website

Found some easy free domains:

• Cloudflare Pages gives a free .pages.dev subdomain — stable, reliable, and perfect for projects.

• GitHub Pages gives a free github.io subdomain — also stable and free forever. I'll likely host my projects this way and link them her

• GitHub Student Developer Pack gives a free .me domain for one year

Saved for later

AI write-ups via GitHub Action. Right now the note body is the post. The next evolution: a CI step that hands my raw Obsidian note to an LLM and publishes a polished write-up before the build runs. Needs an API key and an Action workflow — deliberately deferred until the manual habit sticks.

Auto-generated resume. The download button is hidden until this exists: a build step that compiles the Neural_Grid and Project_Matrix into a clean PDF. Same philosophy as the blog — the site's data is the single source of truth, documents are just projections of it.

RSS feed. Signal_Log posts as an RSS/Atom feed, generated at build time. Cheap to add once posts have stable URLs.

Per-post URLs. Hash routing so each transmission is shareable and linkable — a prerequisite for RSS and for posts showing up anywhere but here.

Next up (pre-deploy)

1. Replace every placeholder — profile, credentials, project links — with real data
2. Regenerate the OG image and favicon with the real name
3. Harden the note parser: warn on unknown skill ids so a typo doesn't silently vanish
4. Cap the Growth_Log feed so a year of notes doesn't render 300 entries
5. Push to GitHub, connect Cloudflare Pages, turn on analytics

Then the loop closes: write in Obsidian, push, and the site does the rest.

Project cards now expose year, company, role, and impact metadata, while detail modals render raw source markdown as HTML instead of plain text.

A new GitHub Actions workflow is added to build and publish the site automatically on push.

Next:

1. Connect the repo to GitHub Pages or Cloudflare Pages and verify the deployment environment.
2. Add automated PDF resume export from the compiled markdown runtime data.
3. Expand note formatting rules for post tagging, embeds, and draft handling.
4. Add a publishing badge or status indicator into the Signal_Log section.