UPD: we have found the first candidate who is ready to take the ownership of the plugin. However if you are interested in to take another plugin, please let me know via email (mikhail.veselov@jetbrains.com) and we will try to find another one. Thank you!
Hello everyone,
PyCharm previously had a plugin providing support for reStructuredText files.
Unfortunately, JetBrains has discontinued active maintenance of the plugin, and it’s now unmaintained.
Given that .rst remains a key format in the Python documentation ecosystem, we’d like to see this plugin live on.
We’re currently seeking developers or organizations interested in the maintenance and further development of the ReStructuredText plugin.
If you are interested, please send me a message to mikhail.veselov@jetbrains.com to discuss the opportunities and next steps.
Thank you!
1 Like
I would like to propose an alternative: Create a new plugin for the rST language server Esbonio. Better yet, since 2025.3 EAP 6 added native support for Ruff, ty, BasedPyright and Pyrefly, it might as well support Esbonio. Someone asked for this two years ago.
A small catch is that there will need to be a “preview” feature, something LSP does not have (the VS Code extension implements its own).
I’m aware LSP is not a replacement for native features. Regardless, this will be far cheaper a solution than rewriting the old plugin from scratch.
I’m just curious. Why did you stop the maintenance for this plugin?
Thank you! Shared the proposal with the PyCharm team
@Mikhail.Veselov - I’m not sure if you’re aware or not, but there is a similar ask from the community about the Mermaid plugin 
https://youtrack.jetbrains.com/issue/MERMAID-190/Update-Mermaid-support-to-v.11.0.0
I’d personally love to see JetBrains hand the source for the Mermaid plugin over to the community for maintenance (I’m a very active user of Markdown and Mermaid) - I wonder if the community got a “two for one” deal (that is, took over maintenance of both restructuredtext and Mermaid; both of which are docs-related plugins) you’d find more folks interested. At the very least, I’d be more inclined to raise my hand - a lot of the plugins I’ve authored haven’t had new features in a while, but I’ve been maintaining them and trying my best to keep them up-to-date with the latest releases.
The plugin has been very useful, but over time it became clear that our teams wouldn’t be able to give it the attention and care it deserves. Rather than letting it go stale, it’d be best to pass it on to someone from the community who’s closer to this area and can help it grow further.
Thank you for bringing up the Mermaid plugin and the link to the issue!
It looks like a great idea of approaching both plugins as a “docs-focused”.
Can’t make any promises yet, I have to discuss it internally first.
As for the Mermaid plugin - I talked internally, and unfortunately, this plugin can’t be transferred outside the JB. The plugin’s code includes parts that can’t be open-sourced or shared. Sorry, but the Marketplace and Platform teams can’t help with this one 