Lighthouse mark for Peisong's Lighthouse Peisong's Lighthouse Somewhere to find inspiration.

LIGHTHOUSE

Lighthouse Configuration

This document describes the repository-local configuration and content conventions used by the Lighthouse site.

Table of Contents

Jekyll Config

The canonical site configuration is:

Important settings include:

  • title, description, timezone
  • url
  • markdown: kramdown
  • permalink: pretty
  • collection output for photos and automated_posts

Public feed endpoints currently live at:

  • /feed.xml
  • /blogs/feed.xml

The primary post browsing surface is /navigator/. It combines deployment-generated repository posts with built-in photo posts. Source roots such as /blogs/ are generated by the deployment pipeline and remain scoped to their own repository content.

Navigator listing controls default to navigator view, surfaced posts enabled, and most-recent ordering. Visitors can switch to a flat all-posts view and sort by most recent, least recent, alphabetical, highest rating, or lowest rating. Rating order uses generated random_weight_total values where available; unrated cards sort after rated cards.

The site also carries resume.tex at repo root as the source of truth for the generated resume page and PDF artifact.

Collections

Current collections:

  • photos Source: _photos/ Layout default: photo
  • automated_posts Source: _automated_posts/ Layout default: page

The automated_posts collection is machine-owned and should not be edited manually.

Shared Data

Shared site metadata and navigation live under _data/:

These files feed the site header, footer, and homepage content blocks.

Machine-generated feed policy currently lands under:

  • _data/generated/rss.yml

Machine-generated navigator source metadata lands under:

  • _data/generated/navigator.yml

Automation-Owned Paths

The deployment pipeline may rewrite the following paths on every run:

  • _automated_posts/
  • generated-directories/
  • _data/generated/
  • assets/generated/

The raw linked-file subtree currently lives under assets/generated/raw/, and resume artifacts are written under assets/generated/resume/. All other paths are treated as manual source by default.

Build Exclusions

The repository excludes non-public paths from the Jekyll build through _config.yml. That exclusion list currently covers:

  • docs and repo-only notes
  • vendored dependencies
  • Git metadata
  • Bundler local state
  • generated raw assets, which the deployment pipeline copies into the built site after Jekyll has finished rendering