@lexibase/create-rdx 1.0.0-beta.7 → 1.0.0-beta.9

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lexibase/create-rdx",
-  "version": "1.0.0-beta.7",
+  "version": "1.0.0-beta.9",
   "description": "Create a new RDX documentation project.",
   "license": "MIT",
   "bin": {
@@ -13,7 +13,7 @@
     "README.md"
   ],
   "engines": {
-    "node": ">=18.18"
+    "node": ">=20.9"
   },
   "publishConfig": {
     "access": "public"

package/templates/default/README.md

@@ -2,6 +2,8 @@
 
 This documentation site was created with RDX.
 
+Requires Node.js 20.9 or newer. Use a currently supported Node.js LTS release.
+
 ## Development
 
 ```bash
@@ -11,6 +13,20 @@ pnpm dev
 Edit files in `docs/` to create your documentation. RDX creates and maintains
 its internal runtime in `.rdx/`.
 
+## Optional versioning
+
+```bash
+pnpm rdx add versioning
+pnpm rdx version 1.0.0
+```
+
+The first command installs the official plugin, activates it in `rdx.config.ts`
+and prepares the runtime. It preserves existing options and validates the
+configuration before saving it, without creating backup files. Restart `pnpm dev` afterward. Repeated
+activation does not duplicate the plugin or upgrade its installed version.
+If the configuration is too dynamic to edit safely, follow the manual
+instructions printed by the CLI. Installing a package alone does not activate it.
+
 ## Public files
 
 Put images and downloads in the project-root `public/` folder:

package/templates/default/docs/examples/accordion.mdx

@@ -0,0 +1,69 @@
+---
+title: Accordion
+description: Keep optional explanations close without crowding the page.
+link_position: 6
+---
+
+## Frequently asked questions
+
+Use Enter or Space to expand an item. Tab moves between questions and links.
+One item opens at a time; selecting it again closes it.
+
+<Accordion>
+  <AccordionItem value="content">
+    <AccordionTrigger>Where do I write my documentation?</AccordionTrigger>
+    <AccordionContent>
+
+Create folders and `.mdx` files inside **docs/**. Each folder becomes a category
+and each file becomes a page.
+
+Read the [introduction](/docs/init/intro) to get started.
+
+    </AccordionContent>
+  </AccordionItem>
+  <AccordionItem value="preview">
+    <AccordionTrigger>How do I preview my changes?</AccordionTrigger>
+    <AccordionContent>
+
+Run the development server:
+
+```bash
+pnpm dev
+```
+
+<Callout variant="tip" title="Live updates">
+
+Keep the server running while editing your documentation.
+
+</Callout>
+
+    </AccordionContent>
+  </AccordionItem>
+  <AccordionItem value="soon" disabled>
+    <AccordionTrigger>More examples (soon)</AccordionTrigger>
+    <AccordionContent>Not available yet.</AccordionContent>
+  </AccordionItem>
+</Accordion>
+
+## Production checklist
+
+Opening an answer closes the previous one in the same group.
+
+<Accordion>
+  <AccordionItem value="build">
+    <AccordionTrigger>Build for production</AccordionTrigger>
+    <AccordionContent>
+
+Run `pnpm build` to generate the production site.
+
+    </AccordionContent>
+  </AccordionItem>
+  <AccordionItem value="start">
+    <AccordionTrigger>Check the production site</AccordionTrigger>
+    <AccordionContent>
+
+Run `pnpm start` after a successful build.
+
+    </AccordionContent>
+  </AccordionItem>
+</Accordion>

package/templates/default/docs/examples/callouts.mdx

@@ -0,0 +1,56 @@
+---
+title: Callouts
+description: Highlight notes, tips and important information.
+link_position: 4
+---
+
+## Highlight important information
+
+Callouts are included in RDX. No import or plugin is required.
+
+<Callout title="A useful note">
+
+Keep supporting information close to the documentation it explains.
+
+</Callout>
+
+<Callout variant="tip" title="A helpful tip">
+
+You can use **Markdown**, [documentation links](/docs/init/intro), and `inline code` inside a callout.
+
+</Callout>
+
+<Callout variant="success" title="Ready to go">
+
+Your documentation is ready to share.
+
+</Callout>
+
+<Callout variant="warning" title="Before updating">
+
+- Read the release notes.
+- Test your changes before deploying.
+
+</Callout>
+
+<Callout variant="danger" title="Irreversible action">
+
+Deleting the source files permanently removes their content.
+
+</Callout>
+
+<Callout>
+
+A title is optional. The default variant is `note`.
+
+</Callout>
+
+## Syntax
+
+```mdx
+<Callout variant="warning" title="Before updating">
+
+Test your changes before deploying.
+
+</Callout>
+```

package/templates/default/docs/examples/links.mdx

@@ -0,0 +1,38 @@
+---
+title: Document links
+description: Link to documentation files using their relative paths.
+link_position: 7
+---
+
+## Link to a page
+
+Read the [introduction](../init/intro.mdx) or learn how to
+[create a page](../init/getting-started.mdx#create-a-page).
+
+```md
+[Introduction](../init/intro.mdx)
+[Create a page](../init/getting-started.mdx#create-a-page)
+```
+
+RDX resolves these paths relative to this file. When viewing a snapshot,
+links stay inside that snapshot instead of switching to Current.
+
+## Link to a section
+
+Jump to the [tables example](./markdown.mdx#tables), or return to
+[the first section](#link-to-a-page) of this page.
+
+Markdown headings receive automatic IDs. Repeated headings get suffixes such as
+`tables-1`. Relative document links must include the `.mdx` extension.
+
+<Callout title="Keep links portable">
+
+Use forward slashes and match the file's name and capitalization. If a destination
+does not exist in the current version, RDX reports the source file and link to fix.
+
+</Callout>
+
+## Assets and external links
+
+[External links](https://example.com/), `/images/logo.svg` and paths to downloads
+are not rewritten. Put public assets in `public/` and reference them from `/`.

package/templates/default/docs/examples/markdown.mdx

@@ -13,3 +13,50 @@ link_position: 1
 ```ts
 const framework = 'RDX'
 ```
+
+## Tables
+
+| Feature | Available |
+| :------ | --------: |
+| Markdown tables | Yes |
+| Callouts | Yes |
+| Code blocks | Yes |
+| Blockquotes | Yes |
+
+### Five-column comparison
+
+Wider tables scroll horizontally on small screens without widening the page.
+
+| Feature | Description | Status | Plugin | Example |
+| :------ | :---------- | :----: | :----: | :------ |
+| Markdown | Write headings, lists, and paragraphs | Included | Not required | `## Heading` |
+| Callout | Highlight contextual information | Included | Not required | `<Callout>` |
+| Code block | Display source code with a copy button | Included | Not required | `pnpm dev` |
+| Blockquote | Quote a passage or explanation | Included | Not required | `> A quotation` |
+
+## Task lists
+
+- [x] Create a documentation project
+- [ ] Add your own pages
+
+> Keep explanations close to the content they describe.
+>
+> A quotation can contain **formatted text**, [links](/docs/init/intro), and `inline code`.
+
+You can also use ~~strikethrough~~ text.
+
+## Syntax highlighting
+
+Put the language after the opening fence, such as `tsx`, `json`, `bash`, `py`
+or `css`. Colors follow your site's light/dark theme automatically. Unlabelled
+or unknown languages remain readable as plain text.
+
+```tsx
+export function Welcome() {
+  return <h1>Welcome to RDX</h1>
+}
+```
+
+```json
+{ "framework": "RDX", "minimal": true }
+```

package/templates/default/docs/examples/tabs.mdx

@@ -0,0 +1,72 @@
+---
+title: Tabs
+description: Group related examples without leaving the page.
+link_position: 5
+---
+
+## Choose your package manager
+
+Tabs are included in RDX. No import or plugin is required.
+Use the arrow keys to move between tabs and Enter or Space to select one.
+
+<Tabs defaultValue="pnpm">
+  <TabsList aria-label="Package manager">
+    <TabsTrigger value="npm">npm</TabsTrigger>
+    <TabsTrigger value="pnpm">pnpm</TabsTrigger>
+    <TabsTrigger value="yarn">yarn</TabsTrigger>
+  </TabsList>
+  <TabsContent value="npm">
+
+Install dependencies with **npm**:
+
+```bash
+npm install
+```
+
+  </TabsContent>
+  <TabsContent value="pnpm">
+
+Install dependencies with **pnpm**:
+
+```bash
+pnpm install
+```
+
+  </TabsContent>
+  <TabsContent value="yarn">
+
+Install dependencies with **yarn**:
+
+```bash
+yarn install
+```
+
+  </TabsContent>
+</Tabs>
+
+## Keep related information together
+
+Each group works independently. Panels can contain normal Markdown and RDX components.
+
+<Tabs defaultValue="development">
+  <TabsList aria-label="Environment">
+    <TabsTrigger value="development">Development</TabsTrigger>
+    <TabsTrigger value="production">Production</TabsTrigger>
+    <TabsTrigger value="preview" disabled>Preview (soon)</TabsTrigger>
+  </TabsList>
+  <TabsContent value="development">
+
+<Callout variant="tip" title="Live updates">
+
+Run `pnpm dev` and edit your documentation to see changes locally.
+
+</Callout>
+
+  </TabsContent>
+  <TabsContent value="production">
+
+1. Run `pnpm build`.
+2. Run `pnpm start` to check the production site.
+
+  </TabsContent>
+</Tabs>

package/templates/default/package.json

@@ -9,18 +9,18 @@
     "start": "rdx start"
   },
   "dependencies": {
-    "@lexibase/rdx-ui": "^1.0.0-beta.1",
-    "@lexibase/rdx-next": "^1.0.0-beta.8",
-    "next": "^15.5.0",
-    "react": "19.1.0",
-    "react-dom": "19.1.0"
+    "@lexibase/rdx-ui": "1.0.0-beta.2",
+    "@lexibase/rdx-next": "1.0.0-beta.10",
+    "next": "^16.4.2",
+    "react": "19.3.1",
+    "react-dom": "19.3.1"
   },
   "devDependencies": {
     "@types/node": "^22.15.3",
-    "@types/react": "19.1.0",
-    "typescript": "5.9.2"
+    "@types/react": "19.3.0",
+    "typescript": "6.0.3"
   },
   "engines": {
-    "node": ">=18.18"
+    "node": ">=20.9"
   }
 }

package/templates/default/rdx.config.ts

@@ -3,6 +3,8 @@ import { defineConfig } from '@lexibase/rdx-next'
 export default defineConfig({
   title: 'My documentation',
   description: 'Documentation built with RDX.',
+  TOC: false,
+  search: false,
   navbar: {
     title: '',
     actions: {