Standalone Blueprint

[BenjaminHofstetter]

Blueprint is designed as a frontend for an existing knowledge graph, leveraging a Triple Store. It's important to note that the knowledge graph is not exclusive to Blueprint.

However, some users perceive Blueprint (when used with the Docker stack) as a standalone application with its own built-in Triple Store. This leads to questions like, 'How can I add data to Blueprint?

Given the confusion, it might be worth considering the development of a standalone version of Blueprint with an integrated Triple Store. And the ability to add data using Blueprint. This could simplify the user experience and better meet their expectations.

[OliverWoolland]

As a new user (with a limited perspective!) I think it would be reasonable to include an example triplestore in the docker compose stack.

I would welcome the ability to add data via the blueprint UI (perhaps an API as well?) as I would then only have to show users a single portal or expose a single endpoint.

However, as I am using Fuseki as my triplestore I've not had too much trouble so far getting people to add data via the Fuseki web interface. So this approach or similar could be documented in the short term?