The main aim is to provide an easy way to write my technical
documentation.
Don’t care about the formatting and focus on the contents.
To allow teams to manage their knowledge database easily.
Do not depend on third software products like word processors or
complex web applications.
Features
Pros
Writing documentation: Documents must be in Asciidoctor format which
is easy to learn.
Finding documents: Once a document is converted to html, properties
can be browsed. Moreover, property pages have filters and a search entry
to filter by title.
Publishing your repository: all necessary files are inside a
directory. Browse it or copy it to your web server.
Serverless: There is no need for a web server. Of course, you can use
one if you please.
Smart compiling: Only those documents added or modified are compiled.
Use the default themes or build your own custom theme
By modifying templates, it might be integrated with Github or Gitlab.
Cons
Not to much documentation at this moment
No online editor: At this moment, KB4IT doesn’t include any online
editor. You must create or edit your documents with your preferred
editor.
No dynamic search: KB4IT was developed to be as simple as possible.
No dependencies at all excepting Asciidoctor (as text processor and
publishing toolchain) and Python (the programming language used).
API is not stable
Most of the requirements are tailored to my own necessities which
might not be the same as yours.
Installation
From source
If you have used this app before, it might be necessary to uninstall it
before:
Python Programming language that lets you work
more quickly and integrate your systems more effectively.
Asciidoctor A fast text processor &
publishing toolchain for converting AsciiDoc to HTML5, DocBook & more.
UIKit A lightweight and modular front-end
framework for developing fast and powerful web interfaces.
Geany Powerful, stable and lightweight
programmer’s text editor that provides tons of useful features without
bogging down your workflow. It runs on Linux, Windows and MacOS is
translated into over 40 languages, and has built-in support for more
than 50 programming languages.
How to improve KB4IT so it doesn't depend on core properties (a predefined set of properties)?
Or should KB4IT look for a very small set of properties (like Author, Category, Scope)?
Till now, UIKit is included by default as the front-end framework for developing the web interface.
KB4IT shouldn't care about the framework used. Themes should provide it.
Create a set of standard templates (modifiable by users) with a set of predefined properties and values. This would make easy to add issues / tickets / reports / blog posts / etc...
Enable pagination in order to display a large amount of values. Otherwise, it takes ages to display all doc cards at one.
Disable filters for key pages.