Try   HackMD

mkdocs path

Migrating DevTools projects from Sphinx to MkDocs.

The good

  • Natively supported by RTD
  • Best theme for documentation material-docs
    • Very actively maintained
    • Also commercial plans and features
  • Python based
  • Popular, mkdocs itself 16k stars and materialk theme 13k

The bad

  • Main project lacks leadership
    • But it looks stable
  • Lots of plugins
    • Most under personal github accounts
  • Community health
    • mkdocstrings vs material-theme
    • some from original mkdocs team left
  • monorepo plugin by Spotify stuggle

Interactions so far

  • material theme - 🟢 very good
  • mkdocstring - 🟢 very good
  • mkdocs - 🟡 ok-ish
  • monorepo plugin - 🟠 poor
    • zero feedback from Spotify folks
  • markdown-exec - 🟢
  • other plugins… (TBD)

Challanges

  • Monorepo plugin (single site conslidation)
    • Navigation with monorepo
    • File inclusion
    • Speed at scale (❓)
    • Top right github links not pointing to project
  • Search scalability?

Ecosystem

Last changed by 
 
Sorin Sbarnea
Ansible DevTools Team Lead
0
1
173

Read more

Molecule driver culling of 2023

As part of the effort to revive molecule project some drastic measures were put in place. Unmaintained drivers archived on January 5th, 2023: openstack, goss, libvirt, alicloud, vmware, digitalocean, kubevirt, lxd, inspec. Anyone wanting to revive and maintain one of these will have to make a pull request against molecule-plugins repository. The relatively active drivers were moved to molecule-plugins repository, where we expected them to be maintained by the community. Which drivers should we still see in addition to delegated? azure docker containers

Jan 8, 2023
Ansible Code Extension stats

Operating System src pie title Operating System "windows" : 1993 "linux" : 2729 "macos": 2488 Flavours src

Jan 6, 2023
ansible-lint runnimg modes

Current online offline Future - running modes realtime # vs extension mode, really fast quick # from the CLI

Dec 7, 2022
Reviewer guidelines

That is an early draft, so please add comments or correct errors directly. Keep in mind that your role is to prevent new bug introduction or lowering the existing code quality. As a reviewer you are there not to prevent or delay a change but to help it succeed. Avoid mirroring other reviewers. You are not adding much value if you wait for other to act act first and only agree with them. If you do not find yourself able to review a particular change, just mention it via a comment and remove yourself from the reviewers list, potentially mentioning those that should be able to do it.

Sep 29, 2021
Read more from Sorin Sbarnea
Published on HackMD