writerside

Dear friends, with this release we are closing Writerside IDE - but giving you the free Writerside plugin to continue writing, building, and publishing documentation. Details: jb.gg/wrs_no Huge thanks to everyone who used, supported, and believed in Writerside 💜

Our favourite part of the “State of Docs” report from @GitBookIO ? 54% say docs generate as many leads as their marketing site -- while 39% don’t track anything at all. 🤷‍♀️ What stood out to you? 👉 stateofdocs.com/2025/

Friends at @GitBookIO are running The State of Docs survey -- use your voice to prove why docs matter! 💪 🤓 jb.gg/gb_stateofdocs

New Writerside plugin release is here! 🚀 - Set custom last modified dates in topics. - Enable soft wraps in code blocks. - Use custom titles for the 'See also' block and web summaries on starting pages. Update via your IDE - or use JetBrains Marketplace 👉jb.gg/wrs_plg

@martinbonnin Yes, we're closing the standalone Writerside product, but the plugin will remain available for free with JetBrains IDEs. There's no public roadmap ATM, unfortunately, as the development will mostly focus on internal usage needs

@onwriterside I love you but damn those blog posts are hard to decipher. Looks like the standalone IDE goes away but the plugin stays? Is there a roadmap for the plugin somewhere?

Dear friends, with this release we are closing Writerside IDE - but giving you the free Writerside plugin to continue writing, building, and publishing documentation. Details: jb.gg/wrs_no Huge thanks to everyone who used, supported, and believed in Writerside 💜

@OMFGNuts Writerside users can continue working with the plugin, which has the same feature set -- and remains free for all. Software decisions are never easy, and we understand the frustration. We truly appreciate everyone who gave Writerside a try.

The Writerside plugin remains free on JetBrains Marketplace, and you can continue using it with your JetBrains IDE: plugins.jetbrains.com/plugin/20158-w…

💪Help shape the future of documentation Spend 45 minutes with The Good Docs Project -- if you're involved in documenting a software project, they need your insights 🤓 More details in the blog post: thegooddocsproject.dev/blog/ux-resear…

💡Docs with semantic markup are not static - feed them to an LLM and they can suggest precise actions, like shortcuts or buttons to trigger IDE features. See how JetBrains used this in their AI Assistant. Kudos to @flounder4130 for sharing! flounder.dev/posts/rag-sema…

@PV28638 Not at the moment - we currently support only copy mode. However, this is something we’re considering adding to our roadmap for this year, even for the GA release. I’ve created a ticket: youtrack.jetbrains.com/issue/WRS-6787… Feel free to track its progress and share your feedback!

Thanks for the quick reply. Another question I have. I have works with multiple subfolders each of them containing markdown files. Is it possible to use onwriterside to aggregate these markdowns by their root folder, WITHOUT copying them inside onwriterside's folder, but instead the changes to be committed directly on the original markdown files in their folders? The issue here is that I don't want to duplicate the files (which are under their own version control, or are linked already elsewhere), but instead use the onwriterside as aggregator S/W just for gathering and displaying these files together and/or editing them in place. Is this possible? May I have miss this functionality?

Including code snippets in docs? 🤓 Soon, you’ll be able to reference code outside the documentation module - just like this 👇 #nextEAP #SneakPeek

@PV28638 Also, if you prefer to edit content directly in preview mode, this issue might be relevant to your needs. It’s about adding WYSIWYG support in Writerside: youtrack.jetbrains.com/issue/WRS-3104…

Hi. I was testing this S/W just now. Is it's possible to open the MD files from OnWritterSide IDE with our own external Markdown editors? So something like right-click in a topic (which is an MD file eventually as I get) and then click "Open external.." and this to call our default MD S/W (ie I use typora) and edit everything there? Personally I don't like at all to have two windows (edit/preview). I prefer to work on the preview directly (like typora) and when required to return to edit mode for fixes/whatever. Is there any case to implement such a feature?

Our partners @thegooddocs have just released 🥇 A new Changelog template 🥈 An updated Release Notes template 🥉 Improved template standardization Use them now in Writerside: 👉 In the WRS tool window, click + → Topic from Template, et voilà! jb.gg/tgdp

@kataokatsuki Hi, @kataokatsuki. Hope this will make your day a bit brighter — we've fixed this sneaky bug with invoking the Save image dialog youtrack.jetbrains.com/issue/WRS-6138 Please, update 🫂

Writerside 2024.3 eap来た！ と思ってウッキウキでバージョン上げたら、まだd&dバグ直ってないようで血の涙を流している youtrack.jetbrains.com/issue/WRS-6138

New Writerside Early Access release – with more goodness for content reuse 🚀 ✂️ Dedicated view for snippet libraries 🗂️ Folders for topics in the Table of Contents 🛠️ Fixes for GitHub Action, API docs generation, XML schema, and more! Download: jb.gg/writerside

JetBrains #AI #Assistant now understands Writerside! If you have a question about markup or a specific feature and have the JetBrains AI plugin, you can 👇

@sumihiran Thank you for your detailed feedback! 🌟 Exposing a Writerside API for custom exporters is a good idea, especially as we’re exploring more output formats like Confluence. While it’s not in our immediate plans, we’ll consider it as we evaluate future plans.🙌

@onwriterside is a great step toward keeping tech docs close to the source—better than markdown and DIY libraries. It brings features making it a go-to tool for technical documentation. But like many organizations, we love Confluence. Without an ADF exporter, that's not a reality

@thejarodparker @jetbrains Thank you so much for sharing your thoughts! We’d love to understand more about your ideal workflow- when you mention a built-in solution, what platform or tool do you envision it being integrated into?

@onwriterside @jetbrains General thoughts: I don't primarily do documentation, but I did find it useful in writing better documentation. I also really like the font. However, I'm not sure I'll really integrate it into my workflow, as it's yet another application to open. I'd prefer something built-in.

Testing out @jetbrains Writerside for the first time. We'll see how it goes.

@pixelsnob 🎉 Glad to hear the update made a difference, Alex! Rest well! 😊 We’re always looking to make the SEO process for docs even smoother - if you have any more ideas or feedback, feel free to share.

@siedlerchr That's awesome to hear! 🎉 We're happy that you're using it for your customer API documentation. If you have any feedback or ideas on how we can improve the API docs, we’d love to hear it! 😊

@onwriterside Oh nice! Will update asap! We already use it for the customer api documentation of one our projects

Ta-da! The new Writerside Early Access release is here 😎 Highlights: - Code blocks (quick demo below!) - API docs generation improvements - PDF via builder …and _much_ more! Full list here 👉jetbrains.com/help/writersid…