The documentation
When the book is read, the documentation takes over. It is generated from the library itself: every class explains its own methods, so the documentation cannot drift from the code.
The whole scope, area by area
Every area of the platform has its classes in the reference. Pick an area to open its page: what you can do there, a run example, the narrations about it, then its functions grouped by what they do, each with its own explanation, and its classes. The colour on the left of each entry is its theme.
Four ways in
The reference
575 classes and 18,561 methods, each with the explanation the library gives of itself, by area and from A to Z. Generated, never hand-written; 1,177 methods also have an entry with examples run inside the library, graded by purpose.
How-to
Twenty-eight recipes, each answering one "how do I…?" with one block of code: lists, numbers, strings and text. Every one was run inside the library and printed what it promises; each links to the methods it uses.
The narrations
135 documents that tell the library as stories in code, from the mental model to the agents that cannot hurt you. Each is a page here, and each says which of its blocks kept their promise when it was run for this site.
The areas
Twenty-eight areas, each with what Softanza rethought, its code run, and its lanes rated against the leaders of its category.
The Softanza way The library documents itself. An object answers with its own methods, explains each one, and says how; this documentation is that answer, collected and published, not a manual written beside the code.