Archbee

The Archbee team cooked in March. Check out our change log (self-powered): https://lnkd.in/dfksgKKa I'll make it quicker: - Archbee meets the Command Line - App Widget Mapping - OpenID Connect (OIDC) Authentication - Inline TeX Support - New supported language: Finnish - Versioning experience improvements - Emails that don't look like 2009 - And much more that we forgot about. More cooking this month.

Writer Agent, Inline Blocks, Detach Content Snippets, Full Scalar import and massive performance improvements in our editor (even for humongous docs) is what we shipped in February. Come get a piece... of the best documentation platforms out there.

Most documentation workflows didn’t start fragmented, they evolved that way. Writing happens in one system, technical review in another, feedback in a third, and publishing becomes a coordinated handoff. Over time, that complexity slows teams down, introduces unnecessary risk, and makes every release heavier than it needs to be. As documentation grows, the lack of a centralized workflow turns simple updates into multi-step processes that drain time and context. In this session, we’ll walk through what a centralized documentation workflow looks like in practice. From drafting and collaboration to publishing and hosting, you’ll see how teams can simplify their process, keep feedback in context, and move from draft to published without juggling disconnected tools. The focus is practical and real-world: how documentation actually gets done, and how it can be done more smoothly. What you’ll learn: - Why documentation workflows become fragmented over time - Where friction appears in writing, review, and publishing - What a centralized writing → review → publish flow looks like - How to reduce context switching without disrupting technical workflows - How teams can scale documentation without adding more tools Who should attend: - Technical writers and documentation managers - Product and engineering teams involved in documentation review - Teams managing growing or multi-product documentation - Organizations looking to centralize and simplify their docs workflow About the speaker: Armando Salazar is a Documentation Success Manager at Archbee with a background in technical writing and documentation architecture. He works closely with growing teams to design scalable documentation workflows that balance structure, collaboration, and ease of use. His focus is helping organizations reduce friction in their documentation process while maintaining clarity and quality as they scale.

Drafts are cool, but branches are chilly. We're shipping a new way to collaborate on documentation, very similar to git. We shipped our GitLab integration (in addition to the existent GitHub and Bitbucket ones) for more options about your source of truth. RSS feeds? We got you with this new release. API docs references with Scalar? It's native in Archbee now. Check out the full change log: https://lnkd.in/dfksgKKa

𝗜’𝗺 𝗰𝘂𝗿𝗶𝗼𝘂𝘀—𝘄𝗵𝗶𝗰𝗵 𝗰𝗮𝗺𝗽 𝗮𝗿𝗲 𝘆𝗼𝘂 𝗶𝗻? Team Google, Team Microsoft, or are you brave enough to stick with Chicago Manual of Style? 👇

Hear ye, hear ye. We shipped some absolutely critical features and updates in November. Portal Dashboards, improved Tables & Link Grid blocks, Doc Actions and more... You won't believe what's next... (and you won't find about it if you don't subscribe to our dogfooded changelog here https://lnkd.in/dfksgKKa). Rockets and puppies.

We've been making the docs-as-code experience much better, and we launched our Visual Studio Code Extension. It helps you create, validate, and preview documentation with integrated linting, snippets, and live preview capabilities. Additionally, it has integrated linting for markdown and mdx, and rich code snippets that help you use our custom blocks (only found in Archbee). Get it today, use it and ship better docs to your customers (and leave us a review on VS Code marketplace). https://lnkd.in/d92y58RU

Most companies treat their API documentation like a high school homework assignment. Done at the last minute. Barely proofread. Handed in with a "good enough" attitude. And they wonder why developer adoption is flat. Here's the truth: Your API docs aren't a feature. They are the entire product to the developer integrating with you. ---- A developer lands on your docs for the first time. They aren't there to read. They're there to solve a problem. They're on a deadline. They're frustrated. They're 10 minutes away from Googling " alternatives." What do they find? A wall of auto-generated endpoints. Parameters with zero context. "Success: 200 OK" (Thanks, super helpful.) They're not looking for a dictionary. They're looking for a map. You just handed them a 1,000-page encyclopedia. ---- This isn't a "docs problem." This is a sales problem. Every second a developer spends hunting for a simple quickstart guide, your "Time to Value" metric ticks up. Every ambiguous error code they have to guess at is a tiny papercut. Every time they have to "contact support" for a basic workflow, you're not just losing their time—you're losing their trust. Bad docs don't just create support tickets. They kill deals. They poison community forums. They are a silent, invisible churn machine. ---- The solution? Stop thinking like a librarian and start thinking like a guide. Your API reference isn't a "cost center" to be minimized. It's your #1 salesperson, working 24/7. It's your most patient onboarding specialist. It's your best-informed support agent. It’s the single highest-leverage tool you have for driving adoption. ---- You don't need more documentation. You need better documentation. Stop: Just listing endpoints. Start: Creating a 3-minute "Get your first API call" quickstart right at the top. Stop: Assuming they know your internal jargon. Start: Writing "recipe-style" guides for the 3-5 most common use cases. (e.g., "How to Upload a File," "How to Generate a Report.") Stop: Hiding examples behind a "click to expand." Start: Using a three-panel layout with code examples right next to the reference (done in 1-click with Archbee). Make it scannable. Make it interactive. Make the "happy path" so obvious a junior dev can follow it at 2 AM. ---- Good docs aren't about what the API can do. They're about what the developer can do with it. Tech Writers & Doc Managers: What's the single biggest win you've had by treating your docs as a product? Or... what's the #1 battle you're still fighting? Let's talk in the comments. 👇

Shippity ship! Meet our new Visual Studio Code extension, fresh out of beta. Your Users can now suggest changes that you just click Approve 😉. New lists for much better UX and editing. Better control of search results using Search Priority. I'll be back next month... You ain't ready!

We are participating at WriteTheDocs Berlin - our second day here is just starting. Come speak to our team about TURNING STATIC DOCS INTO INSTANT ANSWERS. We'll help you build beautiful knowledge portals that are easy to navigate, search, share and contribute to.