Other Docs & User Guides
Theneo isn't just for API documentation—it also empowers teams to create non-API documents, such as technical guides, onboarding docs, tutorials, help centers, product manuals, and more.
Getting Started from the Theneo Dashboard
- Login to Theneo Dashboard Go to Theneo Dashboard and sign in with your workspace credentials.
- Create a New Project Click on "Create Project" from the dashboard.
- Select “Other Docs” On the project creation page, choose the "Other Docs" option instead of an API format.
- Pick Your Sections You’ll be prompted to choose section templates like:
- Introduction/Overview
- Prerequisites & Installation
- Sample Code & Tutorials
- Supported Libraries
- Usage & Integration
- Troubleshooting & Support
Editing Your Docs in Theneo
Once the project is created, you have two ways to start working on your documentation:
A. Use the Theneo Editor
Enjoy a Notion- and Figma-like editing experience with:
- Rich text formatting
- Drag & drop content blocks
- Real-time editing and live preview
- Easy collaboration with teammates
Everything you need to build modern documentation without writing a single line of code.
B. Import Markdown Using Theneo CLI
Prefer to write in Markdown and keep content locally? You can import Markdown files into Theneo using the CLI.
CLI Usage
theneo import [options]
Options
| The slug of the project you want to update |
| The workspace slug to use (defaults to your primary workspace) |
| Path to the directory containing your generated Markdown |
| Auto-publish the imported content (optional) |
| The version slug of the project (optional) |
| Use a specific CLI profile if configured |
| Show help and usage information |
Example
Usage: theneo import [options]
Update theneo project from generated markdown directory
Options:
--project <project-slug> project slug
--workspace <workspace-slug> Enter workspace slug where the project should be created in, if not present uses default workspace
--dir <directory> Generated theneo project directory
--publish Automatically publish the project (default: false)
--projectVersion <version-slug> Version slug
--profile <string> Use a specific profile from your config file.
-h, --help display help for commandRecommended Layout: Single Page Template
For guides and other non-API docs, such as:
- Tutorials
- Onboarding walkthroughs
- Step-by-step how-tos
We highly recommend using the Single Page Template.
Why Choose the Single Page Template?
Modular Layout | Each section appears on its own page for cleaner, more intuitive navigation. |
Improved Performance | Only the requested page loads, speeding up performance — great for large docs. |
Clear Navigation & URLs | Each section gets a unique URL, perfect for deep linking and sharing. |
Optimized for Guides | Best suited for linear content such as step-by-step instructions or tutorials. |
Better Readability | Reduces scrolling fatigue and offers a more focused, distraction-free experience. |
What made this section unhelpful for you?
On this page
- Other Docs & User Guides