u/bodiam

Hi all,

Happy to announce that we've released Markdown Pro, a new plugin for the Jetbrains family of products. How does Markdown Pro compare to the bundled Markdown plugin? Glad you asked!

A few new features:

Markdown Pro adds explicit `.mdx` support:

• `.mdx` files open with Markdown editing behavior instead of as plain text.
• JSX component names, attributes, values, and expressions receive editor highlighting.
• Multiline components can be folded, including components whose content contains literal tags in code spans.
• Formatting actions, task-list actions, inspections, tables, and live templates work in MDX-aware contexts.
• Front matter, fenced code, and JSX expressions are excluded from authoring features when applying them would be incorrect.

Also:

Markdown Pro adds project-level rendering choices for:

• GitHub Flavored Markdown.
• Markdown Extra.
• CommonMark.
• Standard Markdown based on John Gruber's original syntax.

Also, the plugin provides document conversions through Morph, enhanced table editing, more inspections, Mermaid, GeoJSON, Interactive Ascii STL models, and much more!

You can find the plugin here: https://plugins.jetbrains.com/plugin/33400-markdown-pro, and while it's a commercial plugin, we currently have a 50% off promo, so you'd basically pay $1.50 for this plugin.

If you have any feedback, would be happy to hear!!

Cheers,

Erik

Hi all, I'm the author of the Typst plugin for IntelliJ, and one of my users had to make a switch from Typst to LaTeX due to the requirements of their university. This was the trigger to create a new LaTeX plugin, LaTeX Pro which support latexmk, Tectonic, pdfLaTeX/XeLaTeX/LuaLaTeX, has features like live preview, 2 way navigation, and more. It's a commercial plugin which allows me to support this plugin now and in the future.

It's a relatively new plugin, so there might be an issue here or there, but if there's an issue, feature request or just general feedback, then I'm happy to hear about this!

