Quickstart: create the first project and open it

The shortest way from “the plugin is installed” to “a project exists, carries a hub bar, and your account has a role in it”. Three steps, about ten minutes.

Prerequisites

wkdocore and wkcore are installed and enabled.
You may create pages and manage groups.
The other DevOps packages are optional. A hub whose plugin is absent simply does not appear — it breaks nothing.

Step 1: fix the project root

Admin → Configuration, section wkdocore, setting projectroot. Every namespace directly below it is a project.

Decide this before creating content: it is the one setting that decides what counts as a project at all.

On this installation projectroot is {lang}:projects and projectlangs is de,en,hr,it,sl. The {lang} placeholder is expanded per entry, so a project lives under de:projects:, en:projects: and so on. Existing example: de:projects:dwplugins.

Step 2: create the project by creating a page

Create a page below the root:

en:projects:acme:start

That is the whole procedure. With autodiscover — the default — the project acme now exists, derived from the namespace. There is no registration and no entry to maintain.

If a project should be known before anybody has created content for it, add its slug to knownprojects as well.

Step 3: grant access through groups

Membership is expressed in group names built from roleprefix and the project slug:

@dwdo_acme_maintainers
@dwdo_acme_contributors
@dwdo_acme_readers

Put your account into one of them under Admin → User Manager. There is no second membership store to keep in step with the wiki's users.

The roles sit above the DokuWiki ACL, they do not replace it. The ACL decides who sees a page; the role decides who may operate the project's functions. Without read permission on the namespace the role buys nothing.

Check the result

Open en:projects:acme:start.

Above the content sits the hub bar with Overview, Dashboard, Boards, Repos, Pipelines, Wiki, Queries and Settings — minus those whose plugin is not installed.
Settings appears only if your account holds at least the Maintainer role.
If the bar is missing entirely, your template has no drop-in point for it and fallbacknav is off. On this installation fallbacknav is 0, because the wkbizway template brings its own drop-in point.

A hub can be missing for three quite different reasons, and from the page all three look the same:

Cause	Where to check
The plugin is not installed	Extension Manager
The flag is off	setting `disabledhubs`
The role is too low	the account's groups in the User Manager

Next step

From project to source — the same path from the reader's side.
wkdoworkitems — the first work item, which boards, queries and the dashboard all live off.
wkdoado — the connection to Azure DevOps.
wkdocore (German) — the package page: context object, role model, every setting.