3 ms·

For those who are wondering how the styling looks, I signed up and copy-pasted a markdown sample here: https://app.faqt.co/share/k6hs7l https://app.faqt.co/shar

For those who are wondering how the styling looks, I signed up and copy-pasted a markdown sample here: https://app.faqt.co/share/k6hs7l https://app.faqt.co/share/k6hs7l This looks pretty cool. I think I'l be using this from now on. Features I'd like to see in the future: - custom domain (esp for teams, which I see is in the works) - Revision History - Exports/Backups - Searching - Raw markdown support. I often like to copy markdown from places, and this would come handy. Just a .md at the end of the route would do. - API support is always nice Also, while you are working at a team solution, you might want to take a look at this blog post [0] from xoxco, where they describe their knowledge base that integrates very well with slack. [0]: https://medium.com/why-not/our-slack-wiki-e4f6d23a3495 https://medium.com/why-not/our-slack-wiki-e4f6d23a3495

shkkmo 11y ago
Yeah, I can't put the time in to enter stuff into a proprietary codebase until there is the ability to export or a api to allow me to write my own export.
siavosh 11y ago
This is helpful, thanks for sharing. We've struggled with where to integrate with first as most integrations I've seen have been gratuitous, but #slack is a solid possibility. Curious about the API support, how would you use it?
- captn3m0 11y ago
  While I do have a _drafts directory for my blog under version control, editing it locally is a pain. What I'd like to do: - write the blog post drafts under a `Drafts` category at faqt - Run a script that fetches all drafts and commits them in my drafts repo when I run it That way, my repo stays updated, and I don't have to worry about copying-pasting updates there. I could even write a "publish-from-faqt-to-blog" script that detects a category change from "Drafts" to "Published" and handles that for me. Would you be considering front-matter yaml support. If you add that, tagging+searching things would become so much better. (Every doc gets its own set of properties). Also, if you give us an API, we can make more integrations ourselves. That is one of the main reasons behind Slack's success.
  - hobofan 11y ago
    For such a use-case Contentful[0] might be viable solution. [0] https://www.contentful.com https://www.contentful.com
asdfzxc 11y ago
Can you share the markdown sample? I've never used markdown before, outside of reddit (I think), and I'd like to use this sample as a reference.
- captn3m0 11y ago
  I copied it from http://www.unexpected-vortices.com/sw/rippledoc/quick-markdown-example.html http://www.unexpected-vortices.com/sw/rippledoc/quick-markdo...
siavosh 11y ago
A quick follow up: we just released the export functionality where you can download all of your markdown with one click anytime. Let us know if you have any thought or questions.
- captn3m0 11y ago
  Thanks a lot.

shkkmo 11y ago

Yeah, I can't put the time in to enter stuff into a proprietary codebase until there is the ability to export or a api to allow me to write my own export.

siavosh 11y ago

This is helpful, thanks for sharing. We've struggled with where to integrate with first as most integrations I've seen have been gratuitous, but #slack is a solid possibility. Curious about the API support, how would you use it?

captn3m0 11y ago
While I do have a _drafts directory for my blog under version control, editing it locally is a pain. What I'd like to do: - write the blog post drafts under a `Drafts` category at faqt - Run a script that fetches all drafts and commits them in my drafts repo when I run it That way, my repo stays updated, and I don't have to worry about copying-pasting updates there. I could even write a "publish-from-faqt-to-blog" script that detects a category change from "Drafts" to "Published" and handles that for me. Would you be considering front-matter yaml support. If you add that, tagging+searching things would become so much better. (Every doc gets its own set of properties). Also, if you give us an API, we can make more integrations ourselves. That is one of the main reasons behind Slack's success.
- hobofan 11y ago
  For such a use-case Contentful[0] might be viable solution. [0] https://www.contentful.com https://www.contentful.com

asdfzxc 11y ago

Can you share the markdown sample? I've never used markdown before, outside of reddit (I think), and I'd like to use this sample as a reference.

captn3m0 11y ago
I copied it from http://www.unexpected-vortices.com/sw/rippledoc/quick-markdown-example.html http://www.unexpected-vortices.com/sw/rippledoc/quick-markdo...

siavosh 11y ago

A quick follow up: we just released the export functionality where you can download all of your markdown with one click anytime. Let us know if you have any thought or questions.

captn3m0 11y ago
Thanks a lot.