3 ms·
Test driving it, like it a lot! Some initial feedback: * I sent a support request by email with two screenshots. The first screenshot did not show up in the we
by jstsch 7y ago
Test driving it, like it a lot! Some initial feedback:
* I sent a support request by email with two screenshots. The first screenshot did not show up in the web view (the cid: remains in the HTML source).
* A demo account with lots of dummy data might be useful for a quick glance at the product.
* Might want to add a Letsencrypt wildcard SSL domain for https://*.demo.fullhelp.com https://*.demo.fullhelp.com
* Missing language string when creating an article: Title.created
* There is a non-deletable dummy note attached to a customer from a certain Peter Richards ;)
* Typo: shoirtly -> shortly
* Theming: this is quite a big feature, so understandably a bit rough right now, perhaps offer a blank template .ZIP file to get started?
* I'd like to be able to modify language strings, but perhaps this goes via the theming ZIP
Looks quite cool!
- fullhelp 7y agoHi! Thanks for taking the time to check it out and the feedback! For the theming feature, I was thinking of adding a way to export the installed themes, that way the user can download the theme being used and apply any customization and re-upload as a new custom theme. A blank template for new designs is an excellent idea. I've also created a small node based command-line program that syncs local development changes to the live knowledge base portals. This helps a lot with testing and previewing the themes. I've not released it just yet, I plan to do so with an MIT license on GitHub. It is similar to Shopify's Themekit (https://shopify.github.io/themekit https://shopify.github.io/themekit). This is what I use to work on theme designs. For knowledgebase language strings, you are right, that's possible at the moment through the theme locale files.