a ; "
\n

Give your app an identity: a title, a description and a landing page

\n

In LinkedDataHub everything is a document, and every document is a named graph whose name is the document's URL. Your\n dataspace starts with a single document: the root document at the base URI. It doubles as the app's homepage, so making the app yours starts with describing this one\n document.

\n

In this stage you give the root document a title, a description and a first content block — and see the result render as your\n homepage.

\n
\n
\n \n \n
\n
\n

Open the base URL (e.g. https://localhost:4443/) and authenticate with the owner's WebID certificate. Choose Edit in the action bar's Actions dropdown\n to open the document edit form, change the title to Northwind Traders, fill in the description, and save. Then, in the\n Content layout mode, add an XHTML content block with a short welcome text using the\n XHTML button at the bottom of the page. The Edit\n content guide walks through the block editor in detail.

\n \"Root\n
\n \n
\n
\n

What you now see

\n

Reload the base URL: the homepage now carries your title and welcome text. You have not touched a template, a controller or a database schema — you replaced the description of one\n document, and the UI is a rendering of that description.

\n \"The\n
\n
\n

How this works

\n
    \n
  • Documents — the document hierarchy and how documents map to named graphs
    • \n
  • Content blocks — how rdf:_1, rdf:_2, … sequence a document's content
    • \n
  • HTTP API — the PUT semantics behind ldh put
    • \n
\n
\n

Next: Structure

\n
"^^ . a ; ; "2026-09-29T09:52:42.666Z"^^; ; "Give your app an identity: a title, a description and a landing page"; "Hello dataspace"; ; .