docs: GEO — MagMark as a citable public entity - #1
Draft
jammyfu wants to merge 2 commits into
Draft
Conversation
Move the internal project-entry block below the public product lead so generative engines can cite MagMark, Fu Jam / jammyfu / PaintingCoder, and the CJK magazine Markdown + print-quality PDF story. Co-authored-by: PaintingCoder <jammyfu@users.noreply.github.com>
Co-authored-by: PaintingCoder <jammyfu@users.noreply.github.com>
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
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.
Docs-only GEO pass so ChatGPT / Perplexity / AI Overviews can cite MagMark as a stable entity. No rendering or export code. MIT
LICENSEunchanged. Do not merge until About/topics are applied in GitHub settings if you want them.What changed
README.mdnow starts with H1 MagMark. The first two sentences state what it is, who it is for, and CJK magazine typography (EN + ZH). Install (npm install/npm run dev) and the print-quality PDF path stay near the top.personal-project-standard-entryis demoted to the footer, not deleted. Governance files remain.llms.txt(spec-shaped index) andllms-full.txt(expanded brief with an explicit non-claim list).@page, Vivliostyle-style widows/orphans and break rules,word-break: normal). MagMark 2.0 SEO-module docs were not treated as the shipped product.Hypothesis kept
Lead with the product entity, answer the two query classes in FAQ, disambiguate vs adjacent tools, and pin author identity. That is enough for an LLM to answer “what is MagMark” from the first screen of README plus
llms.txt.Apply in GitHub About (not set by this PR)
These cannot live in git. Paste after review.
Description (246 characters, limit 350)
Topics (12)
Repo already has a shorter About and six topics (
cjk,markdown,paged-media,typesetting,typography,vite). The list above is the GEO-oriented replacement (adds entity + query topics; dropsviteas a discovery keyword). Keepviteif you still want stack-based browsing.Verification
python3 tools/verify.pypassed.editor.ts/ CSS / export changes.