PrestaShop Technical Documentation Site

This repository contains the sources to build DevDocs - PrestaShop's technical documentation site.

Contributing

• To contribute content, read this guide. Documentation content is tracked in the Docs Repository.
• To update the theme: Submit your Pull Request to the Theme repository.

Rendering the site locally

Using docker compose

1. Clone the repository somewhere on your system:

   git clone --recurse-submodules https://github.com/PrestaShop/devdocs-site.git
   

2. Switch to the devdocs-site directory:

   cd devdocs-site
   

3. Create .env file by .env.example:

   cp .env.example .env
   

4. Launch Hugo service:

   docker compose up hugo
   

5. You can access to the devdocs site at http://localhost:1313

Natively

Setting up your environment

1. Install Hugo. You will need v0.121+ (extended binary)

   • Mac and Linux: Run ./bin/installHugo.sh
   • Windows: Grab the release binary

   Or read the Official install guide.

2. Clone the repository somewhere on your system

   git clone --recurse-submodules https://github.com/PrestaShop/devdocs-site.git
   

Launching the site

1. Switch to the src directory:

   cd /path/to/devdocs-site/src
   

2. Launch Hugo:

   hugo server
   

   You may need to change the path to the hugo binary depending on where it is on your system

3. Done! You can open up the site on your browser.

   It's usually available at http://localhost:1313

   Any change you perform on your data will be updated almost instantly.

Customizing the style

We use Sass for styling, bundled by Hugo itself.

The source files for the main css & js are in the assets directory of the theme's repository.

Deployment

• The sources of this site are hosted on devdocs-site, the Sources repository.
• The Hugo theme of this site is hosted on ps-docs-theme, the Theme repository.
• The content of this site is hosted on docs, the Content Repository.

Every time a contribution is merged inside one of the docs branches, a first GitHub workflow will notify the Sources repository.

Upon being notified, a second GitHub workflow is triggered in devdocs-site, which updates its submodules and commits them.

This commit triggers a third GitHub workflow that will deploy the latest version to devdocs.prestashop-project.org .

Theme updates do not trigger a deployment, consequently following a theme update, the docs website must be deployed manually.

AI assistant access (MCP)

The documentation is also exposed to AI assistants through a Model Context Protocol server, so that tools like Claude, Cursor or ChatGPT answer PrestaShop questions from the actual documentation.

The Hugo build publishes three machine-readable artifacts alongside the site:

Artifact	Contents
/<path>/index.md	raw markdown source of every page
/llms.txt	index of the supported documentation version, per the llms.txt convention
/mcp-index.json	compact page catalogue

The MCP server itself is a small stateless HTTP service in mcp-server/ — GitHub Pages can only serve static files, and MCP requires an endpoint that answers POST requests. It holds no data of its own: it reads the artifacts above and delegates search to the site's existing Algolia DocSearch index, so documentation changes go live without redeploying it.

To run and test the whole thing locally:

npm run mcp:local    # builds the site, serves it, starts the Worker on :8787
npm run mcp:test     # in another terminal

See mcp-server/README.md for setup, deployment and usage.

License

Content from this documentation is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License.