Skip to main content

User manual

Learn to keep your material in Library, write connected notes in Context, and find your knowledge when you need it. You can use dtxWiki in your browser without writing code. AI connections are optional.

Choose your starting point​

ALREADY HAVE ACCESS?Create your first page Sign in to an installed dtxWiki and write a useful note, step by step.SETTING UP DTXWIKI?Installation and access Choose a setup route for your computer or understand what to ask an administrator.FILES AND NOTES TO ORGANIZE?Organize your material Keep original files in Library, then connect them to the pages you write.LOOKING FOR A WORKFLOW?Find your use case Follow a guide for research, product work, team operations, small business, writing or teaching.

For AI access, read MCP connections. If you operate a team server, start with deployment.

From installation to your first useful page​

  1. Choose a setup route. Installation and first sign-in explains Python tools, the npm launcher, and joining a server prepared by an administrator. Pick one route.
  2. Create your account. A new local installation has no default login. Register with email/password or a server-configured external provider, then open a workspace you may access. An SSO account may have no account email or local password. Server administration is a separate permission, explained in installation.
  3. Keep dtxWiki running. The local app processes Library imports and queued account emails in the background by itself, so you do not start a separate worker. The systemd and Docker server setups in this manual run this processing as a separate service. Read Access and background operation for another-device access and background execution.
  4. Write one small Context page. Follow your first workspace, save a draft visible to permitted Editors and Owners, and publish when it is ready for workspace readers.
  5. Set up email only when needed. SMTP is optional. Ordinary sign-in and wiki use work without it. Optional email setup with Gmail covers HTTPS, app passwords, configuration, and checking delivery.

Three useful places​

  • Library holds source material such as uploaded files. A file may need processing before extracted text is available.
  • Context holds pages you write: your explanation, decisions, summaries and references.
  • Chats shows dtxWiki tool operations made by a connected AI client. It is not a transcript of everything you said to that AI.

INTERACTIVE EXPLANATION

From a source to a useful answer

Follow one small decision through three places. You choose what to write and when to share it.

Start with something you can check

Keep the original material in Library. Read it before turning it into a claim.

Your next action

Open the material and identify the passage you actually need.

An uploaded file may need processing before its extracted text is available.

A source excerpt

Fictional user interview · 7 October

“I found the settings, but I did not know which option to choose first.”

Observation: a new user needs a first task, not only a list of features.

Library

Step 1 of 3 · Keep the source

Fictional example. These controls explain a workflow; they do not operate dtxWiki.

Think of Library as your reference shelf and Context as your working notebook. Write one small page that will help you with a real next step; you do not need a large knowledge system to begin.

A small first exercise​

  1. Create a Context page called My project.
  2. Write what you are trying to achieve, what you already know, and one open question.
  3. Save the draft, which permitted workspace Editors and Owners may read. Decide separately whether to request review or publish for workspace readers.
  4. Add a second page with a decision or source summary, then link the pages.
  5. Next time you return, use Search to find the background. If you turn on the experimental Ask menu in Settings → Labs, you can also ask a question about it.

Choose a more detailed use case when you are ready: research, product work, operations, running a small business, creative writing or teaching.

What stays under your control​

Your installation stores its data in an environment you or your administrator manage. Workspace permissions, page workflow and MCP credential scopes determine access. If you connect an external AI service, permitted material that it reads may also be processed by that provider. Read privacy and security before using confidential information.

Not sure what a term means? Keep the glossary open alongside the guide.

Continue with the 0.2 workflows​

Read the v0.2.1 release notes for features and upgrade requirements. After linking pages, explore their document graph, then enable personal Labs and the Owner setting for the Knowledge Map. Inbox collects notices addressed to you. Use Account management for sign-in methods and deletion scope.

Version basis: verified product README.