In the upcoming release of Toolkit for Cloudflare, we added support for the Cloudflare status dashboard (https://cloudflarestatus.com/) right in the IDE. The reason was that we couldn't connect to one of their services, and we weren't sure if that was caused by us or by Cloudflare (turns out, that of course it was caused by us!).

Anyway, we decided it would be nice to see alerts, statuses, and a history of the status dashboard right in the IDE, so we integrated it. The new release contains a ton of features, like better auth handling, support for most AI services, MCP handlng for code, endpoints, documentation, and a bunch more.

Feel free to try it out, and hit me up with questions if you have any.

I run https://allscreenshots.com, a screenshot API, since the beginning of this year.

Even before launching the product, I obsessed over the usual playbook: the landing page copy, pricing tiers, social media posts, waiting for the magical $ 10k MRR would happen. Instead of an overnight success, it trickled. We got a a signup here, a trial there, but none of the 10k overnight stories you read about (and, which aren't always 100% accurate).

The thing that actually gave us growth was the opposite of what I expected: the people who showed up annoyed. Someone who would try out product would hit a wall. For example, our docs were wrong, an edge case that gave an error 500, a feature they assumed existed and didn't, and fire off a frustrated message.

My instinct from day 1 was to treat those as fires to put out quietly. Apologize, patch, move on, minimize the damage. But above all: I'd reply personally, often from my personal email address. Sometimes I'd ask to hop on a call. It was never to defend the product, but instead to actually understand what they were trying to build and where it let them down. Let's be honest: nobody needs screenshots as their main product, it's always part of a bigger solution. To talk to hour users, and mostly listen, is to understand them better. And any reported issue, I'd fix immediately when I could. I'd fix the doc that day. Ship the missing param that week. Tell them when we working on it, and when it was live.

Almost every one of them converted to paid. It was not because I tried to sell them anything. To be honest, and this might sound strange, but it wasn't even the goal to sell. It was to improve the product, and by contacting them, they got to experience what it's like when the person behind the API actually gives a damn. A frustrated user is someone who cared enough to try to make it work. And the people who care enough to complain, are the people who need the product the most.

So, how we approach things now, is that every bug report is a free conversation with someone who's already decided your product should exist. They've done the hard part: they showed up and tried. All you have to do is not waste it. Now, in no way am I going to suggest that introducing bugs in the right way of doing business, but when there is a user who has issues, try not to get defensive on it; help them, fix things, and understand what they're trying to accomplish. The angry email is the opportunity, and showing you care will make you grow.

It's a slow journey, and def not a a 10k overnight success, but every week, https://allscreenshots.com gets around 1-2 paying customers, resulting in around 500 users with a little over 20 paying users. This is far from a sustainable business, but we're in it for the long run, and we see a slow, steady and accelerating growth in the last 5 months, and let's see where we are in a year from now!

Anyone else find their best customers came in hot?

Hi all, I'm the author of Nix Pro, a new IntelliJ/Jetbrains plugin to support Nix development. It's a commercial plugin to support the future development and maintenance of the plugin. It supports features such as syntax highlighting, templates, formatting (using multiple formatters), refactoring, code inspections, online/offline documentation integration, code completion, etc)

It's still a relatively new plugin so there might be bugs, but I'm aiming to support this plugin for a long time if there's any interest in it.

Feedback, bugs, feature suggestions would all be more than welcome!

Cheers,

Erik

PS: for anyone who reads this, but thinks the price is too high, send me a DM and I'll give you a 50% discount, easy as that.

hi all, I'm the author of the IntelliJ Typst plugin and I'm spending quite a bit of time, passion and enthusiasm into maintaining this plugin.

Typst is a markup language, popular in academic and publishing settings. The plugin provides full-featured Typst support for all JetBrains IDEs, powered by the Tinymist language server.

Yesterday, a big update was released, which makes the plugin far better than before. I believe this to be the biggest update so far, which brings the following changes:

Added

• "Typst root path" setting under Settings > Tools > Typst - sets the root used to resolve absolute Typst paths such as #include "/chapters/intro.typ". Supports ${workspaceFolder} substitution; leave empty to use the project root. See sample-project/root-path-demo/ for an example
• Export to HTML, Markdown and plain text via Tools > Typst (routed through the tinymist language server)
• "Profile current file" action under Tools > Typst - saves a Chrome-compatible trace JSON file
• Code vision bar above .typ files with quick access to Profile, Export, and more actions
• "Create missing variable" intention - quick-fix to insert a #let declaration for undefined variables
• Compilation error overlay in the preview panel - shows inline errors when the document fails to compile, and clears automatically when fixed
• Spell checking now covers comments in addition to markup content
• "Font paths" setting - list of directories recursively searched for fonts. Supports ${workspaceFolder}
• "Search system fonts" toggle - disable to restrict font discovery to the configured font paths
• "Syntax only" setting (auto / enable / disable / onPowerSaving) controlling whether tinymist uses full semantic analysis or syntax-only mode
• "Extra typst args" setting - forwarded to the tinymist compiler (space-separated, supports quoted values and backslash escapes)

Changed

• Tinymist is now downloaded automatically on first use
• Automatic tinymist update check is enabled by default
• "Export output location" setting to export the PDF next to the source .typ file or at the project root
• Settings > Tools > Typst screen is grouped into Tinymist server / Compilation / Export / Preview / Formatter / Advanced sections
• Exported files are now revealed in the project tree after export
• PDF, PNG and SVG export now also run through tinymist, so preview and all export actions work without a separate typst installation
• Removed the separate Typst CLI setting and the Typst compile/watch run configurations
• Export failures now show the actual Typst problem in plain language instead of internal tinymist or Rust error text

Fixed

• Fixed new Typst file template
• Export PDF code lens button now works when the IntelliJ working directory is read-only
• Tinymist download failure now shows a retry hint instead of requiring manual setup
• Profiling now uses the correct tinymist LSP command (getDocumentTrace)
• Custom fonts added through "Font paths" now show up in the live preview, and changing font settings refreshes preview automatically
• Reformat Code now runs your selected Typst formatter (typstyle or typstfmt) and cleans up accidental runs of empty lines instead of leaving the document unchanged
• The Tinymist path field now shows the detected binary path as selectable text instead of placeholder-only text
• Live preview now updates from the unsaved editor buffer instead of forcing a file save on every keystroke, so editor cleanup options such as removing trailing blank lines only run on explicit save

I'm always looking for feedback in terms of bugs, missing features, etc, so if you have any, feel free to share them!

Cheers,

Erik