Skip to content

Commit 179711d

Browse files
committed
#134 knowledge base use case
1 parent f55c292 commit 179711d

File tree

1 file changed

+31
-0
lines changed

1 file changed

+31
-0
lines changed

src/usecases/knowledge-base.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
# Atomic Server as a Knowledge Base
2+
3+
A Knowledge Base is a tool that helps you to store and manage data.
4+
They are designed to be very flexible, and can be used for many purposes.
5+
In a way they are the antidote to using many different online tools for very different purposes.
6+
7+
Knowledge bases can be used to:
8+
9+
- Document features of a product or service
10+
- Meeting minutes
11+
- Plan projects
12+
- Manage team members and their profiles
13+
- Describe strategy
14+
- Document features
15+
- Document bugs
16+
17+
Some organisations store this information in a shared folder in Google Drive,
18+
some have a bunch of spreadsheets,
19+
and some may have
20+
21+
## Why Atomic Data is great for storing knowledge
22+
23+
Atomic Data is structured in a way that makes re-use very easy.
24+
Every property of data has its own URL, which helps users to know what a piece of data sementically represents.
25+
For developers, Atomic Data is great as it has a very simple yet powerful RESTful API.
26+
And because it's entirely open and free, there's no vendor lock-in.
27+
28+
## Why Atomic Server is a great knowledge base
29+
30+
Atomic Data is a _specification_ that is suitable for knowledge bases, and Atomic Server is a _piece of software_.
31+
Atomic Server is an open source knowledge base that is very powerful, feature-rich, and easy to use.

0 commit comments

Comments
 (0)