Python environment tools for Visual Studio Code
Performant Python environment tooling and support, such as locating all global Python installs and virtual environments.

Environment Types Supported

• python.org
• Windows Store
• PyEnv
• PyEnv-Win
• PyEnv-Virtualenv
• Conda
• Miniconda
• Miniforge
• PipEnv
• Homebrew
• VirtualEnvWrapper
• VirtualEnvWrapper-Win
• Venv
• VirtualEnv
• Python on your PATH

Features

• Discovery of all global Python installs
• Discovery of all Python virtual environments

In a previous article, we established that content is sovereign, which means the site generator needs to gather content from various repositories and branches. In order for the generator to identify, aggregate, and catalog content partitioned in this way, the repositories must present a consistent structure. Otherwise, the generator isn’t going to know which files represent pages or which pages should be grouped together.

This plugin is designed to help to publish your Antora docs into Confluence. The main reason is, that we want to have a single source of truth for our documentation. We want to write our documentation in AsciiDoc and publish it to Confluence as some of our Stakeholders are using Confluence.

The captain offers the following options:

• Publish your whole Antora docs to Confluence
• Publish only selected pages/ folders, by using filters
• Control where the docs should be published by setting an
  overall parent page in Confluence
• Decide if you want to inform your readers that those pages are
• generated by automation by applying a banner.

You’d think an intuitive system for creating links between pages would be a central feature of every site generator. After all, that’s kind of what the web is all about. Sadly, it’s often an afterthought.

The current mechanisms tend to distract from writing. Each time you want to make a link to another page, you have to pause to compute a relative path and/or transform the path to a published URL in your head. If you move the page you’re editing, it may cause the relative path to shift, which means you have to go back and recompute those references.

It’s no wonder writers create broken links at an alarming rate or spend excessive amounts of time fixing broken links left behind by other writers. But we can’t fault the writers when it’s the system itself that’s broken. Let’s figure out a solution.

Ship your documentation as fast as your product.

We provide tools and workflows that help teams coordinate documentation initiatives across products and departments.