← Digital News

Documentation Update September 29, 2020

Hey folks,

Another month, another documentation update! It’s been a little less than a month, and each member of the team has lost a bit of time during September, so this update might be a little shorter than usual, but we’ve still got plenty of cool stuff that’s shipped!

New docs

For more up-to-date notifications, we post every new document or significant update (including ops docs) in the #org-documentation channel in Slack!

Site updates

We continue to work on the knowledge base as a site. After adding a couple new sections last month, we’ve been working to fix some functionality on the internal version of the knowledge base. We’ve fixed a few bugs with search and links to internal resources. We’re still chasing down a bug that makes search unreliable unless you’re on the homepage of the internal version of Banno Knowledge, but we’ll be trying to get that resolved in October.

In progress

As always, we’re moving through both our backlog and new shipping features each month. Docs currently in progress that should be either launching or in draft review in October include:

  • Continued work on Transfer docs
  • Documentation for the Transactions and Accounts view in Banno Apps
  • Documentation around Banno Reports
  • Beginning work on Banno Content as we scope out individual docs and restructure to match current verbiage and feature sets.
  • We’re also adding a collection of best practices docs alongside these feature docs, which will live on Banno Knowledge. Two of these are in review, with more on the way!

Doc day

Spearheaded by Dan Chilton, several engineering teams are taking Wednesday, September 30 to work on all of our docs, especially technical docs. Provided this goes well, this will be spreading throughout the org over the next year. If you’re interested in seeing what folks are working on, feel free to poke your head into #doc-day-event on Slack!

Anything else?

As always, if you’d like to see any documentation work done, throw us a service desk request, tag a post with the :documentation-team: reaction, or just give us a holler in #org-documentation! Whether you need new docs, an edit, or have a suggestion as to how we can improve what we’re putting out, we’d love to hear from ya!