NeoWiki Demo - User contributions [en]

NeoWiki

2026-04-30T12:36:32Z

NeoWiki: Importing NeoWiki demo data

Main Page

2026-04-24T22:46:26Z

NeoWiki: Importing NeoWiki demo data

<div style="max-width:1200px; font-size: 1.15rem">
Welcome to the NeoWiki demo wiki!

NeoWiki turns your wiki into a collaborative graph database by letting you store and query structured information.
Information is stored in versioned document form inside wiki pages. The latest version is also stored in
graph databases, via which it can be queried.

NeoWiki is in the experimental proof-of-concept phase. It is not production-ready, public interfaces will change,
big structural changes will happen, and key functionality is still missing.

This demo exists to gather feedback to inform further development.

You can find [https://github.com/ProfessionalWiki/NeoWiki/tree/master/docs technical documentation] in the
[https://github.com/ProfessionalWiki/NeoWiki NeoWiki git repository]. You can also
[https://github.com/ProfessionalWiki/NeoWiki/issues view the issue tracker] or
[https://professional.wiki/en/contact contact Professional Wiki] (the maintainer of NeoWiki).
</div>

== Discover NeoWiki Step by Step ==

Terminology is explained in [https://github.com/ProfessionalWiki/NeoWiki/blob/master/docs/Glossary.md the glossary].

'''As a reader:'''

* View a Subject: [[Professional Wiki]]
* View a Schema: [[Schema:Company]]

'''As an editor:'''

* Edit a Subject: [[Professional Wiki]] (login required)
* Edit a Schema: either via a Subject using it, i.e. [[Professional Wiki]], or directly on the Schema page, i.e. [[Schema:Company]]
* Create a Subject: Create a new page with any content, then click "Create subject" in the NeoWiki section of the sidebar.

'''As a developer:'''

* View Subject JSON: [[Special:NeoJson/ACME_Inc]] (developer UI, normal users will not see JSON. [https://github.com/ProfessionalWiki/NeoWiki/blob/master/docs/SubjectFormat.md View docs])
* Query the graph database: [[Cypher|Cypher raw example]]
* Read values in wikitext: [[Value parser function]]
* Read values in Lua: [[Lua Data Access]]
* [[#REST_API_endpoints|Explore the REST API]]

== European Museums ==

A dataset of European museums, artists, and artworks showcasing cross-schema relations and rich property types.

'''Museums:''' [[Musee dOrsay|Musée d'Orsay]], [[Rijksmuseum]], [[Kunsthistorisches Museum]], [[Museo del Prado]]

'''Artists:''' [[Claude Monet]], [[Vincent van Gogh]], [[Johannes Vermeer]], [[Diego Velazquez|Diego Velázquez]], [[Gustav Klimt]]

'''Artworks:''' [[Water Lilies]], [[Starry Night Over the Rhone|Starry Night Over the Rhône]], [[The Milkmaid]], [[Las Meninas]], [[The Kiss]], [[The Art of Painting]]

'''Exhibitions:''' [[Impressionist Masters]], [[Dutch Golden Age Highlights]]

'''Cities:''' [[Paris]], [[Amsterdam]], [[Vienna]], [[Madrid]]

'''Overview:''' [[Museum Collection]]

== Demo Pages ==

* Simple page with automatic infobox and edit form: [[NeoWiki]], [[ProWiki]]
* Subject with relations: [[Professional Wiki]]
* Multiple subjects per page: [[ACME Inc]]
* Wikibase Statement emulation: [[Berlin]]
* Displaying data from other pages: [[Company Infoboxes]]
* [[Reactive UI example]]

== Schemas and Layouts ==

'''Schemas''' define the structure of your data. For instance, you can define that an Employee has a compensation
in EUR with a value between 0 and 1000000.

* [[Schema:Company]], [[Schema:Product]], [[Schema:Employee]]
* [[Schema:Museum]], [[Schema:Artist]], [[Schema:Artwork]], [[Schema:Exhibition]], [[Schema:Attendance]]
* [[Special:Schemas|View all schemas]]

'''Layouts''' customize how Subjects are displayed by selecting which properties to show and in what order.

* [[Layout:CompanyOverview]]
* [[Special:Layouts|View all layouts]]

== REST API Endpoints ==

An auto-generated OpenAPI 3.0 spec describes the REST API:

* [{{SERVER}}{{SCRIPTPATH}}/rest.php/specs/v0/module/- NeoWiki OpenAPI spec] — <code>/rest.php/specs/v0/module/-</code>
* [{{SERVER}}{{SCRIPTPATH}}/rest.php/specs/v0/discovery Module discovery] — <code>/rest.php/specs/v0/discovery</code>

Example endpoint URL: <code>{{SERVER}}{{SCRIPTPATH}}/rest.php/neowiki/v0/subject/s1demo4sssssss1</code>

=== Read Endpoints ===

* <code>GET /neowiki/v0/subject/{subjectId}</code> Gets the JSON definition of a subject
* <code>GET /neowiki/v0/schema/{schemaName}</code> Gets the JSON definition of a schema

=== Write Endpoints ===

These require a CSRF token, first obtained via <code>api.php?action=query&format=json&meta=tokens&type=csrf</code>

* <code>POST /neowiki/v0/page/{pageId}/mainSubject</code> Creates a new main subject
* <code>POST /neowiki/v0/page/{pageId}/childSubjects</code> Creates a new child subject
* <code>PATCH /neowiki/v0/subject/{subjectId}</code> Updates a subject
* <code>DELETE /neowiki/v0/subject/{subjectId}</code> Deletes a subject

These endpoints are designed for the NeoWiki frontend. They are not a complete general purpose API yet.

Professional Wiki

2026-04-24T19:41:35Z

NeoWiki: Importing NeoWiki demo data

Schema:Company

2026-04-24T19:01:03Z

NeoWiki: Importing NeoWiki demo data

{
"propertyDefinitions": {
"Founded at": {
"type": "number"
},
"Websites": {
"type": "url",
"multiple": true
},
"Main product": {
"type": "relation",
"relation": "Has main product",
"targetSchema": "Product"
},
"Products": {
"type": "relation",
"relation": "Has product",
"targetSchema": "Product",
"multiple": true
},
"Status": {
"type": "select",
"options": [
{
"id": "o1demo1aaaaaaa1",
"label": "Active"
},
{
"id": "o1demo1aaaaaaa2",
"label": "Inactive"
},
{
"id": "o1demo1aaaaaaa3",
"label": "Acquired"
},
{
"id": "o1demo1aaaaaaa4",
"label": "Dissolved"
}
],
"required": true
},
"World domination progress": {
"type": "number",
"default": 0
}
}
}

ACME Inc

2026-04-23T18:19:16Z

NeoWiki: Importing NeoWiki demo data

The Main Subject of this page is the Company ACME Inc, shown in the infobox.

The page also contains Child Subjects which are Products.

TODO: show a table here, for now see the "View or edit JSON" developer link in the NeoWiki section of the sidebar

You can have as many Child Subjects on a page as you want. For instance you could also define Employees.

TODO: show a table here, for now see the "View or edit JSON" developer link in the NeoWiki section of the sidebar

It is up to you to choose if you define products, employees and other business objects on their own pages or if you
define multiple subjects on a single page.

Professional Wiki

2026-04-23T18:19:16Z

NeoWiki: Importing NeoWiki demo data

Schema:Company

2026-04-23T18:19:16Z

NeoWiki: Importing NeoWiki demo data

Module:NeoWikiDemo

2026-04-20T11:27:48Z

NeoWiki: Importing NeoWiki demo data

local p = {}
local nw = require( 'mw.neowiki' )

function p.value( frame )
local property = frame.args[1]
local page = frame.args['page']

local options = nil
if page then
options = { page = page }
end

local v = nw.getValue( property, options )

return tostring( v or '' )
end

function p.values( frame )
local property = frame.args[1]
local page = frame.args['page']
local separator = frame.args['separator'] or ', '

local options = nil
if page then
options = { page = page }
end

local all = nw.getAll( property, options )

if not all then
return ''
end

local parts = {}
for _, item in ipairs( all ) do
parts[#parts + 1] = tostring( item )
end

return table.concat( parts, separator )
end

function p.subject( frame )
local page = frame.args[1]
local s = nw.getMainSubject( page )

if not s then
return 'No subject found'
end

local rows = {}
rows[#rows + 1] = '{| class="wikitable"'
rows[#rows + 1] = '! Property !! Type !! Value(s)'

for name, stmt in pairs( s.statements ) do
local vals = {}
for _, v in ipairs( stmt.values ) do
if type( v ) == 'table' then
vals[#vals + 1] = v.label or v.target or tostring( v )
else
vals[#vals + 1] = tostring( v )
end
end
rows[#rows + 1] = '|-'
rows[#rows + 1] = '| ' .. name .. ' || ' .. stmt.type .. ' || ' .. table.concat( vals, ', ' )
end

rows[#rows + 1] = '|}'
return table.concat( rows, '\n' )
end

function p.children( frame )
local page = frame.args[1]
local children = nw.getChildSubjects( page )

if not children or #children == 0 then
return 'No child subjects'
end

local parts = {}
for _, child in ipairs( children ) do
parts[#parts + 1] = "'''" .. child.label .. "''' (" .. child.schema .. ")"
end

return table.concat( parts, ', ' )
end

local function renderRowsAsTable( rows, columns )
if #rows == 0 then
return 'No results'
end

if not columns then
columns = {}
for k in pairs( rows[1] ) do
columns[#columns + 1] = k
end
table.sort( columns )
end

local out = { '{| class="wikitable"', '! ' .. table.concat( columns, ' !! ' ) }

for _, row in ipairs( rows ) do
local cells = {}
for _, col in ipairs( columns ) do
local v = row[col]
cells[#cells + 1] = v == nil and '' or tostring( v )
end
out[#out + 1] = '|-'
out[#out + 1] = '| ' .. table.concat( cells, ' || ' )
end

out[#out + 1] = '|}'
return table.concat( out, '\n' )
end

function p.query( frame )
return renderRowsAsTable( nw.query( frame.args[1] ) )
end

function p.productsFoundedSince( frame )
local year = tonumber( frame.args[1] ) or 2000

return renderRowsAsTable( nw.query(
'MATCH (n:Product) WHERE n.`Available since` >= $year ' ..
'RETURN n.name AS name, n.`Available since` AS year ORDER BY year',
{ year = year }
) )
end

local function propertyDetails( prop )
local details = {}

if prop.type == 'select' then
local labels = {}
for _, option in ipairs( prop.options ) do
labels[#labels + 1] = option.label
end
details[#details + 1] = 'options: ' .. table.concat( labels, ', ' )
elseif prop.type == 'number' then
if prop.minimum ~= nil then
details[#details + 1] = 'min: ' .. tostring( prop.minimum )
end
if prop.maximum ~= nil then
details[#details + 1] = 'max: ' .. tostring( prop.maximum )
end
if prop.precision ~= nil then
details[#details + 1] = 'precision: ' .. tostring( prop.precision )
end
elseif prop.type == 'relation' then
details[#details + 1] = 'targetSchema: ' .. prop.targetSchema
details[#details + 1] = 'relation: ' .. prop.relation
elseif prop.type == 'text' or prop.type == 'url' then
if prop.multiple then
details[#details + 1] = 'multiple: true'
end
if prop.uniqueItems then
details[#details + 1] = 'uniqueItems: true'
end
end

return table.concat( details, ', ' )
end

function p.schema( frame )
local schema = nw.getSchema( frame.args[1] )

if not schema then
return 'Schema not found'
end

local rows = {}
for _, prop in ipairs( schema.properties ) do
rows[#rows + 1] = {
Name = prop.name,
Type = prop.type,
Required = prop.required and 'Yes' or 'No',
Details = propertyDetails( prop ),
}
end

return renderRowsAsTable( rows, { 'Name', 'Type', 'Required', 'Details' } )
end

return p

Lua Data Access

2026-04-20T11:27:47Z

NeoWiki: Importing NeoWiki demo data

This page demonstrates the <code>mw.neowiki</code> Lua API for accessing NeoWiki structured data from templates and modules.

The examples use [[Module:NeoWikiDemo]], a demo module included with NeoWiki.

== Reading Property Values ==

<code>mw.neowiki.getValue()</code> returns a single scalar value. <code>mw.neowiki.getAll()</code> returns all values as a table.

{| class="wikitable"
! Property !! getValue !! getAll
|-
| Founded at || {{#invoke:NeoWikiDemo|value|Founded at|page=ACME Inc}} || {{#invoke:NeoWikiDemo|values|Founded at|page=ACME Inc}}
|-
| Websites || {{#invoke:NeoWikiDemo|value|Websites|page=ACME Inc}} || {{#invoke:NeoWikiDemo|values|Websites|page=ACME Inc}}
|-
| Products (relations) || {{#invoke:NeoWikiDemo|value|Products|page=ACME Inc}} || {{#invoke:NeoWikiDemo|values|Products|page=ACME Inc}}
|}

== Full Subject Data ==

<code>mw.neowiki.getMainSubject()</code> returns all data for a Subject as a Lua table, enabling templates to render complete data views.

=== Professional Wiki ===

{{#invoke:NeoWikiDemo|subject|Professional Wiki}}

=== ACME Inc ===

{{#invoke:NeoWikiDemo|subject|ACME Inc}}

== Child Subjects ==

<code>mw.neowiki.getChildSubjects()</code> returns all non-main Subjects on a page.

Child subjects on [[ACME Inc]]: {{#invoke:NeoWikiDemo|children|ACME Inc}}

== Running Cypher Queries ==

<code>mw.neowiki.query()</code> runs a read-only Cypher query and returns each row as a Lua table keyed
by the <code>RETURN</code> aliases. Use it when a single-property lookup is not enough — for example
to join Subjects, sort results, or list all Subjects of a given type.

=== Listing all Companies ===

<syntaxhighlight lang="cypher">
MATCH (n:Company) RETURN n.name, n.id
</syntaxhighlight>

{{#invoke:NeoWikiDemo|query|MATCH (n:Company) RETURN n.name, n.id}}

=== Parameterised query: Products available since a given year ===

Templates should always pass values via the <code>params</code> table instead of concatenating into the query string.

<syntaxhighlight lang="lua">
nw.query(
'MATCH (n:Product) WHERE n.`Available since` >= $year ' ..
'RETURN n.name AS name, n.`Available since` AS year ORDER BY year',
{ year = 2010 }
)
</syntaxhighlight>

Products available since 2010: {{#invoke:NeoWikiDemo|productsFoundedSince|2010}}

== Inspecting a Schema ==

<code>mw.neowiki.getSchema()</code> returns a Schema definition as a Lua table, including all property names, types, and type-specific attributes. This enables templates to render or validate any schema without hardcoding property names.

=== Company ===

{{#invoke:NeoWikiDemo|schema|Company}}

=== Employee ===

{{#invoke:NeoWikiDemo|schema|Employee}}

== Module Source ==

The demo module uses these <code>mw.neowiki</code> functions:

<syntaxhighlight lang="lua">
local nw = require( 'mw.neowiki' )

-- Read a single value (always returns a scalar or nil)
nw.getValue( 'Founded at' ) --> 2005
nw.getValue( 'Products' ) --> "Foo" (first value only)

-- Read all values (always returns a 1-indexed table or nil)
nw.getAll( 'Products' ) --> { "Foo", "Bar", "Baz" }

-- Get full subject data
local s = nw.getMainSubject( 'ACME Inc' )
s.id, s.label, s.schema, s.statements

-- Get child subjects
local children = nw.getChildSubjects( 'ACME Inc' )

-- Run a read-only Cypher query
local rows = nw.query(
'MATCH (n:Product) WHERE n.`Available since` >= $year RETURN n.name, n.`Available since`',
{ year = 2010 }
)
</syntaxhighlight>

See [[Module:NeoWikiDemo]] for the full source.

Main Page

2026-04-20T11:27:46Z

NeoWiki: Importing NeoWiki demo data

<div style="max-width:1200px; font-size: 1.15rem">
Welcome to the NeoWiki demo wiki!

NeoWiki turns your wiki into a collaborative graph database by letting you store and query structured information.
Information is stored in versioned document form inside wiki pages. The latest version is also stored in
graph databases, via which it can be queried.

NeoWiki is in the experimental proof-of-concept phase. It is not production-ready, public interfaces will change,
big structural changes will happen, and key functionality is still missing.

This demo exists to gather feedback to inform further development.

You can find [https://github.com/ProfessionalWiki/NeoWiki/tree/master/docs technical documentation] in the
[https://github.com/ProfessionalWiki/NeoWiki NeoWiki git repository]. You can also
[https://github.com/ProfessionalWiki/NeoWiki/issues view the issue tracker] or
[https://professional.wiki/en/contact contact Professional Wiki] (the maintainer of NeoWiki).
</div>

== Discover NeoWiki Step by Step ==

Terminology is explained in [https://github.com/ProfessionalWiki/NeoWiki/blob/master/docs/Glossary.md the glossary].

'''As a reader:'''

* View a Subject: [[Professional Wiki]]
* View a Schema: [[Schema:Company]]

'''As an editor:'''

* Edit a Subject: [[Professional Wiki]] (login required)
* Edit a Schema: either via a Subject using it, i.e. [[Professional Wiki]], or directly on the Schema page, i.e. [[Schema:Company]]
* Create a Subject: Create a new page with any content, then click "Create subject" in the NeoWiki section of the sidebar.

'''As a developer:'''

* View Subject JSON: [[Special:NeoJson/ACME_Inc]] (developer UI, normal users will not see JSON. [https://github.com/ProfessionalWiki/NeoWiki/blob/master/docs/SubjectFormat.md View docs])
* Query the graph database: [[Cypher|Cypher raw example]]
* Read values in wikitext: [[Value parser function]]
* Read values in Lua: [[Lua Data Access]]
* [[#REST_API_endpoints|Explore the REST API]]

== European Museums ==

A dataset of European museums, artists, and artworks showcasing cross-schema relations and rich property types.

'''Museums:''' [[Musee dOrsay|Musée d'Orsay]], [[Rijksmuseum]], [[Kunsthistorisches Museum]], [[Museo del Prado]]

'''Artists:''' [[Claude Monet]], [[Vincent van Gogh]], [[Johannes Vermeer]], [[Diego Velazquez|Diego Velázquez]], [[Gustav Klimt]]

'''Artworks:''' [[Water Lilies]], [[Starry Night Over the Rhone|Starry Night Over the Rhône]], [[The Milkmaid]], [[Las Meninas]], [[The Kiss]], [[The Art of Painting]]

'''Exhibitions:''' [[Impressionist Masters]], [[Dutch Golden Age Highlights]]

'''Cities:''' [[Paris]], [[Amsterdam]], [[Vienna]], [[Madrid]]

'''Overview:''' [[Museum Collection]]

== Demo Pages ==

* Simple page with automatic infobox and edit form: [[NeoWiki]], [[ProWiki]]
* Subject with relations: [[Professional Wiki]]
* Multiple subjects per page: [[ACME Inc]]
* Wikibase Statement emulation: [[Berlin]]
* Displaying data from other pages: [[Company Infoboxes]]
* [[Reactive UI example]]

== Schemas and Layouts ==

'''Schemas''' define the structure of your data. For instance, you can define that an Employee has a compensation
in EUR with a value between 0 and 1000000.

* [[Schema:Company]], [[Schema:Product]], [[Schema:Employee]]
* [[Schema:Museum]], [[Schema:Artist]], [[Schema:Artwork]], [[Schema:Exhibition]], [[Schema:Attendance]]
* [[Special:Schemas|View all schemas]]

'''Layouts''' customize how Subjects are displayed by selecting which properties to show and in what order.

* [[Layout:CompanyOverview]]
* [[Special:Layouts|View all layouts]]

== REST API Endpoints ==

We will have OpenAPI docs later. For now, you can find a complete and up-to-date list by looking at the
[https://github.com/ProfessionalWiki/NeoWiki/blob/master/extension.json MediaWiki API route definitions].
Search for "RestRoutes".

Example URL: https://neowiki.dev/w/rest.php/neowiki/v0/subject/s1demo4sssssss1

=== Read Endpoints ===

* <code>GET /neowiki/v0/subject/{subjectId}</code> Gets the JSON definition of a subject
* <code>GET /neowiki/v0/schema/{schemaName}</code> Gets the JSON definition of a schema

=== Write Endpoints ===

These require a CSRF token, first obtained via <code>api.php?action=query&format=json&meta=tokens&type=csrf</code>

* <code>POST /neowiki/v0/page/{pageId}/mainSubject</code> Creates a new main subject
* <code>POST /neowiki/v0/page/{pageId}/childSubjects</code> Creates a new child subject
* <code>PATCH /neowiki/v0/subject/{subjectId}</code> Updates a subject
* <code>DELETE /neowiki/v0/subject/{subjectId}</code> Deletes a subject

These endpoints are designed for the NeoWiki frontend. They are not a complete general purpose API yet.

ACME Inc

2026-04-20T11:27:46Z

NeoWiki: Importing NeoWiki demo data

Professional Wiki

2026-04-20T11:27:45Z

NeoWiki: Importing NeoWiki demo data

Schema:Company

2026-04-20T11:27:45Z

NeoWiki: Importing NeoWiki demo data

Schema:Everything

2026-04-20T11:27:45Z

NeoWiki: Importing NeoWiki demo data

{
"description": "Everything currently almost supported, maybe.",
"propertyDefinitions": {
"string/text": {
"type": "text"
},
"string/text (required)": {
"type": "text",
"required": true
},
"string/text (many)": {
"type": "text",
"multiple": true
},
"string/text (duplicates)": {
"type": "text",
"multiple": true,
"uniqueItems": false
},
"string/text (default)": {
"type": "text",
"default": "Default value"
},
"string/url": {
"type": "url"
},
"string/url (many)": {
"type": "url",
"multiple": true
},
"number/number": {
"type": "number"
},
"number/number (w precision)": {
"type": "number",
"precision": 2
},
"number/number (w bounds)": {
"type": "number",
"minimum": 42,
"maximum": 100
},
"select/select": {
"type": "select",
"options": [
{
"id": "o1demo1aaaaaab1",
"label": "Draft"
},
{
"id": "o1demo1aaaaaab2",
"label": "Review"
},
{
"id": "o1demo1aaaaaab3",
"label": "Approved"
},
{
"id": "o1demo1aaaaaab4",
"label": "Archived"
}
]
},
"select/select (required)": {
"type": "select",
"options": [
{
"id": "o1demo1aaaaaac1",
"label": "Low"
},
{
"id": "o1demo1aaaaaac2",
"label": "Medium"
},
{
"id": "o1demo1aaaaaac3",
"label": "High"
},
{
"id": "o1demo1aaaaaac4",
"label": "Critical"
}
],
"required": true
},
"select/select (many)": {
"type": "select",
"options": [
{
"id": "o1demo1aaaaaad1",
"label": "Red"
},
{
"id": "o1demo1aaaaaad2",
"label": "Green"
},
{
"id": "o1demo1aaaaaad3",
"label": "Blue"
},
{
"id": "o1demo1aaaaaad4",
"label": "Yellow"
}
],
"multiple": true
},
"relation/relation": {
"type": "relation",
"relation": "Has product",
"targetSchema": "Product"
},
"relation/relation (many)": {
"type": "relation",
"relation": "Has product",
"targetSchema": "Product",
"multiple": true
}
}
}

Value parser function

2026-04-16T13:39:47Z

NeoWiki: Importing NeoWiki demo data

This page demonstrates the <code>neowiki_value</code> parser function for reading values from Subjects.

== Reading from the Current Page's Subject ==

When used on a page with a Subject, <code>neowiki_value</code> reads from that page's main Subject by default.
Visit [[ACME Inc]] to see these values in the infobox.

{| class="wikitable"
! Property !! Syntax !! Result
|-
| Founded at || <code><nowiki>{{#neowiki_value: Founded at | page=ACME Inc}}</nowiki></code> || {{#neowiki_value: Founded at | page=ACME Inc}}
|-
| Websites || <code><nowiki>{{#neowiki_value: Websites | page=ACME Inc}}</nowiki></code> || {{#neowiki_value: Websites | page=ACME Inc}}
|-
| Products || <code><nowiki>{{#neowiki_value: Products | page=ACME Inc}}</nowiki></code> || {{#neowiki_value: Products | page=ACME Inc}}
|-
| World domination progress || <code><nowiki>{{#neowiki_value: World domination progress | page=ACME Inc}}</nowiki></code> || {{#neowiki_value: World domination progress | page=ACME Inc}}%
|-
| Missing property || <code><nowiki>{{#neowiki_value: Nonexistent | page=ACME Inc}}</nowiki></code> || (empty) {{#neowiki_value: Nonexistent | page=ACME Inc}}
|}

== Custom Separator ==

Multi-valued properties use <code>, </code> as separator by default. Use <code>separator=</code> to change it:

* Default: {{#neowiki_value: Products | page=ACME Inc}}
* Semicolons: {{#neowiki_value: Products | page=ACME Inc | separator=;}}
* Pipe: {{#neowiki_value: Products | page=ACME Inc | separator={{!}}}}

== Cross-Page Lookups ==

Read values from any page using the <code>page=</code> parameter:

* Professional Wiki was founded at: {{#neowiki_value: Founded at | page=Professional Wiki}}
* ACME Inc was founded at: {{#neowiki_value: Founded at | page=ACME Inc}}

== Inline Usage ==

The parser function can be used inline in running text:

{{#neowiki_value: Products | page=Professional Wiki}} are products of Professional Wiki, which was founded in {{#neowiki_value: Founded at | page=Professional Wiki}}.

Main Page

2026-04-16T13:39:47Z

NeoWiki: Importing NeoWiki demo data

<div style="max-width:1200px; font-size: 1.15rem">
Welcome to the NeoWiki demo wiki!

NeoWiki turns your wiki into a collaborative graph database by letting you store and query structured information.
Information is stored in versioned document form inside wiki pages. The latest version is also stored in
graph databases, via which it can be queried.

NeoWiki is in the experimental proof-of-concept phase. It is not production-ready, public interfaces will change,
big structural changes will happen, and key functionality is still missing.

This demo exists to gather feedback to inform further development.

You can find [https://github.com/ProfessionalWiki/NeoWiki/tree/master/docs technical documentation] in the
[https://github.com/ProfessionalWiki/NeoWiki NeoWiki git repository]. You can also
[https://github.com/ProfessionalWiki/NeoWiki/issues view the issue tracker] or
[https://professional.wiki/en/contact contact Professional Wiki] (the maintainer of NeoWiki).
</div>

== Discover NeoWiki Step by Step ==

Terminology is explained in [https://github.com/ProfessionalWiki/NeoWiki/blob/master/docs/Glossary.md the glossary].

'''As a reader:'''

* View a Subject: [[Professional Wiki]]
* View a Schema: [[Schema:Company]]

'''As an editor:'''

* Edit a Subject: [[Professional Wiki]] (login required)
* Edit a Schema: either via a Subject using it, i.e. [[Professional Wiki]], or directly on the Schema page, i.e. [[Schema:Company]]
* Create a Subject: Create a new page with any content and click "Create subject". That button is there just for the PoC.

'''As a developer:'''

* View Subject JSON: [[Special:NeoJson/ACME_Inc]] (developer UI, normal users will not see JSON. [https://github.com/ProfessionalWiki/NeoWiki/blob/master/docs/SubjectFormat.md View docs])
* Query the graph database: [[Cypher|Cypher raw example]]
* Read values in wikitext: [[Value parser function]]
* Read values in Lua: [[Lua Data Access]]
* [[#REST_API_endpoints|Explore the REST API]]

== European Museums ==

A dataset of European museums, artists, and artworks showcasing cross-schema relations and rich property types.

'''Museums:''' [[Musee dOrsay|Musée d'Orsay]], [[Rijksmuseum]], [[Kunsthistorisches Museum]], [[Museo del Prado]]

'''Artists:''' [[Claude Monet]], [[Vincent van Gogh]], [[Johannes Vermeer]], [[Diego Velazquez|Diego Velázquez]], [[Gustav Klimt]]

'''Artworks:''' [[Water Lilies]], [[Starry Night Over the Rhone|Starry Night Over the Rhône]], [[The Milkmaid]], [[Las Meninas]], [[The Kiss]], [[The Art of Painting]]

'''Exhibitions:''' [[Impressionist Masters]], [[Dutch Golden Age Highlights]]

'''Cities:''' [[Paris]], [[Amsterdam]], [[Vienna]], [[Madrid]]

'''Overview:''' [[Museum Collection]]

== Demo Pages ==

* Simple page with automatic infobox and edit form: [[NeoWiki]], [[ProWiki]]
* Subject with relations: [[Professional Wiki]]
* Multiple subjects per page: [[ACME Inc]]
* Wikibase Statement emulation: [[Berlin]]
* Displaying data from other pages: [[Company Infoboxes]]
* [[Reactive UI example]]

== Schemas and Layouts ==

'''Schemas''' define the structure of your data. For instance, you can define that an Employee has a compensation
in EUR with a value between 0 and 1000000.

* [[Schema:Company]], [[Schema:Product]], [[Schema:Employee]]
* [[Schema:Museum]], [[Schema:Artist]], [[Schema:Artwork]], [[Schema:Exhibition]], [[Schema:Attendance]]
* [[Special:Schemas|View all schemas]]

'''Layouts''' customize how Subjects are displayed by selecting which properties to show and in what order.

* [[Layout:CompanyOverview]]
* [[Special:Layouts|View all layouts]]

== REST API Endpoints ==

We will have OpenAPI docs later. For now, you can find a complete and up-to-date list by looking at the
[https://github.com/ProfessionalWiki/NeoWiki/blob/master/extension.json MediaWiki API route definitions].
Search for "RestRoutes".

Example URL: https://neowiki.dev/w/rest.php/neowiki/v0/subject/s1demo4sssssss1

=== Read Endpoints ===

* <code>GET /neowiki/v0/subject/{subjectId}</code> Gets the JSON definition of a subject
* <code>GET /neowiki/v0/schema/{schemaName}</code> Gets the JSON definition of a schema

=== Write Endpoints ===

These require a CSRF token, first obtained via <code>api.php?action=query&format=json&meta=tokens&type=csrf</code>

* <code>POST /neowiki/v0/page/{pageId}/mainSubject</code> Creates a new main subject
* <code>POST /neowiki/v0/page/{pageId}/childSubjects</code> Creates a new child subject
* <code>PATCH /neowiki/v0/subject/{subjectId}</code> Updates a subject
* <code>DELETE /neowiki/v0/subject/{subjectId}</code> Deletes a subject

These endpoints are designed for the NeoWiki frontend. They are not a complete general purpose API yet.

Property Values

2026-04-09T10:57:42Z

NeoWiki: Importing NeoWiki demo data

This page demonstrates the <code>neowiki_value</code> parser function for reading individual property values from Subjects.

== Reading from the Current Page's Subject ==

When used on a page with a Subject, <code>neowiki_value</code> reads from that page's main Subject by default.
Visit [[ACME Inc]] to see these values in the infobox.

{| class="wikitable"
! Property !! Syntax !! Result
|-
| Founded at || <code><nowiki>{{#neowiki_value: Founded at | page=ACME Inc}}</nowiki></code> || {{#neowiki_value: Founded at | page=ACME Inc}}
|-
| Websites || <code><nowiki>{{#neowiki_value: Websites | page=ACME Inc}}</nowiki></code> || {{#neowiki_value: Websites | page=ACME Inc}}
|-
| Products || <code><nowiki>{{#neowiki_value: Products | page=ACME Inc}}</nowiki></code> || {{#neowiki_value: Products | page=ACME Inc}}
|-
| World domination progress || <code><nowiki>{{#neowiki_value: World domination progress | page=ACME Inc}}</nowiki></code> || {{#neowiki_value: World domination progress | page=ACME Inc}}%
|-
| Missing property || <code><nowiki>{{#neowiki_value: Nonexistent | page=ACME Inc}}</nowiki></code> || (empty) {{#neowiki_value: Nonexistent | page=ACME Inc}}
|}

== Custom Separator ==

Multi-valued properties use <code>, </code> as separator by default. Use <code>separator=</code> to change it:

* Default: {{#neowiki_value: Products | page=ACME Inc}}
* Semicolons: {{#neowiki_value: Products | page=ACME Inc | separator=;}}
* Pipe: {{#neowiki_value: Products | page=ACME Inc | separator={{!}}}}

== Cross-Page Lookups ==

Read values from any page using the <code>page=</code> parameter:

* Professional Wiki was founded at: {{#neowiki_value: Founded at | page=Professional Wiki}}
* ACME Inc was founded at: {{#neowiki_value: Founded at | page=ACME Inc}}

== Inline Usage ==

The parser function can be used inline in running text:

{{#neowiki_value: Products | page=Professional Wiki}} are products of Professional Wiki, which was founded in {{#neowiki_value: Founded at | page=Professional Wiki}}.

Professional Wiki

2026-04-09T10:57:42Z

NeoWiki: Importing NeoWiki demo data

Module:NeoWikiDemo

2026-04-07T16:09:53Z

NeoWiki: Importing NeoWiki demo data

Lua Data Access

2026-04-07T16:09:53Z

NeoWiki: Importing NeoWiki demo data

Company Infoboxes

2026-04-07T16:09:52Z

NeoWiki: Importing NeoWiki demo data

Reactive UI example

2026-04-07T16:09:52Z

NeoWiki: Importing NeoWiki demo data

This page shows Subjects defined on [[ACME Inc]].

Data is displayed multiple times in different forms, demonstrating automatic and immediate update everywhere once you edit it in one location.

{{#view: s1demo5aaaaaaa1}}

{{#view: s1demo5aaaaaaa1 | CompanyOverview}}

{{#view: s1demo5aaaaaaa1}}

'''Placeholder Text'''

How to explain? How to describe? Even the omniscient viewpoint quails.

A singleton star, reddish and dim. A ragtag of asteroids, and a single planet, more like a moon. In this era the star hung near the galactic plane, just beyond the Beyond. The structures on the surface were gone from normal view, pulverized into regolith across a span of aeons. The treasure was far underground, beneath a network of passages, in a single room filled with black. Information at the quantum density, undamaged. Maybe five billion years had passed since the archive was lost to the nets.

The curse of the mummy's tomb, a comic image from mankind's own prehistory, lost before time. They had laughed when they said it, laughed with joy at the treasure . . . and determined to be cautious just the same. They would live here a year or five, the little company from Straum, the archaeologist programmers, their families and schools. A year or five would be enough to handmake the protocols, to skim the top and identify the treasure's origin in time and space, to learn a secret or two that would make Straumli Realm rich. And when they were done, they would sell the location; perhaps build a network link (but chancier that—this was beyond the Beyond; who knew what Power might grab what they'd found).

So now there was a tiny settlement on the surface, and they called it the High Lab. It was really just humans playing with an old library. It should be safe, using their own automation, clean and benign. This library wasn't a living creature, or even possessed of automation (which here might mean something more, far more, than human). They would look and pick and choose, and be careful not to be burned. . . . Humans starting fires and playing with the flames.

The archive informed the automation. Data structures were built, recipes followed. A local network was built, faster than anything on Straum, but surely safe. Nodes were added, modified by other recipes. The archive was a friendly place, with hierarchies of translation keys that led them along. Straum itself would be famous for this.

Main Page

2026-04-07T16:09:52Z

NeoWiki: Importing NeoWiki demo data

<div style="max-width:1200px; font-size: 1.15rem">
Welcome to the NeoWiki demo wiki!

NeoWiki turns your wiki into a collaborative graph database by letting you store and query structured information.
Information is stored in versioned document form inside wiki pages. The latest version is also stored in
graph databases, via which it can be queried.

NeoWiki is in the experimental proof-of-concept phase. It is not production-ready, public interfaces will change,
big structural changes will happen, and key functionality is still missing.

This demo exists to gather feedback to inform further development.

You can find [https://github.com/ProfessionalWiki/NeoWiki/tree/master/docs technical documentation] in the
[https://github.com/ProfessionalWiki/NeoWiki NeoWiki git repository]. You can also
[https://github.com/ProfessionalWiki/NeoWiki/issues view the issue tracker] or
[https://professional.wiki/en/contact contact Professional Wiki] (the maintainer of NeoWiki).
</div>

== Discover NeoWiki Step by Step ==

Terminology is explained in [https://github.com/ProfessionalWiki/NeoWiki/blob/master/docs/Glossary.md the glossary].

'''As a reader:'''

* View a Subject: [[Professional Wiki]]
* View a Schema: [[Schema:Company]]

'''As an editor:'''

* Edit a Subject: [[Professional Wiki]] (login required)
* Edit a Schema: either via a Subject using it, i.e. [[Professional Wiki]], or directly on the Schema page, i.e. [[Schema:Company]]
* Create a Subject: Create a new page with any content and click "Create subject". That button is there just for the PoC.

'''As a developer:'''

* View Subject JSON: [[Special:NeoJson/ACME_Inc]] (developer UI, normal users will not see JSON. [https://github.com/ProfessionalWiki/NeoWiki/blob/master/docs/SubjectFormat.md View docs])
* Query the graph database: [[Cypher|Cypher raw example]]
* [[#REST_API_endpoints|Explore the REST API]]

== European Museums ==

A dataset of European museums, artists, and artworks showcasing cross-schema relations and rich property types.

'''Museums:''' [[Musee dOrsay|Musée d'Orsay]], [[Rijksmuseum]], [[Kunsthistorisches Museum]], [[Museo del Prado]]

'''Artists:''' [[Claude Monet]], [[Vincent van Gogh]], [[Johannes Vermeer]], [[Diego Velazquez|Diego Velázquez]], [[Gustav Klimt]]

'''Artworks:''' [[Water Lilies]], [[Starry Night Over the Rhone|Starry Night Over the Rhône]], [[The Milkmaid]], [[Las Meninas]], [[The Kiss]], [[The Art of Painting]]

'''Exhibitions:''' [[Impressionist Masters]], [[Dutch Golden Age Highlights]]

'''Cities:''' [[Paris]], [[Amsterdam]], [[Vienna]], [[Madrid]]

'''Overview:''' [[Museum Collection]]

== Other Demo Pages ==

* Simple page with automatic infobox and edit form: [[NeoWiki]], [[ProWiki]]
* Subject with relations: [[Professional Wiki]]
* Multiple subjects per page: [[ACME Inc]]
* Wikibase Statement emulation: [[Berlin]]
* Displaying data from other pages: [[Company Infoboxes]]
* [[Reactive UI example]]
* Lua/Scribunto data access: [[Lua Data Access]]

'''Schemas''' allow you to define the structure of your data. For instance, you can define that a Employee has a
compensation in EUR with a value between 0 and 1000000.

* [[Schema:Company]]
* [[Schema:Product]]
* [[Schema:Employee]]
* [[Schema:Museum]]
* [[Schema:Artist]]
* [[Schema:Artwork]]
* [[Schema:Exhibition]]
* [[Schema:Attendance]]
* [[Special:Schemas|View all schemas]]

== REST API Endpoints ==

We will have OpenAPI docs later. For now, you can find a complete and up-to-date list by looking at the
[https://github.com/ProfessionalWiki/NeoWiki/blob/master/extension.json MediaWiki API route definitions].
Search for "RestRoutes".

Example URL: https://neowiki.dev/w/rest.php/neowiki/v0/subject/s1demo4sssssss1

=== Read Endpoints ===

* <code>GET /neowiki/v0/subject/{subjectId}</code> Gets the JSON definition of a subject
* <code>GET /neowiki/v0/schema/{schemaName}</code> Gets the JSON definition of a schema

=== Write Endpoints ===

These require a CSRF token, first obtained via <code>api.php?action=query&format=json&meta=tokens&type=csrf</code>

* <code>POST /neowiki/v0/page/{pageId}/mainSubject</code> Creates a new main subject
* <code>POST /neowiki/v0/page/{pageId}/childSubjects</code> Creates a new child subject
* <code>PATCH /neowiki/v0/subject/{subjectId}</code> Updates a subject
* <code>DELETE /neowiki/v0/subject/{subjectId}</code> Deletes a subject

These endpoints are designed for the NeoWiki frontend. They are not a complete general purpose API yet.

ACME Inc

2026-04-07T16:09:52Z

NeoWiki: Importing NeoWiki demo data

The Main Subject of this page is the Company ACME Inc, shown in the infobox.

The page also contains Child Subjects which are Products.

TODO: show a table here, for now see the "View or edit JSON" developer UI at the bottom

You can have as many Child Subjects on a page as you want. For instance you could also define Employees.

TODO: show a table here, for now see the "View or edit JSON" developer UI at the bottom

It is up to you to choose if you define products, employees and other business objects on their own pages or if you
define multiple subjects on a single page.

Professional Wiki

2026-04-07T16:09:51Z

NeoWiki: Importing NeoWiki demo data

Musee dOrsay

2026-04-07T16:09:49Z

NeoWiki: Importing NeoWiki demo data

The Musée d'Orsay is a museum in Paris, France, on the Left Bank of the Seine. It is housed in the former Gare d'Orsay,
a Beaux-Arts railway station built between 1898 and 1900.

The museum holds mainly French art dating from 1848 to 1914, including paintings, sculptures, furniture, and photography.
It is home to the world's largest collection of Impressionist and Post-Impressionist masterpieces by painters including
Monet, Manet, Degas, Renoir, Cézanne, Seurat, Sisley, Gauguin, and Van Gogh.

{{#view: sEpfwLY8VcdQZJL}}
{{#view: sEpfwLY8WnceT2y}}
{{#view: sEpfwLY8XjJ8gE1}}

Schema:Company

2026-04-07T16:09:33Z

NeoWiki: Importing NeoWiki demo data

{
"propertyDefinitions": {
"Founded at": {
"type": "number"
},
"Websites": {
"type": "url",
"multiple": true
},
"Main product": {
"type": "relation",
"relation": "Has main product",
"targetSchema": "Product"
},
"Products": {
"type": "relation",
"relation": "Has product",
"targetSchema": "Product",
"multiple": true
},
"Status": {
"type": "select",
"options": [
"Active",
"Inactive",
"Acquired",
"Dissolved"
],
"required": true
},
"World domination progress": {
"type": "number",
"default": 0
}
}
}

Schema:Everything

2026-04-07T16:09:33Z

NeoWiki: Importing NeoWiki demo data

{
"description": "Everything currently almost supported, maybe.",
"propertyDefinitions": {
"string/text": {
"type": "text"
},
"string/text (required)": {
"type": "text",
"required": true
},
"string/text (many)": {
"type": "text",
"multiple": true
},
"string/text (duplicates)": {
"type": "text",
"multiple": true,
"uniqueItems": false
},
"string/text (default)": {
"type": "text",
"default": "Default value"
},
"string/url": {
"type": "url"
},
"string/url (many)": {
"type": "url",
"multiple": true
},
"number/number": {
"type": "number"
},
"number/number (w precision)": {
"type": "number",
"precision": 2
},
"number/number (w bounds)": {
"type": "number",
"minimum": 42,
"maximum": 100
},
"select/select": {
"type": "select",
"options": [
"Draft",
"Review",
"Approved",
"Archived"
]
},
"select/select (required)": {
"type": "select",
"options": [
"Low",
"Medium",
"High",
"Critical"
],
"required": true
},
"select/select (many)": {
"type": "select",
"options": [
"Red",
"Green",
"Blue",
"Yellow"
],
"multiple": true
},
"relation/relation": {
"type": "relation",
"relation": "Has product",
"targetSchema": "Product"
},
"relation/relation (many)": {
"type": "relation",
"relation": "Has product",
"targetSchema": "Product",
"multiple": true
}
}
}

Reactive UI example

2026-03-30T11:17:00Z

NeoWiki: Importing NeoWiki demo data

This page shows Subjects defined on [[ACME Inc]].

Data is displayed multiple times in different forms, demonstrating automatic and immediate update everywhere once you edit it in one location.

{{#view: s1demo1aaaaaaa1}}

{{#view: s1demo1aaaaaaa4}}
{{#view: s1demo1aaaaaaa3}}
{{#view: s1demo1aaaaaaa2}}
{{#view: s1demo1aaaaaaa1}}

== Placeholder Text ==

How to explain? How to describe? Even the omniscient viewpoint quails.

A singleton star, reddish and dim. A ragtag of asteroids, and a single planet, more like a moon. In this era the star hung near the galactic plane, just beyond the Beyond. The structures on the surface were gone from normal view, pulverized into regolith across a span of aeons. The treasure was far underground, beneath a network of passages, in a single room filled with black. Information at the quantum density, undamaged. Maybe five billion years had passed since the archive was lost to the nets.

The curse of the mummy's tomb, a comic image from mankind's own prehistory, lost before time. They had laughed when they said it, laughed with joy at the treasure . . . and determined to be cautious just the same. They would live here a year or five, the little company from Straum, the archaeologist programmers, their families and schools. A year or five would be enough to handmake the protocols, to skim the top and identify the treasure's origin in time and space, to learn a secret or two that would make Straumli Realm rich. And when they were done, they would sell the location; perhaps build a network link (but chancier that—this was beyond the Beyond; who knew what Power might grab what they'd found).

So now there was a tiny settlement on the surface, and they called it the High Lab. It was really just humans playing with an old library. It should be safe, using their own automation, clean and benign. This library wasn't a living creature, or even possessed of automation (which here might mean something more, far more, than human). They would look and pick and choose, and be careful not to be burned. . . . Humans starting fires and playing with the flames.

The archive informed the automation. Data structures were built, recipes followed. A local network was built, faster than anything on Straum, but surely safe. Nodes were added, modified by other recipes. The archive was a friendly place, with hierarchies of translation keys that led them along. Straum itself would be famous for this.

Rijksmuseum

2026-03-30T11:17:00Z

NeoWiki: Importing NeoWiki demo data

Layout:CompanyOverview

2026-03-25T11:18:00Z

NeoWiki: Importing NeoWiki demo data

{
"schema": "Company",
"type": "infobox",
"description": "Shows only founding year and world domination progress",
"displayRules": [
{
"property": "World domination progress"
},
{
"property": "Founded at"
}
]
}

Museum Collection

2026-03-25T11:01:57Z

NeoWiki: Importing NeoWiki demo data

This page shows infoboxes with data from various museum and artwork pages, demonstrating cross-page subject display.

== Museums ==

{{#view: sEpfwJLnx3Kze3t}}
{{#view: sEpfwJLnxyQy6vR}}
{{#view: sEpfwJLnyuR5E4i}}
{{#view: sEpfwJLnzqsDMs5}}

== Selected Artworks ==

{{#view: sEpfwJLo6Si6kJo}}
{{#view: sEpfwJLo8KqKsUP}}
{{#view: sEpfwJLoABDZ18D}}

Company Infoboxes

2026-03-25T11:01:57Z

NeoWiki: Importing NeoWiki demo data

This page shows infoboxes with data from the [[Professional Wiki]] and [[ACME Inc]] pages.

== Default Infobox ==

Shows all properties in schema-defined order:

{{#view: s1demo1aaaaaaa1}}
{{#view: s1demo5sssssss1}}

== With a Layout ==

The same subjects rendered through the [[Layout:CompanyOverview]] Layout, which only shows "World domination progress" and "Founded at":

{{#view: s1demo1aaaaaaa1 | CompanyOverview}}
{{#view: s1demo5sssssss1 | CompanyOverview}}

Reactive UI example

2026-03-25T11:01:57Z

NeoWiki: Importing NeoWiki demo data

This page shows Subjects defined on [[ACME Inc]].

Data is displayed multiple times in different forms, demonstrating automatic and immediate update everywhere once you edit it in one location.

{{#view: s1demo1aaaaaaa1}}

{{#view: s1demo1aaaaaaa4}}
{{#view: s1demo1aaaaaaa3}}
{{#view: s1demo1aaaaaaa2}}
{{#view: s1demo1aaaaaaa1}}

## Placeholder Text

How to explain? How to describe? Even the omniscient viewpoint quails.

A singleton star, reddish and dim. A ragtag of asteroids, and a single planet, more like a moon. In this era the star hung near the galactic plane, just beyond the Beyond. The structures on the surface were gone from normal view, pulverized into regolith across a span of aeons. The treasure was far underground, beneath a network of passages, in a single room filled with black. Information at the quantum density, undamaged. Maybe five billion years had passed since the archive was lost to the nets.

The curse of the mummy's tomb, a comic image from mankind's own prehistory, lost before time. They had laughed when they said it, laughed with joy at the treasure . . . and determined to be cautious just the same. They would live here a year or five, the little company from Straum, the archaeologist programmers, their families and schools. A year or five would be enough to handmake the protocols, to skim the top and identify the treasure's origin in time and space, to learn a secret or two that would make Straumli Realm rich. And when they were done, they would sell the location; perhaps build a network link (but chancier that—this was beyond the Beyond; who knew what Power might grab what they'd found).

So now there was a tiny settlement on the surface, and they called it the High Lab. It was really just humans playing with an old library. It should be safe, using their own automation, clean and benign. This library wasn't a living creature, or even possessed of automation (which here might mean something more, far more, than human). They would look and pick and choose, and be careful not to be burned. . . . Humans starting fires and playing with the flames.

The archive informed the automation. Data structures were built, recipes followed. A local network was built, faster than anything on Straum, but surely safe. Nodes were added, modified by other recipes. The archive was a friendly place, with hierarchies of translation keys that led them along. Straum itself would be famous for this.

Museum Collection

2026-03-24T14:44:46Z

NeoWiki: Importing NeoWiki demo data

This page shows infoboxes with data from various museum and artwork pages, demonstrating cross-page subject display.

== Museums ==

<div class="ext-neowiki-view" data-mw-neowiki-subject-id="sEpfwJLnx3Kze3t"></div>
<div class="ext-neowiki-view" data-mw-neowiki-subject-id="sEpfwJLnxyQy6vR"></div>
<div class="ext-neowiki-view" data-mw-neowiki-subject-id="sEpfwJLnyuR5E4i"></div>
<div class="ext-neowiki-view" data-mw-neowiki-subject-id="sEpfwJLnzqsDMs5"></div>

== Selected Artworks ==

<div class="ext-neowiki-view" data-mw-neowiki-subject-id="sEpfwJLo6Si6kJo"></div>
<div class="ext-neowiki-view" data-mw-neowiki-subject-id="sEpfwJLo8KqKsUP"></div>
<div class="ext-neowiki-view" data-mw-neowiki-subject-id="sEpfwJLoABDZ18D"></div>

Company Infoboxes

2026-03-24T14:44:46Z

NeoWiki: Importing NeoWiki demo data

<div class="ext-neowiki-view" data-mw-neowiki-subject-id="s1demo1aaaaaaa1"></div>
<div class="ext-neowiki-view" data-mw-neowiki-subject-id="s1demo5sssssss1"></div>

This page shows infoboxes with data from the [[Professional Wiki]] and [[ACME Inc]] pages.

This is achieved with the following wikitext that references the IDs of the subjects:

<pre>
<div class="ext-neowiki-view" data-mw-neowiki-subject-id="s1demo1aaaaaaa1"></div>
<div class="ext-neowiki-view" data-mw-neowiki-subject-id="s1demo5sssssss1"></div>
</pre>

This syntax is temporary and will change as we move out of the proof-of-concept phase.

Reactive UI example

2026-03-24T14:44:46Z

NeoWiki: Importing NeoWiki demo data

This page shows Subjects defined on [[ACME Inc]].

Data is displayed multiple times in different forms, demonstrating automatic and immediate update everywhere once you edit it in one location.

<div class="ext-neowiki-view" data-mw-neowiki-subject-id="s1demo1aaaaaaa1"></div>

<div class="ext-neowiki-view" data-mw-neowiki-subject-id="s1demo1aaaaaaa4"></div>
<div class="ext-neowiki-view" data-mw-neowiki-subject-id="s1demo1aaaaaaa3"></div>
<div class="ext-neowiki-view" data-mw-neowiki-subject-id="s1demo1aaaaaaa2"></div>
<div class="ext-neowiki-view" data-mw-neowiki-subject-id="s1demo1aaaaaaa1"></div>

## Placeholder Text

How to explain? How to describe? Even the omniscient viewpoint quails.

A singleton star, reddish and dim. A ragtag of asteroids, and a single planet, more like a moon. In this era the star hung near the galactic plane, just beyond the Beyond. The structures on the surface were gone from normal view, pulverized into regolith across a span of aeons. The treasure was far underground, beneath a network of passages, in a single room filled with black. Information at the quantum density, undamaged. Maybe five billion years had passed since the archive was lost to the nets.

The curse of the mummy's tomb, a comic image from mankind's own prehistory, lost before time. They had laughed when they said it, laughed with joy at the treasure . . . and determined to be cautious just the same. They would live here a year or five, the little company from Straum, the archaeologist programmers, their families and schools. A year or five would be enough to handmake the protocols, to skim the top and identify the treasure's origin in time and space, to learn a secret or two that would make Straumli Realm rich. And when they were done, they would sell the location; perhaps build a network link (but chancier that—this was beyond the Beyond; who knew what Power might grab what they'd found).

So now there was a tiny settlement on the surface, and they called it the High Lab. It was really just humans playing with an old library. It should be safe, using their own automation, clean and benign. This library wasn't a living creature, or even possessed of automation (which here might mean something more, far more, than human). They would look and pick and choose, and be careful not to be burned. . . . Humans starting fires and playing with the flames.

The archive informed the automation. Data structures were built, recipes followed. A local network was built, faster than anything on Straum, but surely safe. Nodes were added, modified by other recipes. The archive was a friendly place, with hierarchies of translation keys that led them along. Straum itself would be famous for this.

Main Page

2026-03-24T14:44:46Z

NeoWiki: Importing NeoWiki demo data

<div style="max-width:1200px; font-size: 1.15rem">
Welcome to the NeoWiki demo wiki!

NeoWiki turns your wiki into a collaborative graph database by letting you store and query structured information.
Information is stored in versioned document form inside wiki pages. The latest version is also stored in
graph databases, via which it can be queried.

NeoWiki is in the experimental proof-of-concept phase. It is not production-ready, public interfaces will change,
big structural changes will happen, and key functionality is still missing.

This demo exists to gather feedback to inform further development.

You can find [https://github.com/ProfessionalWiki/NeoWiki/tree/master/docs technical documentation] in the
[https://github.com/ProfessionalWiki/NeoWiki NeoWiki git repository]. You can also
[https://github.com/ProfessionalWiki/NeoWiki/issues view the issue tracker] or
[https://professional.wiki/en/contact contact Professional Wiki] (the maintainer of NeoWiki).
</div>

== Discover NeoWiki Step by Step ==

Terminology is explained in [https://github.com/ProfessionalWiki/NeoWiki/blob/master/docs/Glossary.md the glossary].

'''As a reader:'''

* View a Subject: [[Professional Wiki]]
* View a Schema: [[Schema:Company]]

'''As an editor:'''

* Edit a Subject: [[Professional Wiki]] (login required)
* Edit a Schema: either via a Subject using it, i.e. [[Professional Wiki]], or directly on the Schema page, i.e. [[Schema:Company]]
* Create a Subject: Create a new page with any content and click "Create subject". That button is there just for the PoC.

'''As a developer:'''

* View Subject JSON: [[Special:NeoJson/ACME_Inc]] (developer UI, normal users will not see JSON. [https://github.com/ProfessionalWiki/NeoWiki/blob/master/docs/SubjectFormat.md View docs])
* Query the graph database: [[Cypher|Cypher raw example]]
* [[#REST_API_endpoints|Explore the REST API]]

== European Museums ==

A dataset of European museums, artists, and artworks showcasing cross-schema relations and rich property types.

'''Museums:''' [[Musee dOrsay|Musée d'Orsay]], [[Rijksmuseum]], [[Kunsthistorisches Museum]], [[Museo del Prado]]

'''Artists:''' [[Claude Monet]], [[Vincent van Gogh]], [[Johannes Vermeer]], [[Diego Velazquez|Diego Velázquez]], [[Gustav Klimt]]

'''Artworks:''' [[Water Lilies]], [[Starry Night Over the Rhone|Starry Night Over the Rhône]], [[The Milkmaid]], [[Las Meninas]], [[The Kiss]], [[The Art of Painting]]

'''Exhibitions:''' [[Impressionist Masters]], [[Dutch Golden Age Highlights]]

'''Cities:''' [[Paris]], [[Amsterdam]], [[Vienna]], [[Madrid]]

'''Overview:''' [[Museum Collection]]

== Other Demo Pages ==

* Simple page with automatic infobox and edit form: [[NeoWiki]], [[ProWiki]]
* Subject with relations: [[Professional Wiki]]
* Multiple subjects per page: [[ACME Inc]]
* Wikibase Statement emulation: [[Berlin]]
* Displaying data from other pages: [[Company Infoboxes]]
* [[Reactive UI example]]

'''Schemas''' allow you to define the structure of your data. For instance, you can define that a Employee has a
compensation in EUR with a value between 0 and 1000000.

* [[Schema:Company]]
* [[Schema:Product]]
* [[Schema:Employee]]
* [[Schema:Museum]]
* [[Schema:Artist]]
* [[Schema:Artwork]]
* [[Schema:Exhibition]]
* [[Schema:Attendance]]
* [[Special:Schemas|View all schemas]]

== REST API Endpoints ==

We will have OpenAPI docs later. For now, you can find a complete and up-to-date list by looking at the
[https://github.com/ProfessionalWiki/NeoWiki/blob/master/extension.json MediaWiki API route definitions].
Search for "RestRoutes".

Example URL: https://neowiki.dev/w/rest.php/neowiki/v0/subject/s1demo4sssssss1

=== Read Endpoints ===

* <code>GET /neowiki/v0/subject/{subjectId}</code> Gets the JSON definition of a subject
* <code>GET /neowiki/v0/schema/{schemaName}</code> Gets the JSON definition of a schema

=== Write Endpoints ===

These require a CSRF token, first obtained via <code>api.php?action=query&format=json&meta=tokens&type=csrf</code>

* <code>POST /neowiki/v0/page/{pageId}/mainSubject</code> Creates a new main subject
* <code>POST /neowiki/v0/page/{pageId}/childSubjects</code> Creates a new child subject
* <code>PATCH /neowiki/v0/subject/{subjectId}</code> Updates a subject
* <code>DELETE /neowiki/v0/subject/{subjectId}</code> Deletes a subject

These endpoints are designed for the NeoWiki frontend. They are not a complete general purpose API yet.

Professional Wiki

2026-03-24T14:44:44Z

NeoWiki: Importing NeoWiki demo data

Museum Collection

2026-02-03T14:41:03Z

NeoWiki: Importing NeoWiki demo data

This page shows infoboxes with data from various museum and artwork pages, demonstrating cross-page subject display.

== Museums ==

<div class="ext-neowiki-view" data-subject-id="sEpfwJLnx3Kze3t"></div>
<div class="ext-neowiki-view" data-subject-id="sEpfwJLnxyQy6vR"></div>
<div class="ext-neowiki-view" data-subject-id="sEpfwJLnyuR5E4i"></div>
<div class="ext-neowiki-view" data-subject-id="sEpfwJLnzqsDMs5"></div>

== Selected Artworks ==

<div class="ext-neowiki-view" data-subject-id="sEpfwJLo6Si6kJo"></div>
<div class="ext-neowiki-view" data-subject-id="sEpfwJLo8KqKsUP"></div>
<div class="ext-neowiki-view" data-subject-id="sEpfwJLoABDZ18D"></div>

Main Page

2026-02-03T14:41:03Z

NeoWiki: Importing NeoWiki demo data

<div style="max-width:1200px; font-size: 1.15rem">
Welcome to the NeoWiki demo wiki!

NeoWiki turns your wiki into a collaborative graph database by letting you store and query structured information.
Information is stored in versioned document form inside of wiki pages. The latest version is also stored in
graph databases via which it can be queried.

NeoWiki is in the experimental proof of concept phase. It is not production ready, public interfaces will change,
big structural changes will happen, and key functionality is still missing.

This demo exists to gather feedback to inform further development. ([https://professional.wiki/en/contact Contact Professional Wiki])

You can find [https://github.com/ProfessionalWiki/NeoWiki/tree/master/docs technical documentation] in the
[https://github.com/ProfessionalWiki/NeoWiki NeoWiki git repository].
</div>

== Discover NeoWiki Step by Step ==

Terminology is explained in [https://github.com/ProfessionalWiki/NeoWiki/blob/master/docs/Glossary.md the glossary].

'''As a reader:'''

* View a Subject: [[Professional Wiki]]
* View a Schema: [[Schema:Company]]

'''As an editor:'''

* Edit a Subject: [[Professional Wiki]] (login required)
* Edit a Schema: either via a Subject using it, i.e. [[Professional Wiki]], or directly on the Schema page, i.e. [[Schema:Company]]
* Create a Subject: Create a new page with any content and click "Create subject". That button is there just for the PoC.

'''As a developer:'''

* View Subject JSON: [[Special:NeoJson/ACME_Inc]] (developer UI, normal users will not see JSON. [https://github.com/ProfessionalWiki/NeoWiki/blob/master/docs/SubjectFormat.md View docs])
* Query the graph database: [[Cypher|Cypher raw example]]
* [[#REST_API_endpoints|Explore the REST API]]

== European Museums ==

A dataset of European museums, artists, and artworks showcasing cross-schema relations and rich property types.

'''Museums:''' [[Musee dOrsay|Musée d'Orsay]], [[Rijksmuseum]], [[Kunsthistorisches Museum]], [[Museo del Prado]]

'''Artists:''' [[Claude Monet]], [[Vincent van Gogh]], [[Johannes Vermeer]], [[Diego Velazquez|Diego Velázquez]], [[Gustav Klimt]]

'''Artworks:''' [[Water Lilies]], [[Starry Night Over the Rhone|Starry Night Over the Rhône]], [[The Milkmaid]], [[Las Meninas]], [[The Kiss]], [[The Art of Painting]]

'''Exhibitions:''' [[Impressionist Masters]], [[Dutch Golden Age Highlights]]

'''Cities:''' [[Paris]], [[Amsterdam]], [[Vienna]], [[Madrid]]

'''Overview:''' [[Museum Collection]]

== Other Demo Pages ==

* Simple page with automatic infobox and edit form: [[NeoWiki]], [[ProWiki]]
* Subject with relations: [[Professional Wiki]]
* Multiple subjects per page: [[ACME Inc]]
* Wikibase Statement emulation: [[Berlin]]
* Displaying data from other pages: [[Company Infoboxes]]
* [[Reactive UI example]]

'''Schemas''' allow you to define the structure of your data. For instance, you can define that a Employee has a
compensation in EUR with a value between 0 and 1000000.

* [[Schema:Company]]
* [[Schema:Product]]
* [[Schema:Employee]]
* [[Schema:Museum]]
* [[Schema:Artist]]
* [[Schema:Artwork]]
* [[Schema:Exhibition]]
* [[Schema:Attendance]]
* [{{fullurl:Special:AllPages|from=&to=&namespace=7474}} View all schemas]

== REST API Endpoints ==

We will have OpenAPI docs later. For now, you can find a complete and up-to-date list by looking at the
[https://github.com/ProfessionalWiki/NeoWiki/blob/master/extension.json MediaWiki API route definitions].
Search for "RestRoutes".

Example URL: https://neowiki.dev/w/rest.php/neowiki/v0/subject/s1demo4sssssss1

=== Read Endpoints ===

* <code>GET /neowiki/v0/subject/{subjectId}</code> Gets the JSON definition of a subject
* <code>GET /neowiki/v0/schema/{schemaName}</code> Gets the JSON definition of a schema

=== Write Endpoints ===

These require a CSRF token, first obtained via <code>api.php?action=query&format=json&meta=tokens&type=csrf</code>

* <code>POST /neowiki/v0/page/{pageId}/mainSubject</code> Creates a new main subject
* <code>POST /neowiki/v0/page/{pageId}/childSubjects</code> Creates a new child subject
* <code>PATCH /neowiki/v0/subject/{subjectId}</code> Updates a subject
* <code>DELETE /neowiki/v0/subject/{subjectId}</code> Deletes a subject

These endpoints are designed for the NeoWiki frontend. They are not a complete general purpose API yet.

Dutch Golden Age Highlights

2026-02-03T14:41:03Z

NeoWiki: Importing NeoWiki demo data

Gustav Klimt

2026-02-03T14:41:02Z

NeoWiki: Importing NeoWiki demo data

Kunsthistorisches Museum

2026-02-03T14:41:02Z

NeoWiki: Importing NeoWiki demo data

Paris

2026-02-03T14:41:02Z

NeoWiki: Importing NeoWiki demo data

Starry Night Over the Rhone

2026-02-03T14:41:02Z

NeoWiki: Importing NeoWiki demo data

Impressionist Masters

2026-02-03T14:41:02Z

NeoWiki: Importing NeoWiki demo data

Professional Wiki

2026-02-03T14:41:01Z

NeoWiki: Importing NeoWiki demo data

Musee dOrsay

2026-02-03T14:41:01Z

NeoWiki: Importing NeoWiki demo data

The Musée d'Orsay is a museum in Paris, France, on the Left Bank of the Seine. It is housed in the former Gare d'Orsay, a Beaux-Arts railway station built between 1898 and 1900.

The museum holds mainly French art dating from 1848 to 1914, including paintings, sculptures, furniture, and photography. It is home to the world's largest collection of Impressionist and Post-Impressionist masterpieces by painters including Monet, Manet, Degas, Renoir, Cézanne, Seurat, Sisley, Gauguin, and Van Gogh.

Vienna

2026-02-03T14:41:01Z

NeoWiki: Importing NeoWiki demo data