kotlin4example
furo
kotlin4example | furo | |
---|---|---|
1 | 7 | |
15 | 2,466 | |
- | - | |
6.0 | 8.6 | |
about 2 months ago | 7 days ago | |
Kotlin | Sass | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kotlin4example
-
Technical documentation that just works
This tool seems like it is a nice markdown based CMS but I don't see too many features related to the more difficult parts of doing technical documentation. Like having working code samples.
I attempted a Kotlin centric documentation framework a while ago to address this: https://github.com/jillesvangurp/kotlin4example
I mainly use it to generate the documentation for my Elasticsearch Kotlin Client (jillesvangurp/es-kotlin-client). The idea there is that all examples and source samples are correctly compiling Kotlin code that I can get the output of when they run (e.g. a println). Running the tests, actually generates the documentation markdown. Using a dsl and multiline strings, I can mix lambda code blocks, markdown, or markdown inside files. For the lambda blocks, it figures out the source and line numbers using reflection. But it can also grab source samples based on comment markers. For bigger blobs of markdown, it's easier to grab the content from markdown files. For smaller sections of markdown, I can use inline multi line strings or a Kotlin DSL.
The main benefit of this is that my examples update as I change and refactor the code base. Also, since it runs as part of my tests, I know when examples break.
furo
-
Can someone help me understand "documentation generators" and the purpose of Sphinx?
Sphinx has more and in my opinion better themes (especially the popular Furo them). I also think it's better for handling large and complex sites. It's way more extensible. That there are far more Sphinx users means that you're more likely to have community support if/when you run into issues.
-
Can you select themes for rustdoc?
My company uses sphinx, in particular the furo theme: https://github.com/pradyunsg/furo. I'd like to use something like this to start documenting our Rust repositories. Is this possible on stable?
-
[D] What JAX NN library to use?
On another note, what did you dislike in Sphinx ? I found it pretty easy to work with until now and there are quite nice themes, like Furo (https://github.com/pradyunsg/furo), which is actually pretty similar to your current docs theme. I used it recently for one of my projects (see https://francois-rozet.github.io/piqa/piqa.psnr.html).
-
New Sphinx theme
reminds me a lot of Furo which is used by big names such as urllib3, pip, attrs, psycopg3, black
- Furo: A clean customizable documentation theme for Sphinx
- Technical documentation that just works
-
Furo – A clean customizable documentation theme for Sphinx
This theme was created by one of the maintainers of pip, which is where I first saw it (https://pip.pypa.io/en/stable/). Here are some of the things I like about it:
- Well-chosen, proportionate font sizes and spacing.
- Table of contents sidebars for both the current page and the whole documentation site.
- Fully responsive: sidebars disappear in narrow windows or small screens, but can still be popped out.
- Clean color scheme with good contrast, and full support for dark mode (see screenshot at https://github.com/pradyunsg/furo/blob/main/README.md).
What are some alternatives?
ltex-ls - LTeX Language Server: LSP language server for LanguageTool :mag::heavy_check_mark: with support for LaTeX :mortar_board:, Markdown :pencil:, and others
mkdocs-material - Documentation that simply works
fastapi - FastAPI framework, high performance, easy to learn, fast to code, ready for production
sphinx - The Sphinx documentation generator
mike - Manage multiple versions of your MkDocs-powered documentation via Git
mkdocstrings - :blue_book: Automatic documentation from sources, for MkDocs.
vscode-theme-alabaster-dark - Dark version of alabaster ported from https://github.com/tonsky/sublime-scheme-alabaster
crystal-book - Crystal reference with language specification, manuals and learning materials
PVEDiscordDark - A Discord-like dark theme for the Proxmox Web UI.