@ScribeWiki emulates a hierarchical folder system without actually forcing you to sort your content hierarchically.
You can “expand” a page or collection to see the content it relates to. It gives you a super easy way to traverse your web of knowledge!
@getclibu Nice, you've packed a ton of functionality in there! Surprised you are still classifying it as an alpha.
From what I can gather it seems like it is more aimed at personal note taking?
I'm hoping this is a first step in connecting documentation to what's being documented.
It currently supports Confluence and Basecamp but happy to add more integrations on request :)
Any chance this would float @ProductHunt's audience @rrhoover?
We built a @GitHub App that lets you easily connect files in your GitHub repository to documents in your wiki!
Anytime you submit a Pull Request it will give you a summary of the connected documents, highlighting any that are in need of an update.
@alkshendra_26@ianstormtaylor It seems like your editor is coming along pretty well! Which parts where you having the most trouble with?
I’ve finished writing the first article in the set and I’m on to the second. Hoping for it to be finished within the next few weeks :)
Started writing a set of articles on #slatejs. Will detail:
* How it works internally
* How to build a feature rich editor
* What is currently difficult to do with SlateJs
* What is in the works for SlateJs
Huge thank you to @ianstormtaylor for building such a great library!
@webkit we would love it if you could enable getUserMedia (i.e. the camera) in browsers other than Safari on iOS. Pretty please...
https://t.co/pCq5i8XQvy
The FLIP Animation technique is easily one of the most underrated techniques for web development. It's really helping Scribe feel more like an App.
Thanks @aerotwist :)
Just putting the finishing touches on the tablet revision system!
Think of tablets like documents in other wiki products. It’s useful to be able to see who has edited which part of the tablet over time so you know who to ask further questions of. This enables that 👍
It would be nice if #NoCode tools were at a place where they could build easily Scribes frontend (rich text editor that needs SSR for SEO reasons).
Coding can really feel like a lot of undifferentiated heavy lifting sometimes.
Analytics has generally been a seperate section removed from everything else.
We have been thinking a lot about how it can be more integrated into the day to day experience.
Why is it that your internal knowledge base and the web (public knowledge base) are two seperate entities?
Why isn’t your wiki just a layer on top of the web... food for thought
Current tech stack: React (NextJs) + Elixir + GCP
Critical libraries: Apollo Client + Absinthe + SlateJs
Building a PWA with a WISYWIG editor + offline support + indexable public wikis + big emphasis on search + more
@zeithq@reactjs@elixirlang#slatejs#nextjs
There is a fundamental problem to documentation, the more thorough it is the quicker it becomes outdated.
I think tools (*cough* Scribe *cough*) can do more to alleviate this than you may think. All comes down to how much of the documentation management we can do for you.
Imagine if your documentation was connected to the thing it was documenting. If that thing changes then that documentation is marked as potentially needed an update.
Could work both ways, e.g. for codebases if you haven’t updated the corresponding documentation you cant publish