Skip to content

docs(getting-started): list what a fresh install contains and its default module states - #62

Merged
anoziere merged 4 commits into
thelia:mainfrom
ThomasDaSilva:docs/424-fresh-install-contents
Oct 2, 2026
Merged

anoziere merged 4 commits into
thelia:mainfrom
ThomasDaSilva:docs/424-fresh-install-contents

Conversation

@ThomasDaSilva

Copy link
Copy Markdown
Contributor

A new page next to the installation guide answers the question every evaluator asks before installing: what do I get after a fresh install.

It lists the thirteen modules a new shop ships with, in two tables: the ones declared by thelia/thelia-skeleton (useful whatever the theme) and the ones each theme requires because its rendering depends on them. Each row gives the module code, its role in one line, its default state and a link to its repository. A short section explains the difference between shipped and active, how to activate a module, and that an update never rewrites the state the merchant chose. A last section says what is deliberately not shipped and how to add it with Composer.

Placed in docs/getting-started/ and versioned_docs/version-3.0/getting-started/, with sidebar_position: 2.5 so it sits right after "Standard Installation".

Build checked with Node 22: the page is generated and adds no broken link (the broken links the build reports are all in the 2.x pages, unchanged here).

Related: thelia/thelia#3945 (the <enabled-by-default> element), thelia/thelia-skeleton#3, thelia-templates/default-twig#96, thelia-templates/flexy#232 (the module list moving to the skeleton). The default states in the tables reflect those PRs: every module listed is active by default until a module declares otherwise.

@anoziere
anoziere merged commit c1250e5 into thelia:main Oct 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants