@geetfun
0
0
0
0
2
3
Login to ask this maker a question.
Answered by geetfun...
First off, thanks for being a supporter of Eager.app. Super, super happy to see it being used by others.
A few reasons for creating the Knowledge Base product for Eager.
I wanted to be able to host my docs from a subdirectory. For example, at https://eager.app/docs instead of docs.eager.app, like so many Knowledge Base apps force you to.
The KB or documentation site can be such a rich source of SEO and a way for users to find out about you that I feel it should be more optimized for this. Having the option for Eager to serve through to your subdirectory gives you that extra SEO juice.
Next, I wanted something that looked great out of the box, both on mobile and the desktop. I wanted a simple and clean design for basic documentation.
Prior to Eager, I've run several micro-SAAS products and it has always been a pain point to get a quick documentation site up and running.