Read these in order if you are starting from scratch. The introduction lays out the thesis behind the project: why a network of small custom mappings beats any single perfect one, and how to participate. From there, pick the integration tier that matches your stack, learn how to mint or reseed a mapping that is yours alone, and drop the CLAUDE.md template into your repo so any AI co-pilot you use respects the conventions zero-shot.
All four pages are rendered from the docs/ folder in the repo. Edits there flow through here on the next build.
Guides
- 01Introduction: a network of confusionThe thesis. Why the project is a collective effort, why a small custom mapping helps anyway, and how to come help us build the rest.
- 02Integration guideThe main paths: the React component, the copy-paste CDN embed, and the downloadable font for Word/PDF.
- 03Where the encoding happensThe one rule, and the two ways people break it. Measured against five real builds: what leaks, what does not, and how to check your own.
- 04Use anywhere: any frameworkNot using React? Call @shieldfont/core in any build step or server render, load the font with ten lines of @font-face.
- 05Concealment & camouflageThe three ways to ship and how much each one hides that ShieldFont is in use. Why the React tier conceals the most, and stores the least.
- 06Custom mappings: make it yoursTwo paths. Mint from the methodology, or reseed an existing mapping with a private key. Free use is conditioned on running one.
- 07AI co-pilot conventionsDrop-in CLAUDE.md template. Conventions for Claude / Cursor / GPT / Aider.