Tool idea : A publishing engine for OKF

[straumat]

Hi,

Can you give me feedback on my idea for developing a publishing engine that turns Markdown files into navigable knowledge systems for both humans and AI agents?

The idea is to build something similar to Hugo, but for the Open Knowledge Format.

It would provide a command-line application with commands such as:

• format: Cleans .md files (e.g., removes unnecessary empty lines).
• validate: Checks that all files in the directory are valid.
• serve: Runs a local web server that displays a website generated from the .md files.
• build: Generates a static website with HTML files created from the .md files, while also preserving the original .md files (so it can be published).

[filipdanisko]

Hi, coincidentally I think I’m working on something very close to this idea.

I have been building an openknowledge CLI for OKF, and some of the pieces you describe already map pretty directly to existing functionality:

• validate maps to openknowledge validate
• serve is close to openknowledge open, which starts a local navigable Markdown/OKF viewer
• build is close to openknowledge to html --out <folder>, which generates a static HTML export
• there is also openknowledge to html --plain for minimal semantic HTML
• and openknowledge to json for tools and AI agents that want a normalized bundle model

So I think we may be thinking in the same direction. I’d be curious whether this matches what you had in mind.

I also think there may be a missing specification layer around publishing and authoring workflows, so I wrote up a related proposal here: #113

Would love your thoughts there too.

[straumat]

Hi :) I think we are working on exaclty the same thing eheh !
I will take a look at #113

[straumat]

Hi !

First release of Kiso, an open source publishing engine that turns Open Knowledge Format (OKF) bundles into static websites for humans and AI agents.

In the same way that Hugo turns Markdown files into a static website, Kiso aims to turn an OKF knowledge base into a structured, browsable, and usable documentation site with llms.txt and sitemap.xml.

You can see how it turns the google example into a documentation website: https://oak-invest.github.io/kiso/examples/kb-google-example/