The generated API reference — every type, every member, the class and collaboration diagrams, the include graph and the per-function call and caller graphs — lives at /static/api/index.html.
It is produced by Doxygen from the annotated headers under libs/internal/sdk/fson/ and the fson-check source. The vendored cparse parsing core is documented separately at cparse.fedem.eu.
For a narrative, human-written companion, read the Reference Manual. It covers the same public surface — the Fson façade, the document model, the parser, the writer and its dialects — but with the why: when a query returns nothing versus throws, what the -- prefix does to a walk, how %include provenance is tracked, which dialect drops which information. Read the reference for orientation, read the Doxygen tree for exact signatures and the graphs.
Which one am I looking at?
| Question | Where to look |
|---|---|
"What is the exact signature of Object::setPath?" | Doxygen › Object |
"Why did getInteger return my fallback?" | Reference › Object — query API |
"What does DisabledMemberPolicy::ConvertToComment emit?" | Reference › FsonWriter — DisabledMemberPolicy |
| "What is the grammar for a bare key?" | Notation › Keys & bare names |
Generating the docs yourself
With fson checked out and Doxygen installed, the CMake target docs produces the HTML tree under build/docs/html/:
cmake -B build
cmake --build build --target docs
xdg-open build/docs/html/index.html
Or through Conan: conan build . -o "&:with_docs=True" -o "&:with_tests=False".
Graphviz dot is picked up automatically when present and enables the class / collaboration / include / call / caller graphs; without it Doxygen falls back to its own simple inheritance diagrams. The same output is uploaded here at each release.
