dschramm

5 ms·

31.
by dschramm 7y ago
I agree, that's one of the challenges we have to tackle. The commands being contextual to the page you are on helps in my point of view, but we have to explore ways of onboarding users in a proper way.
32.
by dschramm 7y ago
Hello HN! We just rolled out this little MVP for a new user interface for our knowledge base software. I would love to hear what you think about it! Cheers, Daniel
33.
Show HN: An experimental, keyboard-first user interface(emvi.com)
263 points by dschramm 7y ago|104 comments
34.
by dschramm 7y ago
Other knowledge bases and wikis tend to rely on a tree-like hierarchy and setting access permissions with a top-to-bottom approach. In Emvi permissions are set on per article basis, so they can have company-wide reach and still be edited by
35.
by dschramm 7y ago
I agree, the culture in an organization makes or breaks a knowledge base. We try to lower the barrier of entry by not giving an article a definitive place, meaning you don't have to think about where to put something when writing a new
36.
by dschramm 7y ago
We do not have an import feature yet, but that is definitely coming. Where would you like to migrate from?
37.
by dschramm 7y ago
Hello HN! Emvi is our approach to a easy-to-use knowledge base for companies and teams of all sizes and we finally reached public beta. You can use it to write down everything you need to remember, share or document and make it discoverable
38.
Launch HN: Emvi – Knowledge management for companies and teams of all sizes(emvi.com)
4 points by dschramm 7y ago|7 comments
39.
by dschramm 7y ago
Hello HN, co-founder of Emvi here! Emvi is our approach to a real-time knowledge base and we finally opened registrations for public Beta. We found that existing tools structure content in a tree-like hierarchy which tends to limit reach an
40.
Show HN: Emvi – Knowledge management platform for companies and teams(emvi.com)
3 points by dschramm 7y ago|2 comments