Slab

The internal wiki your team will actually want to use

#5 Product of the MonthJuly 2018
+2

Slab is a simple, beautiful, and powerful team wiki built for the modern web. It features an intuitive editor, blazing fast search, and numerous integrations, like Slack, Github and GSuite, to tie everything together.

Discussion
Would you recommend this product?
55 Reviews5.0/5
Hi Product Hunt 👋, I'm Jason, the CEO of Slab, and along with my team @anvishapai and @chengyinliu, we are thrilled to share Slab with you. Thanks @chrismessina for hunting us! At Slab, we're building your team's long-term memory. When a team is starting out, knowledge sharing is mostly ad hoc through Google Docs or ephemeral through email or chat. Once they grow to a certain size (remote teams experience this much sooner), finding answers in these tools becomes a struggle and a more deliberate and durable way to share knowledge is needed. Our team has all experienced this problem firsthand, at some of the most innovative software companies. We learned that knowledge sharing at scale is still an open problem, even for the most efficient teams. We've spent the past year iterating with our private beta companies to build Slab. It ties together an intuitive, simple interface with powerful search and organization—and integrates with numerous tools to connect your team's knowledge together. We are excited to share this with you today and would love to get your feedback! We'll be around all day answering questions, so feel free to comment here or email me directly at jason@slab.com.
Upvote (23)Share
@anvishapai @chengyinliu @chrismessina @slab @jhchen What are you guys most excited about building next for Slab users?
Upvote (2)Share
@dtran320 The most common request I hear is Desktop and Mobile apps, and I can't wait for the day I don't have to say "we are working on it"! 😝 Personally however I am most pumped about Search. Fast, relevant search can make such a big impact on your day-to-day productivity. We wanted our search to break past silos so we search across your content from GDrive, GitHub, Slack etc. We have an interesting challenge here where some of these providers' search endpoints ranking algorithms aren't great and don't always contain all the information we want (like Previews). We also have to rank these results against each other (eg: how do you compare a pull request to a Slack message?) while keeping it all blazing fast.
Upvote (5)Share
@anvishapai @chengyinliu @chrismessina @slab @jhchen product looks beautiful. love how it connects to everything. it seems like a pretty busy space how did you guys find your early users for the product and continued to grow since that point?
@anvishapai @chengyinliu @chrismessina @slab @thepriyadarshy There are a lot of writing tools for individuals and small teams, in particular in the note-taking space where sharing and the reader's experience is an afterthought. This is fine for a ten person team but will break down at scale, especially across functions. There are very few tools that scale beyond 25-50 people and even fewer that are both powerful enough for engineering teams and approachable enough for marketing teams. The only name that consistently comes up here as even acceptable is Confluence. Slab hopes to become an alternative that people will name with more enthusiasm. To answer your early growth question specifically I don't think Slab did anything special. We hustled our friends and network, listened to their feedback and iterate, and over time as our product became more worthy, our users referred us.
Upvote (2)Share
Awesome product 😍 Been using it for the past few months, love being able to quickly create docs, and share exports that look fresh with clients and my team 🙌🏽🔥
Upvote (6)Share
@sebfeed We are grateful for your patronage 🙏🏽
Upvote (1)Share

Slab is a simple, but very well designed wiki with a clear sense of purpose: it wants to tie together all the places your team currently stores information to become a single source of knowledge for the entire organization. The result is a wiki that lacks some of the visual niceties and tat of some other solutions, but which makes up for it in sheer usability.

They're threading a needle here. It feels simple and doesn't impose itself at all on your writing process, but it also subtly ensures that you're keeping everything well organized and referenceable by the whole org. That's a stark contrast to systems like Confluence, which are potentially very powerful if used correctly but using where using them "correctly" imposes such an additional upkeep burden they hardly get used at all.

Ultimately, a wiki is only as useful as the amount of infomation it contains. Slab is one of the few I've seen that my team actually seems to like to use. That's a winner today in my book, and I'm very eager to see what else they add as it develops.

Pros:

Lightweight in all the ways you want it to be, easiest to use wiki I've encountered. Search is powerful w/ integration into linked documents

Cons:

Still a bit feature light, works best for content without a lot of visuals. Would benefit from more customization options

Upvote (6)Share
I've been looking for a way to build out SOP's for my business. Considering this... but also I don't know if i like the SOP's living in a proprietary paid monthly solution indefinitely. If there was an export to PDF feature that that could live forever I would be more likely to use this tool.

We* defaulted to using slack/gdocs as the de-facto knowledge management tool, quickly realized that's not the way to grow and started looking into a dedicated solution. I used confluence and a few wiki solutions before, both in context of a tech team in a large investment banking institution, startups and community organizations. In the end it was a close call between Confluence and a Slab, we decided to go with Slab. It is simple and straightforward to use for both devs and non-devs in the team. The Slab devs have been very responsive and added an app integration we really needed (for diagramming) in a matter of days, which was impressive.

* My team makes a hardware product that has a lot of complexity (6 levels, from product design to game engine)

Pros:

Quick setup, clean layout, good performance, team adding new integrations/features often

Cons:

Some integrations not yet there yet (e.g. Jira), still requires thought to be put into the structure of knowledge

Upvote (7)Share
Congratulations on launch! We have been using Slab for a little over a year while building moonlightwork.com. One of my favorite uses cases is taking notes during meetings - it lets people who were there align on takeaways and goals, and it informs others about what happened. I like to think of Slab as Evernote meets Google Docs for teams. Question for @jhchen: How do you use Slab internally at Slab? What have been your most effective or valuable workflows within your own product?
Upvote (5)Share
@philipithomas Thank you for giving us a shot from the beginning and all your feedback throughout 🙏🏽 One main use case is engineering documentation. In building the company we have engaged with several contractors and also the final part of our interview process is a pairing project on our real codebase. Both of these really benefit from getting going as quickly as possible — setting up the development environment, learning about our toolchain, and best practices in our codebase. All this is even synced with Github so we can keep our code review process on particular content e.g. How to Deploy to Production. It’s amazing to see how quickly people can ramp up with the proper forethought and documentation to support it so yes using Slab has absolutely been a critical part to building Slab!
Upvote (2)Share