Slite Blog

I use https://slite.com - it's a very nice, clean modern markdown editor with keyboard shortcuts and ability to paste images from clipboard. You categorize notes in collections and you can search them, export them to markdown or pdf, and work as a team. It has Slack integration as well if that's your thing. Highly recommended!

We started using Slite http://slite.com/ 6 months ago with great success. We previously used Atlassian Confluence for our internal knowledge database, and it resulted in very static content and poor adoption. Slite is a much better choice: we use it for "static" company knowledge (like onboarding, processes, etc.), but also for most of our dynamic content (meeting notes, document drafting, sales support documentation, etc.). Many people (including dev) use it on a daily basis, and most people on a weekly basis. Definitely recommend.

There are two main problems with wikis : Maintaining and Finding. I'll start with the second, because it is 2023, and wikis are finally embracing semantic search [0] This will not only almost solve this problem. It will also alleviate the need for heavy handed organization in general 9categories..) The first problem is best solved IMO with getting someone responsible for gardening it as someone put it in this thread. There are new design approaches for smoothing the process [1], but a human gardener is still you best bet. [0] https://slite.com/ask is the first enterprise wiki I've seen integrating this. [1] An exple for code documentation is https://swimm.io/

And surprise surprise, no location-based pricing on their money site: https://slite.com/pricing. So employees must reduce their salary if they live in a cheap cost of living, but companies based on that same cheap cost of living (i.e. low income) area don't get a discount for their services. In a post-Panama-Papers world, I don't blame individuals for optimizing like companies do. So good talent will live in Argentina and find a way to get a $200k+ salary, if that is what they are worth to someone. And why not, software is eating the world, afterall.

This is really just advertising (little content in the slides) for Slite [0]. Looks at a brief glance that it might be interesting, probably a better URL for the submission than the current slide deck [1]. In fact, @clmntrg, from your submission history I gather Slite is yours (a few submissions about it on blogs/reddit) - why not 'Show HN: Slite - the workspace for async teams' (slite.com link)? I'm sure it would be better received than these 'pitch.com' slides. [2] [0] - https://slite.com [1] - (in case it is updated) https://app.pitch.com/app/public/player/5fa67ab4-b618-46dd-a2a0-886c03… [2] - (examples in case you don't know what I mean) https://news.ycombinator.com/show

Yes, enjoyed the article, but in case others are unaware, there are several other popular block style editors today which use the same data model. E.g. https://slite.com/, https://editorjs.io/ (open source), and https://www.slatejs.org/ (open source).

Anecdote: I know "the right tool" is not the answer usually but suprisingly enough the introduction of https://slite.com (ditching confluence) has helped our team in pushing us further towards a "document first" path / culture.

Slite | Paris or Remote (CET -2 / +2) | Full-time | https://slite.com At Slite (YC W18), we're a friendly bunch excited to bring the power of notes to teams and change the way they share knowledge! Meet the team here: https://jobs.slite.com/ Our team is distributed across 4 cities and counting. We believe in empathy, transparency, asynchronism and remote. We run on React/Redux - Node.js/GraphQL/Docker/Kubernetes We are hiring for: Lead Engineer — help build, manage, and scale Slite API, lead one of our squads — https://jobs.slite.com/lead-engineer/en Get to know us better by reading our blog at: https://medium.com/slite — we value you taking the time getting to know us prior to applying.

Maybe this? https://slite.com This is their post: https://news.ycombinator.com/item?id=16476092

Is one of these 3 what you're looking for? * https://meetcody.ai * https://builtbyjesse.com * https://slite.com/ask

really not trying to blogspam but wrote this article on info architecture in a wiki for Slite – hope it helps: https://slite.com/blog/how-to-build-a-company-wiki-that-doesnt-suck

It's not about leveraging the lower cost of poorer countries that we do that, as we actually have most of our team living in high cost of life ones. Part of the explanation why we do it this way can be found here, https://slite.com/blog/lets-pay-our-remote-employees-fairly-not-equall… happy to continue the discussion if you want to!

Short answer : absolutely not, you can have a look at our privacy policy here : https://slite.com/privacy. On the why investors would fund us, I think the "note" aspect of it is misleading: it's simply giving an ease of use to our users, but the core of slite is the team aspect of it, and our will is to solve knowledge sharing in teams. While this is not solved, clearly investors will fund projects like Slite.

Looking at this page, https://slite.com/use-cases, I feel like this kind of product is an anti-pattern. The reason that it's hard to find things in slack or docs is because these apps do not well understand the underlying structure of the data and so are relegated to either full-text search, or some sort of naive clustering algorithm. Although Slack has made some advances here - such as adding context-specific buttons for actions. Will Slite do a better job at understanding our bug reports than Github? Or understanding our applicant tracking system then Greenhouse? Our customer support than Zendesk? Every one of these tools have a search feature. The value of Google Docs is that it stays out of my way, lets me create freeform notes, and integrates with the rest of Google. Probably the same for Paper, or any other team notes solution. Once something gets complex enough, creates work for teams, or is mission critical, it either needs to be actively managed by a team member, or move into an automated tool that does that management for us. I can't imagine the solution would be to centralize all these disparate workflows in a tool like this.