quicktile VS sphinx

You might wanna have a look at quicktile. It's basically an addon that adds tiling to existing WM. Works well, but lacks some of the intrgrations dedicated tiling WM have.

As the author of QuickTile, which is written in Python but even closer to what you describe than a window manager would be, I have to say that, yeah, doing X11 stuff takes a lot of knowledge that's not ideally documented in non-print sources.

quicktile is a handy tiling tool which saves me a lot of time. native custom tiling is always better tho

It's been a long time since I bothered with this functionality, but I seem to recall that quicktile was a better fit for me than those other two. Not sure if it's still viable.

Actually, I plan to add a .nojekyll file and then use something like Pelican with custom plugins, then set GitHub Actions to run my update.sh on push... similar to how http://ssokolow.com/quicktile/ is a Sphinx-based site hosted on GitHub Pages and automatically regenerated from the pushed sources.

I've been using ssokolow.com/quicktile for this purpose, it does what I need and doesn't replace the wm.

If you're into using shortcuts I would recommend installing Quicktile for manage your windows: https://github.com/ssokolow/quicktile

you can try quicktile

The best I could do for the API documentation for this project of mine was to use the automodule directive to autogenerate at the coarsest level possible and remember to never create new .py files if I could possibly avoid it.

Sphinx is primarily known as a documentation generator, but it can also be used to create static websites. It excels in generating technical documentation, and its support for multiple output formats, including HTML and PDF, makes it a versatile tool. Sphinx uses reStructuredText for content creation and is highly extensible through plugins.

Sphinx a documentation generator or a tool that translates a set of plain text source files into various output formats, automatically producing cross-references, indices, etc. That is, if you have a directory containing a bunch of reStructuredText or Markdown documents, Sphinx can generate a series of HTML files, a PDF file (via LaTeX), man pages and much more.

Notable mentions to [Sphinx](https://www.sphinx-doc.org/). It's workflow is more tuned to the "book" format rather than the blog, forum or thread format.

Currently trying out Sphinx (https://www.sphinx-doc.org) and the trying to get the autodocgen feature to see what that can do.

So, I've documented my code and now I need a .PDF with this documentation. Is there any easy way to do it? Once I used Sphinx but it generated a not so easy .TeX.

AutoPyTabs allows you to write code examples in your documentation targeting a single version of Python and then generates examples targeting higher Python versions on the fly, presenting them in tabs, using popular tabs extensions. This all comes packaged as a markdown extension, MkDocs plugin and a Sphinx, so it can easily be integrated with your documentation workflow.

Honestly, I think it's just an issue of documentation. For example, if there was an easier way to document @overload functions, that would help (cf. https://github.com/sphinx-doc/sphinx/issues/7787)

We use sphynx for our pipeline documentation for all technical details Classes , packages and functions docstrings using reStructuredText (reST) format

I like Sphinx [0] with the MyST Markdown syntax [1]. There is a related project, Myst NB [2], which enables including Jupyter notebooks in your site. There is also a plugin for blogging [3].

[0]: https://www.sphinx-doc.org

Sphinx is the go-to tool for documentation. It took me a while to understand how to use Sphinx, but I now have a decent workflow with MyST which allows me to write all the docs in markdown. My sphinx-markdown-docs repo shows an example of what I do.