Skip to content

docs: slim the readme down and point at the gitbook space - #105

Merged
TheMeinerLP merged 5 commits into
mainfrom
docs/link-gitbook
Oct 10, 2026
Merged

TheMeinerLP merged 5 commits into
mainfrom
docs/link-gitbook

Conversation

@TheMeinerLP

@TheMeinerLP TheMeinerLP commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

Proposed changes

The documentation now lives on the GitBook space at https://docs.onelitefeather.net/falco, and the GitHub wiki is gone.
This PR points readers at that space and cuts the README down to a front door for it:

  • Links from the README, CONTRIBUTING.md, falco-demo/README.md, the issue forms and the pull request template now point at the matching GitBook page. Every target was checked with curl and returned 200. Links inside docs/ are unchanged.
  • The README drops the module descriptions with claims, the benchmark section with its provenance lines and tables, and the API tour. Its content is either already in docs/ or was moved there in the second commit. The quick start keeps the release-please-marked dependency block unchanged and gets the tutorial's runnable example.
  • Missing content moved into docs/: scheduler and builder settings, the Anvil builder and diagnostics, the generator example, the Minestom version caveat for the measured results, and the pre-1.0.0 superclass constraint.

Types of changes

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Performance change (behaviour unchanged, cost changed)
  • Documentation Update (if none of the other choices apply)

Checklist

  • I have read the CONTRIBUTING.md
  • The title of this pull request is a Conventional Commit
  • I have added necessary documentation (if appropriate)

https://claude.ai/code/session_01Q6AxU7jRLmNPHdwg2GpasT

After merge (not verified yet)

GitBook syncs main only after the merge, so these URLs cannot be checked from this branch. Run them once the space has synced; the status codes are the expected results.

  • curl -sS -o /dev/null -w '%{http_code}' -L https://docs.onelitefeather.net/falco/how-to expected 200 (today 404; live only as how-to-guides/how-to)
  • curl … /falco/project-record/research expected 200 (today 404; live only as project-record/project-record/research)
  • curl … /falco/benchmarks expected 200 (today 404; live only as contributing/contributing/benchmarks)
  • Samples, expected 200: /falco/how-to/add-falco-to-your-build, /falco/reference/measured-results, /falco/contributing/benchmarks-and-demo
  • If an index page is still 404 while its sample pages are 200, add a redirects entry in .gitbook.yaml only after confirming the target URL.

The README repeated most of the gitbook space: module descriptions with
claims, a benchmark section with provenance lines and tables, and an API
tour. It now keeps the badges, a short description, a feature list linking
to the gitbook pages, the quick start and links into the four documentation
parts.

Content that existed only in the README moved into the gitbook space:
- how-to/keep-chunk-light: scheduler builder settings, markChanged/markDirty,
  the ChunkLightListener route on an InstanceContainer
- how-to/load-an-anvil-world: builder settings, diagnostics, regionDirectory,
  legacyLayout, openRegionCount
- how-to/use-falcoinstance: generator example and palette copy semantics
- reference/measured-results: the Minestom version and the 26.2 caveat
- explanation/why-falco-instance-exists: the pre-1.0.0 superclass constraint

Claude-Session: https://claude.ai/code/session_01Q6AxU7jRLmNPHdwg2GpasT
@TheMeinerLP
TheMeinerLP requested a review from a team as a code owner October 10, 2026 20:11
Four modules are published (falco-anvil, falco-light, falco-instance,
falco-migration); the BOM covers three of them. The experimental note
now says "all published modules", and the README lists world migration.

Claude-Session: https://claude.ai/code/session_01Q6AxU7jRLmNPHdwg2GpasT
Nested list items under a README were turned into deeper URLs on the
published space: the research index is only served at
/falco/project-record/project-record/research, and nothing resolves at
/falco/project-record/research. GitBook's Git Sync guidance asks for the
README as a top-level sibling with flat bullets under group headings, so
the project record section now follows that shape. Only the section's
own URLs change; each page also resolves at its file-path URL.

Claude-Session: https://claude.ai/code/session_01Q6AxU7jRLmNPHdwg2GpasT
Each group in SUMMARY.md now lists its folder README first and the pages
as sibling bullets below it, following GitBook's guidance for summaries.
Nested bullets under a README produced doubled navigation URLs such as
reference/reference/... and contributing/contributing/benchmarks; the
plain file-path URLs that external links use already resolve.

Claude-Session: https://claude.ai/code/session_01Q6AxU7jRLmNPHdwg2GpasT
@TheMeinerLP
TheMeinerLP merged commit 5a4be00 into main Oct 10, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant