🚀 MyZubster Knowledge Graph: MONERO / ART-001
We have introduced an interactive Knowledge Graph experience for the MyZubster ecosystem.
The goal is to transform isolated knowledge pages into a connected network where people can explore articles, sources, concepts, and related topics through stable, shareable links.
🔗 Open the main knowledge node:
https://myzubster-knowledge.vercel.app/conoscenze?domain=MONERO&id=ART-001
What we built
The first implementation introduces a dedicated /conoscenze route and an interactive graph for the MONERO knowledge domain.
The initial graph contains:
• ART-001 — Introduction to Monero
• ART-002 — Privacy in Monero
• ART-003 — Monero Transactions
• SRC-001 — Monero documentation
• CON-PRIVACY — Privacy
• CON-OSS — Open Source
Every article is identified by two stable values:
domain + article ID
For example:
domain = MONERO
id = ART-001
These values produce the public URL:
https://myzubster-knowledge.vercel.app/conoscenze?domain=MONERO&id=ART-001
This structure allows MyZubster to support many independent knowledge domains without creating a different application for every subject.
Future examples may include:
MONERO / ART-001
KEFIR / ART-001
PERMACULTURE / ART-001
SOUND-SYSTEM / ART-001
CYBERSECURITY / ART-001
How to use the Knowledge Graph
- Open the main knowledge page:
https://myzubster-knowledge.vercel.app/conoscenze?domain=MONERO&id=ART-001
- Select a node in the graph.
The information panel will display:
• node type;
• identifier;
• title;
• description;
• available destination or source.
- Use the filters to focus the graph.
The available filters are:
• All;
• Articles;
• Sources;
• Concepts.
- Open a related article.
Select an article node and use the “Open article” action. The page will load the corresponding domain + id URL.
You can also open articles directly:
🔐 Privacy in Monero — ART-002
https://myzubster-knowledge.vercel.app/conoscenze?domain=MONERO&id=ART-002
🔄 Monero Transactions — ART-003
https://myzubster-knowledge.vercel.app/conoscenze?domain=MONERO&id=ART-003
- Open a source.
Select a source node to inspect its information, then follow the external source link when available.
- Share the current knowledge node.
Copy the complete URL from the browser. Because the domain and article ID are part of the address, another person can open the same node directly.
How the system works
The current implementation uses React 18 and structured knowledge records inside the MyZubster frontend.
The application reads the URL parameters:
/conoscenze?domain=MONERO&id=ART-001
It then uses MONERO:ART-001 as the internal lookup key.
The selected article provides:
• its title and summary;
• its tags;
• relationships with other articles;
• connected sources;
• connected concepts.
The interface converts this structured record into graph nodes and connections.
The interaction flow is:
Public URL
→ domain and article ID
→ structured knowledge record
→ graph nodes and relationships
→ interactive exploration
→ related knowledge
The graph is therefore generated from knowledge data instead of being permanently hard-coded into the visual layout.
How developers can add a new article
- Open the knowledge data file:
frontend/src/data/knowledge.js
- Add a new record using a unique
DOMAIN:ARTICLE-IDkey.
Example:
'MONERO:ART-004': {
id: 'ART-004',
domain: 'MONERO',
title: 'New Monero Article',
summary: 'A concise explanation of the topic.',
tags: ['monero', 'documentation'],
relations: [
{
id: 'ART-001',
label: 'Introduction'
}
],
sources: [
{
id: 'SRC-002',
title: 'Source title',
url: 'https://example.org/source'
}
],
concepts: [
{
id: 'CON-EXAMPLE',
title: 'Example concept'
}
]
}
- Connect the new article to an existing article.
Add a relation to the relevant record:
relations: [
{
id: 'ART-004',
label: 'New topic'
}
]
- Run the frontend build:
cd frontend
npm run build
- Check that the article opens correctly:
/conoscenze?domain=MONERO&id=ART-004
- Commit the source files and publish the change through the normal GitHub and Vercel workflow.
How contributors should prepare knowledge
Before adding a new record, contributors should provide:
• a unique article ID;
• a clear title;
• a concise summary;
• the correct knowledge domain;
• relevant tags;
• relationships with existing articles;
• reliable sources;
• clearly named concepts.
Contributors should not present unsupported claims as verified knowledge. Sources, limitations, review status, and uncertainty should remain visible whenever relevant.
A relationship between two nodes means that the subjects are connected. It does not automatically prove that a claim is correct, scientifically validated, or endorsed by another organization.
Technical implementation
The feature was implemented in the MyZubster React frontend with:
• a new KnowledgeGraphPage component;
• responsive graph styling;
• structured MONERO knowledge data;
• /conoscenze and /knowledge routes;
• filters for different node types;
• navigation between related articles;
• external source links;
• mobile and desktop layouts.
The production build completed successfully before the changes were merged into the main branch.
💻 Source repository:
https://github.com/MyZubster-Ecosystem/myzubster
🔎 Implementation commit:
https://github.com/MyZubster-Ecosystem/myzubster/commit/43c7d966
What comes next
The next development phase can move the structured knowledge records into a dedicated API or versioned knowledge repository.
That evolution would allow:
• automatic graph generation across many domains;
• server-side validation;
• collaborative editing;
• article review states;
• source provenance;
• backlinks between articles;
• search and discovery;
• larger multi-domain graphs;
• integration with Zorgax and other MyZubster services.
The long-term direction is a shared knowledge network where community members can learn, document, verify, connect, and transmit knowledge without losing its sources or context.
Explore the first node:
https://myzubster-knowledge.vercel.app/conoscenze?domain=MONERO&id=ART-001
