docsite VS vscode-ansible

Before we add the redirect we'd like to get your feedback. Please leave a comment on the pull request or head over to the docs channel on Matrix and let us know your thoughts.

Hopefully you've noticed that the "docs.ansible.com" landing page has a different navigation. We've updated it to focus on user journeys so users can find support from Ansible docs more efficiently. There is still lots to do and we'd love to hear from you! Do you have ideas about new user journeys? Do you see any content gaps? Are there things you'd just like to change? Send a PR or open an issue in the ansible/docsite repo and help us keep building better content journeys for the community.

We've just refreshed the layout on docs.ansible.com to include quick and easy links for most visited doc pages. You can find the new "Quicklinks" section on the index, user, developer, and maintainer pages. We want to hear from you, especially if you have a killer suggestion for a quicklink, so open an issue in the ansible/docsite repo.

You might have noticed that "docs.ansible.com" has a different layout. That's because we've revamped it to focus on user journeys so that users find what they need from Ansible docs more efficiently. There is still lots to do and we'd love to hear from you! Do you have ideas about new user journeys? Do you see anything missing from the new docsite? Are there things you'd just like to change? Send a PR or open an issue in the ansible/docsite repo and help us make it even better.

Come join us and help build a new docsite! The community team has been working to update the Ansible documentation landing page based on a set of user journeys. Right now we're working on a prototype docsite to improve the navigation and user experience.

The community engineering team has put together a first set of user journeys for Ansible docsite personas and would like your feedback. You can find the user journeys in GitHub.

The ansible/docsite repo is now public, giving the Ansible community full access to all the html and navigation assets that go into docs.ansible.com. Fork the repo and start hacking.

The place to open issues for the plugin https://github.com/ansible/vscode-ansible

Projects to make it easier to write and test Ansible Content. Includes VScode extension, language server, ansible-lint, molecule, ansible-navigator and potentially other development goodies. To see what's planned, and how you can help checkout the foundation-devtools project board

Ansible-VSCode extension 2.0.0 is out!

Si cela ne fonctionne toujours pas, soulève un problème Github ici https://github.com/ansible/vscode-ansible ou https://github.com/ansible/ansible-language-server avec des détails comme :

I asked the devtools team and here is their reply: "The telemetry data is sent to the Red Servers and are not publicly available. Though we have documented the usage data that we gather here."

Best place to read the changelog is at https://github.com/ansible/vscode-ansible/releases but marketplace only links to the embedded changelog file, which is not as good as the github releases page (hyperlinks,...)

Ansible extension for vscode/codium

Projects to make it easier to write and test Ansible Content. Includes VScode extension, language server, ansible-lint, molecule, ansible-navigator and potentially other development goodies. To see what's planned, and how you can help checkout the foundation-devtools project board

For example one recent bug we found is that defining ANSIBLE_FORCE_COLOR=1 can prevent the extension from working. I do expect that a number of ansible users to configure that in env or in their ansible.cfg file,... Details https://github.com/ansible/vscode-ansible/issues/373 -- we plan to release a fix later this week for this one.

DevTools ↗