Why Two Terminals?
Decap CMS needs a proxy server to read and write files on your local disk. Luax Pro needs its own server to serve the built site. These are two separate processes, so you run them in two separate terminal windows.
Terminal 1: Luax Build Server
Open your first terminal, navigate to the project folder, and run:
Windows:
luax.bat start
Linux / macOS:
./luax.sh start
You will see:
🚀 Server at http://localhost:8080
Keep this terminal open. It watches for file changes and rebuilds your site automatically.
Terminal 2: Decap CMS Proxy
Open a second terminal in the same project folder. Run:
npx decap-server
You will see:
Decap CMS Proxy Server listening on port 8081
This proxy server is what allows Decap CMS to read and write markdown files in your src/ folder.
Important: Node.js 20+ Required
The npx decap-server command requires Node.js 20 or later. If you see an error about Node version, update Node.js from nodejs.org.
You only need Node.js for the CMS admin panel. You do not need Node.js to build or deploy your Luax site.
Access the Admin Panel
Open your browser and go to:
http://localhost:8080/admin/
You should see the Decap CMS login screen. Because local_backend: true is already configured in public/admin/config.yml, the CMS connects directly to your local files without authentication.
What You See in the Admin Panel
The left sidebar shows your collections:
- Site Settings — metadata, index page, about, contact, docs, FAQ, home, privacy
- Blog Posts — create and edit blog articles
- Projects — create and edit project case studies
- Services — create and edit service pages
- Docs Pages — create and edit documentation pages
Click any collection to see its entries. Click an entry to edit it. Changes are saved directly to the corresponding markdown file in src/.
How Changes Flow
When you edit a page in Decap CMS and click Publish:
1. Decap CMS sends the change to the proxy server on port 8081
2. The proxy server writes the updated markdown file to src/
3. Luax's file watcher detects the change
4. Luax rebuilds the affected page
5. Your browser shows the updated content after a refresh
This gives you a live editing experience without touching a text editor.
Stopping the Servers
To stop either server, press Ctrl+C in its terminal window.
Next Step
Both servers are running and you can edit content through Decap CMS. The next guide covers logging in and understanding the admin interface.