Slab

The internal wiki your team will actually want to use

get it
#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.

Around the web

Reviews

  • Pros: 

    Fast, Intuitive, Simple. Powerful integration with Slack and GDocs

    Cons: 

    Still new, compliance roadmap unknown

    We have used Slab since it was in private beta. It's been very helpful for us as we grow and scale the company. For us, as an enterprise startup focused on lengthly sales cycles and deep esoteric knowledge, we knew we needed a great product for us to document a lot of learnings.

    Slab has been a product that everyone in the company has used, and uses without many questions or much on-boarding effort. It's been critical for us to scale knowledge and the ease at which we've managed to capture it has yielded so much as we continue to grow and add people.

    Highly recommended.

    adrian sanders has used this product for one year.
  • Jon XavierWriter, WePay
    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

    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.

    Jon Xavier has used this product for one month.

Discussion

You need to become a Contributor to join the discussion - Find out how.
Jason ChenMakerPro@jhchen
Hi Product Hunt 👋, I'm Jason, the CEO of Slab, and along with my co-founders @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. My co-founders and I have 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.
David Tran@dtran320 · Co-Founder & CTO, Upbeat
@anvishapai @chengyinliu @chrismessina @slab @jhchen What are you guys most excited about building next for Slab users?
Anvisha PaiMaker@anvishapai · Co-founder @slab
@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.
Ashutosh PriyadarshyPro@thepriyadarshy · CEO @ Sunsama
@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?
Jason ChenMakerPro@jhchen
@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.
Sebastián León@sebfeed · Builder. Dreamer
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 🙌🏽🔥
Jason ChenMakerPro@jhchen
@sebfeed We are grateful for your patronage 🙏🏽
Philip I. Thomas@philipithomas · Co-founder at moonlight
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?
Jason ChenMakerPro@jhchen
@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!
Romain Sourdiaux@imromains · 🍋
Interesting 🤔😇 Why should I use Slab instead of like a flexible product like Notion for example?
Anvisha PaiMaker@anvishapai · Co-founder @slab
@imromains Check out my cofounder @jhchen's comment below 👇https://www.producthunt.com/post...
Anurag Goel@anuraggoel · Founder at Render
How does Slab compare to something like Notion (which works well for now for our tiny team)?
Jason ChenMakerPro@jhchen
@anuraggoel There are several consequential differences that stem from one differing goal: Notion seeks to be an all-in-one tool and Slab seeks to be a best-of-breed tool. Slab focuses just on content that has long term relevance to your team. As a result, we have small set of functionality that we need to fit into an interface. Notion has done a good job managing some of their complexity but they are playing the UX game on hard mode. Notion can work well for small teams or individuals. But any time you need advanced task tracking features you'd have to look to GitHub/Asana/JIRA or if you need a more powerful table, Airtable/Excel/Sheets. Notion can't yet match up to the power of these tools for doing what they do best. All teams need wikis, sheets, and tasks at some point. With Slab we've chosen to focus only on the wiki use case, and integrate with the best-of-breed sheets and tasks tools like Google Sheets/JIRA/GitHub etc. The integration link between two different products will never be as tight as the same product, but we think the strength of the individual products being integrated, more than makes up for this.
Romain Sourdiaux@imromains · 🍋
@anuraggoel @jhchen I asked the same question about the difference with Notion; I see what you mean but when I visit your website it just says it's a wiki and I don't actually see much about integrations etc. You need to go on the pricing page and it tells you a bit more about Standard / Premium Integrations but I can't actually find a list or anything? ✌️
Jason ChenMakerPro@jhchen
@anuraggoel @imromains Yup we're still iterating on copy and actually have dedicated pages for integrations planned but wanted to launch sooner. Thanks for the feedback!