GitHub repos full of markdown. A Jenkins job rebuilds using a static site generator (mostly Jekyll, a couple use Pelican). Each team has a subdomain on our inte

GitHub repos full of markdown. A Jenkins job rebuilds using a static site generator (mostly Jekyll, a couple use Pelican). Each team has a subdomain on our internal network, so like accounting.company.internal type thing. Most have a TOC type landing page with popular links. Commit markdown -> site rebuilds itself. GitHub desktop is easy to use and we're generally staffing under 35's, who are pretty computer savvy. They may not get the in's and out's of Git, but Customer Service people are rebasing (their internal knowledge base is built the same way). Upsides for users: Using whatever editor you favor. Anyone can help support your teams efforts (copywriters are committing tweaks all the time to every teams repo, use dem writing skills). We avoid fragmenting and putting multiple UX's in people's faces. Design folks even made some CSS that's easily injected to match company branding. Optional to use of course. This is for the things teams can/want to share. HR obviously doesn't people's salary info in there. We needed GitHub anyway. So we found a way to avoid spinning up some kludgy wiki framework with a shitty WYSIWYG editor no one wants to maintain or paying money for some janky thing like Jive or Yammer.