New publish workflow for preview links

We have received your feedback!

Preview links are a great opportunity for your team to review and give feedback on the work being done. We recognized this when we built the feature, but every change you made went automatically to these links. Because unfinished work went there, it wasn't ideal for reviewing.

We've now changed it, and preview links work exactly like production (with domain) links.

Hit publish, copy the link, send it to your teammates, get reviewed and suggested changes applied, then hit publish to production!

Happy documenting!

πŸ‡ΊπŸ‡¦ New publish workflow, Spaces and more πŸ‡ΊπŸ‡¦

Some changes we've made to allow a better user experience.

1. Staging becomes Preview

Our Staging environment has been renamed to Preview environment and is now publishable — just as the Production environment. Now everybody can preview their documentation sites BEFORE setting their domains — a huge time saver.

On top of that, the Preview environment is now authenticated by default for users already authenticated in Archbee. This makes it possible to create your documentation site privately and make it public only when it's ready, and you've configured it for Production.

2. Collections become Spaces

For many people `Collection` does not reflect what we mean.

Now Spaces, collections were meant to be the first layer of document organization. Spaces sound more familiar from similar software that's focused on internal documentation.


  • Documents are organized into Spaces;
  • Spaces are organized into Sites (which we'll introduce shortly).

3. Workspaces become Orgs

Our Workspaces feature allows you to use a single login to be in the context of multiple companies, negating the need to re-login with another account. 

This is great. However, many users get confused by the concept, buy a subscription and assume it's for all Workspaces they create. Each workspace has its own subscription because what we really mean by workspaces is "organization". 

We considered a switch to "Teams" but we realized it could also mean that there are separate teams in an organization. So we're making this semantic change to reflect that.

4. Code Editors Update

All code editors have been updated to allow multiple tabs using the same language, drag and drop to reorganize tabs, and performance improvements.

5. Better Markdown converters

We've made a bunch of modifications to our Markdown converters and now they catch more of our custom blocks, that were previously hard to translate to markdown. For example, our Link Blocks and Tabs now translate to a custom Markdown directive, that we understand and other software can easily be made to understand.

6. Removing favorite collections (now spaces)

The favorite collections (now spaces) feature has been removed, for various complicated reasons. You can still drag and drop spaces to organize them as you see fit, potentially putting spaces you care more about at the top of your list.

7. Lots of UI changes and improvements

We've reorganized many things around the UI to build a better user experience.

Cheers from the fearless Archbee team, meaning is not afraid to deploy to prod on Fridays or any other day 💪

At least that we can do to feel 0.1% as brave as Ukraine people.

#WeAreWithUkraine 🇺🇦

Product docs site templates, Stripey template beta

Building product docs sites in-house is... time-consuming, de-focusing engineering from the product, error-prone, and... expensive. And in the end, you still lack a nice-to-use CMS for your writers and have to pay for hosting and a search solution.

You can always buy a solution on the market, but there's a big drawback: most solutions don't offer that much customization.

We noticed this a while back and allowed our customers to customize pretty much everything with custom CSS, and custom JS.

While good for many companies, it doesn't seem to be enough for some. 

This is why we've built an entire system that allows us to build documentation site templates very quickly. It's here!

We've also launched the first template for it (beta) — Stripey. Stripey uses Stripe's docs (which is beloved by many developers) as inspiration.

Here's how it looks like on our own docs:

Of course, you still get all the goodies: dark mode, ultra-fast and reliable search, search analytics, authentication options, and rich SEO controls.

Try it out on your docs and let us know what you thought.

Here's what we have planned next for the product documentation sites use case: 

- GitHub Integration (write your docs in GitHub — then use Archbee to generate the site and host it);

- Multi-product sites (use multiple collections on the same site with a tab-switcher similar to Stripe's docs);

- New blocks, many inspired by Stripe's custom made docs;

- i18n;

- Collections as changelogs hooked into the main doc sites.


50+ improvements

As promised to many of you, we're focusing on improving the functionality we already have as opposed to adding new stuff. 

We've improved the performance of the app, the design system, our libraries & code, the self-service abilities of the system.

Here are some highlights:

  • custom HTML with handlebars templates in custom footers or custom landing pages for documentation sites; read more here:;
  • improved image rendering; we've changed our CDN for images with one that renders sizes dynamically and allows people with smaller screens (e.g mobile) to download the exact size of images they need; we also changed the way image widths/heights are calculated so no layout shifting will happen anymore;
  • user downloadable invoices; download any invoice on demand so that you don't have to look for them in your email;
  • ability to appoint a new super admin; this also changes the email that Stripe sends invoices to;
  • ability to change email address by yourself;
  • UI improvements all over; we've tightened our design system even more; more consistent colors and spacing;
  • better automatic scrolling in the document tree section;
  • improved search algorithm and faster instances on AWS for search indexing;
  • we've upgraded most of our code to the latest libraries so you get the benefit of improved performance and security;
  • reduced load time for public collections by 20%;
  • reduced load time for documents by 25%;
  • improved callout blocks;
  • more accurate reading time prediction by using a new algorithm;
  • faster real-time sync between people looking at the same document;
  • better table of contents rendering;
  • improved loading time of the knowledge graph on workspaces with 1000+ documents;
  • improved document tree drag & drop accuracy;
  • improved blockquote rendering.


#1 on ProductHunt, Workspace-Level Domains, Publish-Mode!

What a day on ProductHunt!

Product Hunt Raises $6 Million From A16Z | TechCrunch

Thanks to all your support, we made it to top 1 when we launched Archbee 2.0!

ProductHunt called us a "Google Docs alternative" a few days later in their newsletter. Flattered and humbled!

But there's no resting on the laurels... here's what we released today.

Workspace-Level Domains

One of our cool & distinctive features is that you can share collections of documents on your domain.

But each domain was bound to a single collection. That made it hard for everybody:

  • companies with multiple products had to set a different subdomain for each product's documentation; 
  • agencies with multiple customers (like you'd find an agency with a single customer, haha) had to set a different subdomain for each customer they wanted to share docs with;
  • every new domain had to be set in the DNS provider, taking too much time, and DNS propagation is really slow sometimes;
  • that also made it hard for us because we had to supply many SSL certificates, and that's not easy, or cheap.

The alternative was sharing the collections with an link, and that worked for some companies, but it didn't for those that wanted a more professional look.

Super happy to announce we now made it possible to share multiple collections on the same domain, by having a path on each collection, while maintaining the root path for a single collection. 

It was one of the most requested features!

Here's how you do it:


Our automatic save feature and collaborative experience made it easy to create docs by not having to click any unnecessary buttons.

That's awesome for internal team documentation and collaboration.

But for customer-facing documentation, it's not a good look to have them see unfinished work or drafts.

This is why we now have publish-mode, which snapshots your collection and deploys it to your domain.

You get to keep the staging link that points at the real-time collection, and a production environment to which the snapshot is deployed at your domain. 

Publish-Mode gets activated whenever you have a domain set on your collection.

This new feature also introduces clean URLs. We only add the randomly generated string at the end of the URL if you have another doc named exactly the same. To get the new URLs you have to publish once.

Here's how it looks like:

These two features were critical for our way to become your team's single source of truth for internal AND customer-facing documentation!

Enjoy your holidays, and we'll see you soon with more blazing features.


Improved table of contents

We've heard the feedback, table of contents needed much improvement, both on the internal side but also for external docs or docspaces.

We've built a better UI for all of it, starting from the editing experience, ending with your customer's docs delight.

Here's how it looks like on the internal side.

And the external shared side.

The same improved TOCs are available on individually shared docs and our blog, which is powered by Archbee's editor, check it out:

Doc categories

Our doctrees allow you to build any hierarchy you might want.

But sometimes you want to have parent docs without needing to write anything inside. No more "In here is this, this and that."

This is why we built doc categories. Here's how they look:

Here's how they look like when you share the spaces externally, on our own documentation:

Now you're set to go kill the docs game!

Better public docspaces

We've heard you, the rendering on the public view of docspaces needed improvements.

A refreshed UI is now available, along with performance improvements and placeholders for loading states. The search function used to be a bit hidden, now it's front right and center.

We've also made it possible for you to set the favicon to make your branding experience complete.

Now go in there and build the best documentation for your team and customers!

June 9 Product Update

Many of you asked us for the option to remove our branding from individual public shared docs, as it was already working for public shared docspaces.

For customers on the Scaling plan, this is now available. But we do hope you will help us become more popular by keeping the branding on 😇.

In the process, we've also made doc loading 5% faster, for both internal docs and external docs.

For hosted public docspaces, we've added a status indicator that now allows you to see if your DNS has propagated or not, and more information for how to check yourself if you need details.

May Product Update

In a nutshell, we've been hard at work improving our core tech, but we've also been able to sneak in a couple of nice to have features.


  • documents now load 7-10% faster;
  • we were able to shave 150 to 200 milliseconds off the realtime sync algorithm, making realtime collaboration better;
  • we've added more and better editor shortcuts (Markdown included); check the new shortcuts by hitting Ctrl (or Cmd on Mac) + /;
  • we've changed our CDN to AWS CloudFront, and setup better firewalls to our APIs to mitigate next Denial of Service attacks;
  • certificate generation for hosted docspaces on your domains now happens in maximum 1 hour since the DNS has propagated, and we also have lowered their regeneration rate to 2 months;
  • hosted docspaces are now 15% to 60% faster, as we were able to cache some of the content close to your customers; this will also improve your SEO;
  • UI improvements across the board: more consistent spacing and colors throughout the app; cross platform scrollbars;
  • better support for Safari and Firefox; there's still work to be done here, but we strive to be 100% cross-browser as ~15% of you don't use Chrome-based browsers;
  • better support on mobile browsers;
  • we've started doing automated phishing scans to prevent malicious use of our platform;
  • our embed integrations come out of beta and are now generally available;
  • iframe embeds and custom javascript are generally available but will stay in beta for a while longer;
  • docx import comes out of beta.

What's next?

  • workspace-level domains, share any amount of docspaces in an URL format like this:;
  • desktop app;
  • improved datatables that draw inspiration from AirTable;
  • continued core technology improvements;
  • many misc. features asked by you; thank you for your great ideas in the Feature Wishlist, we watch them closely and many of them will get implemented.
Show Previous EntriesShow Previous Entries