Current status: Updating the https://thi.ng/geom readme to give a better overview of the full extensive API, ahead of the v8 release (soon)... Attached are screenshots of three sections of the readme showing:
list of 32 shape types (both 2D and 3D)
list of 54 polymorphic functions/operations to manipulate/convert/analyze shapes & shape hierarchies
list of additional 40 shape creation functions
Still to come: Documenting the bundled preset implementations of:
vertex convolution kernels (3)
curve subdivision strategies (8)
polygon/polyline to bezier conversion strategies (3)
polygon tessellators (9)
(...and how most of these can be combined & applied iteratively. Some of the recent/existing examples are already hinting at the potential...)
I'm investigating options that are available to create a table of contents in #markdown, really wondering what people are using to create that when writing markdown based docs.
@dantleech that means that you do not have any influence on the order of the chapters? And all headers are included? Or can you specify the maximum level?
I do completely understand that you prefer RST as it is much more powerful and easier to extend with custom syntax. The reason why I'm looking for a way to build a TOC is because @phpdoc users do request for it.
@jaapio@phpdoc depends. You can have per article TOC, or you can ... iterate over a set of pages, order them by whatever (anything in the front matter e.g. weight) and (probably) pull the header structure from them. It's essentially the save as the navigation.
I found that you can pretty much do anything in Hugo, it's just way less elegant than RST/Sphinx!
I really hate haddocks' eyes in code #documentation 'Defines the Foo class', 'Provides an implementation of the foo plugin'. No. It IS the Foo class. It IS the foo plugin.
Why didn't anyone tell me about https://devdocs.io? You convert the site into a web application, enable the packages you need, download for offline access and enjoy fuzzy search, speed and smooth operation for free.
phpDocumentor 3.5 is here! With better Guides support and now fully functional RST! Automatic generated class diagrams by querying your code base and much more!
The series provides an #InDepthAnalysis of the idea that human rights violations, armed conflict & #war cause #psychological & #psychiatric outcomes, using the Kingdom’s tragic past to explore themes.
A young developer who never used Windows 98 back in the day stumbled upon an introductory book on the operating system and posted his impressions on skimming it, which brought him joy. He wrote:
"I was also left with the impression that perhaps I would like more software to come with a physical manual."
Hey if you want to discuss anything about #documentation please sign up at the board at the #DocSummit (room 317) - you can also sign up for lightning talks (documentation related)
Interesting. Several Canonical projects are using Discourse as their #documentation platform.
As with documentation using wikis, it's nearly the opposite of Documentation As Code. Instead of benefiting from a relationship between documentation, the software, its versioning and CI platforms, it builds a direct relation between documentation, support and community.
Would be nice to have a LLM that you can train locally with your organization documentation, to be able to have an interface to easily find that information buried in decades of documents #LLM#MachineLearning#documentation#FOSS