search

officelifehq / officelife

OfficeLife is the first EmpOps platform. It manages everything employees do in a company. From projects to holidays to 1:1s to teams.
https://officelife.io
GNU Affero General Public License v3.0
912 stars 125 forks source link

Ability to have a knowledge base/wiki #917

Closed cweagans closed 3 years ago

cweagans commented 3 years ago

We have a number of policies, documents, checklists, etc. that we currently keep track of in a Google spreadsheet titled (and I'm not joking) the "Sheet of Sheets". It's literally a list of links to other spreadsheets and documents and such.

I would love to not have the Sheet of Sheets anymore.

To do that, we'd need some centralized place where we can either a) write a document/policy/etc directly, or b) link to an existing Google Doc or other external resource. It would be great if we could put it in some kind of organizational hierarchy in the wiki as well. For example, maybe there would be an "Accounting" section, which would link to budget spreadsheets, accounting processes, expense policies, etc. There might also be an "Engineering" section, which would link to the document describing how we work, code review policies, the SLA that we have in place for our products, etc.

To take this even further, it would be great if there were both a company-wide wiki and any number of smaller wikis that belonged to individual departments/business units. We have multiple business units that are doing very different things. Some documents (like our two factor authentication policy) apply business-wide, but some documents (like a proposal template that one business unit uses) aren't that useful to people that aren't working in that business unit.

cweagans commented 3 years ago

(another use case is compliance documentation -- if you're doing SOC2 or something similar, they usually require you to have written policies published somewhere that all employees can see them, along with requirements for regular review, updates, etc.)

OrinSafko commented 3 years ago

This would be incredible. I need a place where I can document for the team what we use each software for and why we decided on this software for this purpose. It would also be a place where we can provide instructions for new users on our team how we use each software. This would definitely fall in line with your vision for the Recruit domain, onboarding. Since software management is part of OfficeLife, this seems like a good way to tie this all together.

djaiss commented 3 years ago

@cweagans this is next on my todo list!

Thanks for submitting this idea.

OrinSafko commented 3 years ago

@cweagans this is next on my todo list!

Thanks for submitting this idea.

Awesome! Can't wait for this.

djaiss commented 3 years ago

@cweagans @OrinSafko trying to scope the first iteration of this feature.

Should all wikis be public in the company for now?

cweagans commented 3 years ago

For the first iteration, certainly. Down the road, it might be nice to have e.g. an engineering wiki that is only accessible to an engineering team.

djaiss commented 3 years ago

For the first iteration, certainly. Down the road, it might be nice to have e.g. an engineering wiki that is only accessible to an engineering team.

Makes sense!

OrinSafko commented 3 years ago

@djaiss I completely agree with @cweagans. Permissions aren't necessary for my team at the moment. But I could see it being necessary for some teams.

djaiss commented 3 years ago

The first iteration of the wiki is now in production. It's a bit rough for now, but we'll make it better over time 😄

OrinSafko commented 3 years ago

@djaiss this is excellent! This is a great start to being able to have our knowledgebase / documentation in OfficeLife. Thank you! I'll be putting feature requests for the Wiki in the discussions as I have ideas. Thanks!

github-actions[bot] commented 3 years ago

:tada: This issue has been resolved in version 0.4.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket:

github-actions[bot] commented 2 years ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.