2 replies to this topic

[gbarry]

For the next week, we will be making a major push to edit and update the current Evernote Knowledge Base. Our education team is plugging away, reviewing and writing suggestions and updating articles.  We want to hear from you--let us know what you would like added, what you think needs updating. If there is ANYTHING you think should be added, we're all ears and listening.

 

Please try to get in all of your submissions in by Friday, March 1st.  After this initial push we'll make available alternative avenues for article suggestions and updates (including our regular KB space on the forum).

Submit your suggestions here: https://docs.google....rZrR_o/viewform

 

We look forward to hearing your suggestions!

[andreb]

Hm ... I still wonder why you don't offer the knowledge base as shared notebook. Wouldn't that make sense?

[gbarry]

We used to have one actually, but it wasn't kept as up-to-date as it could have been (I'm aware of the irony at the moment, since the current KB has needed a refresh for a while as well). An oft-overlooked reason for the KB's existence is to help defray tickets coming in through customer support--if you can find a "suggested answer" in the KB prior to submission, then that reduces our costs from a customer support perspective, or at the very least frees us up to answer one more support question that much faster. Having the KB work directly with our ticketing system meant that it couldn't be run through Evernote, and if wanted to keep both running separately, that would require someone curating and managing both, without any helpful connections between the two.

We do use Evernote to help build the KB, and we're using it to help keep it updated, but even this version would require additional curation before we could externalize it, which would require duplicating what we're already doing with the support version of the KB.