We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Emacs lsp repos use mkdocs for our docs presentation like:
Do you think we should use the same pattern for lsp-sonarlint?
lsp-sonarlint
We use this with Github pages and a GitHub action for deploying the docs, example: https://github.com/emacs-lsp/lsp-dart/blob/master/.github/workflows/docs.yml
Any questions, feel free to ask me here or on gitter :)
The text was updated successfully, but these errors were encountered:
Emacs lsp repos use mkdocs for our docs presentation like: * https://emacs-lsp.github.io/lsp-mode * https://emacs-lsp.github.io/lsp-dart * https://emacs-lsp.github.io/lsp-java * https://emacs-lsp.github.io/lsp-metals Do you think we should use the same pattern for lsp-sonarlint? We use this with Github pages and a GitHub action for deploying the docs, example: https://github.com/emacs-lsp/lsp-dart/blob/master/.github/workflows/docs.yml Any questions, feel free to ask me here or on gitter :)
* https://emacs-lsp.github.io/lsp-mode * https://emacs-lsp.github.io/lsp-dart * https://emacs-lsp.github.io/lsp-java * https://emacs-lsp.github.io/lsp-metals
Sorry I didn't saw this issue!
Of course, it is a great idea, I think the new lsp's webpage are great to newcomers 👍
Sorry, something went wrong.
No branches or pull requests
Emacs lsp repos use mkdocs for our docs presentation like:
Do you think we should use the same pattern for
lsp-sonarlint
?We use this with Github pages and a GitHub action for deploying the docs, example: https://github.com/emacs-lsp/lsp-dart/blob/master/.github/workflows/docs.yml
Any questions, feel free to ask me here or on gitter :)
The text was updated successfully, but these errors were encountered: