Skip to main content

Sites Conformes

Sites Conformes (anciennement « Sites Faciles ») vise à permettre la création simplifiée de sites dont le domaine se termine par .gouv.fr.

Basé sur Wagtail, il permet de concevoir rapidement des sites internet conformes aux normes numériques en vigueur.

En particulier, il permet de construire des pages à l’aide de composants prêts à l’emploi issus du Système de design de l’État (DSFR).

Prérequis

Sites Conformes vise à utiliser les dernières versions disponibles de Django (6.0+) et Wagtail.

Les tests automatisés couvrent les versions suivantes :

Déploiement

Architecture

Made with Django Made with Wagtail

Sites Conformes est développé en utilisant le framework Django et le CMS Wagtail. Il est centré autour d’une application principale nommée sites_conformes.core, accompagnée d’applications annexes pour divers types de pages.

Le détail des applications Django, de la structure du dépôt et le schéma d’ensemble sont décrits dans la documentation d’architecture.

Notifications

Le panneau d’information de l’administration peut afficher des notifications (nouveautés, alertes, maintenances) aux utilisateurs qui ont accès au back-office. Ces notifications sont pilotées par le fichier notifications.json à la racine du dépôt.

Pour savoir comment ajouter, modifier ou désactiver une notification, voir la documentation dédiée : NOTIFICATIONS.md.

Droit d’utilisation du DSFR

Ce projet utilise le DSFR et est donc tenu par les conditions d’utilisations suivantes :

⚠️ Utilisation interdite en dehors des sites Internet de l’État

Il est formellement interdit à tout autre acteur d’utiliser le Système de Design de l’État (les administrations territoriales ou tout autre acteur privé) pour des sites web ou des applications. Le Système de Design de l’État représente l’identité numérique de l’État. En cas d’usage à des fins trompeuses ou frauduleuses, l’État se réserve le droit d’entreprendre les actions nécessaires pour y mettre un terme.

Voir les conditions générales d’utilisation.

⚠️ Prohibited Use Outside Government Websites

This Design System is only meant to be used by official French public services' websites and apps. Its main purpose is to make it easy to identify governmental websites for citizens. See terms.

Metadata

Release files for sites-conformes 4.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for sites-conformes 4.3.0
File Size Uploaded Provenance
sites_conformes-4.3.0.tar.gz 7.7 MB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for sites-conformes 4.3.0
File Interpreter ABI Platform
sites_conformes-4.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 15.8 MB

Release files / sites_conformes-4.3.0.tar.gz

Download URL sites_conformes-4.3.0.tar.gz
Size 7.7 MB
Tags Source
SHA-256 checksum
How to use checksums
90f33aa426f04b43ef5983070237b6803aa849d1a7744de5e060ede51a0bcc54
BLAKE2b-256 checksum
How to use checksums
e591758df17ff794c4da38df27f9e6d9ae2741ecd3b0a6eea24f4f9ddb903d0d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

Release files / sites_conformes-4.3.0-py3-none-any.whl

Download URL sites_conformes-4.3.0-py3-none-any.whl
Size 8.2 MB
Tags Python 3
SHA-256 checksum
How to use checksums
5a68c31d26b0e53a0eb897d4accf83ab5b9d07cf229f8acb2e8d6f8b016a14f1
BLAKE2b-256 checksum
How to use checksums
cbb14f43971915ec4cedc26a73f24d740bf11fab013af29bcf78e9f2cb348b34
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

Security for sites-conformes 4.3.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for sites_conformes-4.3.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Release history Release notifications | RSS feed

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page