TeeSF.com

Public site log

Site Development Log

A public record of how TeeSF.com changes over time: brief deployment notes first, then a weekly narrative that explains what changed on the site.

Log Structure

Each deployment adds one short entry with three to five public bullets. Once a week, those entries are folded into a plain-language blog note.

After every deploy: assign a new version, update assets/data/site.json, and add one public log entry with date, version, public impact, and 3-5 short bullets.
Every week: publish one narrative summary of visible site work.
Privacy check: keep service names high-level and remove anything personal, secret, or account-specific.
Version number: every public site version uses TSF-YYYY.MM.DD.N, where N is the deploy number for that day. The current version must be visible in the fixed bottom-right badge on every public page.
Deploy note template:
Date - version - deploy label - public impact - 3 to 5 bullets

Weekly note template:
Week dates - short title - 2 to 4 paragraphs in public, non-private language

Deploy Log

Short summaries of what changed in each public deployment.

Deploy note Version TSF-2026.04.27.5

New event collections update

  • Rebuilt the gallery data from the current photo folders.
  • Added new collection filters for Tesla Pitch Night, Codex Community Meetup, AWS and EF events, and TatianaSF.
  • Converted PNG files to JPEG copies and removed the PNG originals from the publishable photo set.
  • Removed gallery references to photo files that are no longer present.
  • Kept the public version badge and cache-safe asset URLs current.
Deploy note Version TSF-2026.04.27.4

Hero image and JPEG gallery update

  • Changed the homepage hero image to the event photography cover image.
  • Updated the Open Graph preview image to match the new hero image.
  • Replaced gallery PNG image paths with matching JPEG image paths.
  • Confirmed that each matching JPEG file exists before publication.
  • Kept the public version badge and cache-safe asset URLs current.
Deploy note Version TSF-2026.04.27.3

Logo and gallery layout update

  • Added the TeeSF logo beside the homepage brand name.
  • Kept the contact area focused on the public phone number only.
  • Rebuilt the gallery data so only existing local image files are displayed.
  • Added image dimensions to the photo data and tuned card ratios for cleaner spacing.
  • Narrowed the page layout to prevent horizontal scrolling.
Deploy note Version TSF-2026.04.27.2

Contact and version badge update

  • Replaced the email contact link on the homepage with the public phone number.
  • Added a DevLog link to the top navigation for easier access.
  • Matched the homepage version badge styling to the DevLog badge.
  • Added cache-safe asset URLs so the latest CSS and JavaScript load after deployment.
  • Updated the public version metadata for this deployment.
Deploy note Version TSF-2026.04.27.1

Premium visual journal MVP

  • Published the new TeeSF.com homepage as a premium personal visual journal.
  • Added a curated featured collection, category filters, gallery wall, and lightbox.
  • Moved reusable photo data into assets/data/photos.json.
  • Restored the fixed bottom-right version badge on the public homepage.
  • Kept the legacy site backup out of live deployment while preserving it in Git.
Deploy note Version TSF-2026.04.26.4

Site version badge and numbering rule

  • Introduced the public site version format TSF-YYYY.MM.DD.N.
  • Assigned the current public version number TSF-2026.04.26.4.
  • Added a fixed bottom-right version badge that stays visible while scrolling.
  • Documented that every future deploy must update the visible version number.
  • Kept the version note public-only, with no private deployment or account details.
Deploy note Version TSF-2026.04.26.3

Static homepage and public development log

  • Published the current TeeSF.com homepage as a self-contained static snapshot.
  • Kept the live page focused on the visible site experience without carrying over WordPress internals.
  • Used the existing GitHub-to-Hostinger deployment flow for publication.
  • Improved deployment reliability for the public static site workflow.
  • Added this public development log and weekly blog structure for future updates.

Weekly Blog

Longer public notes about the visible progress of the site.

Weekly note

Moving TeeSF.com into a static publishing flow

This week, TeeSF.com moved from a live WordPress homepage into a static publishing flow that can be deployed directly to the public site. The goal was to preserve the visible homepage as it existed, while making the deployment process simpler and easier to repeat.

The homepage was published as a self-contained HTML snapshot, so the public version can load without relying on the original WordPress page structure. The deployment path now runs through GitHub and Hostinger, using only public-facing site files for publication.

A new development log was added so future site work can be recorded clearly. Each deploy will get a short public summary, and each week those notes will be turned into a readable blog-style update about what changed on the site.

The site also gained a lightweight public version number. The version TSF-2026.04.26.4 is shown in a fixed badge while browsing, making it easier to confirm which deployed version is live.

TSF-2026.04.27.5