Reserve /tangible.team/ for a single-file HTML archive - #581
Merged
Conversation
Reserves /tangible.team/ for a single-file HTML archive. The page carries no YAML front matter, so Jekyll classifies it as a static file and copies it into the built site byte for byte. Adding tangible.team/ to .prettierignore keeps make lint from reformatting the archive, which the repository prettier workflow would otherwise rewrite on every branch push.
✅ Deploy Preview for p13i ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
p13i
marked this pull request as ready for review
August 24, 2026 22:45
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reserves
/tangible.team/on p13i.io for a single-file HTMLarchive. This pull request lands only the placeholder and
the one configuration change the archive needs; the real
~55 MB
index.htmlis dropped in on this branch afterwards.How the path resolves
build_type: legacy,source.branch: gh-pages,source.path: /,cname: p13i.io,https_enforced: true(
GET /repos/p13i/p13i.github.io/pages). GitHub runsJekyll 3.8.0 server-side and publishes
_site/.Pageonly out of a file that starts witha YAML front matter header. Everything else is a
StaticFileand is copied into_site/unchanged.tangible.team/index.htmlstarts with<!DOCTYPE html>,so it is a static file.
README.md,Dockerfile, andstatic/js/main.jsare all byte-for-byteidentical to their
_site/counterparts._site/tangible.team/index.htmlis then served as thedirectory index of
https://p13i.io/tangible.team/.No
.nojekyll, front matter, layout, permalink, or_config.ymlchange is needed, and none is wanted: a.nojekyllfile would switch off the Jekyll build the restof the site depends on, and an
exclude:entry would dropthe page out of
_site/entirely.The one change that is needed
make lintrunsnpx prettier --write --print-width 60 --trailing-comma=none --prose-wrap always '**/*.{md,html,yml,yaml}',and
.github/workflows/prettier.ymlrunsmake lintonevery push to every branch, failing the job and opening an
"Apply prettier" pull request when the tree changes. Without
an ignore entry prettier claims the file:
With
tangible.team/added to.prettierignore:scripts/generate_sitemap.pyonly reads*.mdunder_bytes,_tweets,_posts, and., so it does not touchthis directory.
Size and storage notes
.gitattributesandgit check-attr filter -- tangible.team/index.htmlreports
filter: unspecified, so the archive is stored asan ordinary Git blob, not Git LFS.
100 MB. A ~55 MB file pushes with a warning.
roughly doubles it, still far under the 1 GB GitHub Pages
published-site limit.
Written by Claude