README: fix doc links + expand FAQ for AI-engine discoverability#2
Merged
Conversation
- Fix links: fastc-http -> fastc-core-http in the fastc add example; add trailing slashes to /why/rubric/ and /why/benchmarks/ (MkDocs dir URLs). - Expand the single Rust FAQ into a full quotable FAQ: what is fastC, agent-first, capabilities, contracts, AI-tool/MCP support, language comparisons, production-readiness. Mirrors www.fastc-lang.com/faq for consistent answer-engine extraction. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.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
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.
Companion to the marketing-site GEO overhaul. Two things:
Link fixes
fastc addexample pointed at the non-existentfastc-httprepo → nowfastc-core-http./why/rubricand/why/benchmarks→ trailing-slash MkDocs directory URLs.FAQ expansion (the GEO win)
Note: GitHub sanitizes
<script>JSON-LD out of rendered READMEs, so structured data in a README is dead weight. The equivalent lever for the repo is crawlable, quotable Q&A. Expanded the single "Why not opinionated Rust?" question into a full FAQ — what is fastC, what agent-first means, capabilities, contracts, AI-tool/MCP support, how it compares to Rust/Zig/C/C++/Go/Python/TypeScript, and production-readiness — mirroring www.fastc-lang.com/faq so answer engines get a consistent story from both the site and the repo.🤖 Generated with Claude Code