import new site

.dockerignore

@@ -0,0 +1,2 @@
+_site/
+node_modules/

.github/workflows/Deploy Eleventy with GitHub Pages_dependencies_preinstalled.yml

@@ -0,0 +1,53 @@
+# Sample workflow for building and deploying an Eleventy site to GitHub Pages
+name: Deploy Eleventy with GitHub Pages dependencies preinstalled
+
+on:
+  # Runs on pushes targeting the default branch
+  push:
+    branches: ["gh-pages"]
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+# Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
+# However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  # Build job
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+      - name: Setup Pages
+        uses: actions/configure-pages@v3
+      - name: Build with Eleventy
+        run: |
+          npm install
+          npm run build-ghpages
+          npm run postbuild
+      - name: fr fallback homepage
+        run: "cp _site/fr/index.html _site/index.html"
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v1
+
+  # Deployment job
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v2

.vscode/settings.json

@@ -0,0 +1,6 @@
+{
+    "yaml.schemas": {
+        "kubernetes": "*.yaml",
+        "https://www.artillery.io/schema.json": []
+    }
+}

Dockerfile

@@ -0,0 +1,49 @@
+FROM node:18 as builder
+
+
+ARG http_proxy
+ARG https_proxy
+ARG npm_registry
+ARG no_proxy
+
+ENV NODE_ENV production
+
+# Create app directory
+
+WORKDIR /usr/src/app
+
+# use proxy & private npm registry
+# With internal npm repo (autosigned) disable strict ssl : strict-ssl false
+RUN ln -snf /usr/share/zoneinfo/$TZ /etc/localtime && echo "Europe/Paris" > /etc/timezone ; \
+    if [ ! -z "$http_proxy" ] ; then \
+    npm config delete proxy; \
+    npm config set proxy $http_proxy; \
+    npm config set https-proxy $https_proxy ; \
+    npm config set no-proxy $no_proxy; \
+    fi ; \
+    [ -z "$npm_registry" ] || npm config set registry=$npm_registry ; \
+    [ -z "$npm_registry" ] || npm config set strict-ssl false
+
+RUN npm cache clean -force
+
+# copy all dependances
+COPY package.json ./
+
+# install dependencies
+RUN npm install --save
+
+# copy all source files into app workdir
+COPY . /usr/src/app
+
+# build
+RUN npm run build 
+
+RUN npm run postbuild
+
+FROM nginxinc/nginx-unprivileged
+
+WORKDIR /usr/share/nginx/html/
+
+COPY --from=builder /usr/src/app/_site ./
+
+ENTRYPOINT ["nginx", "-g", "daemon off;"]

_data/data.js

@@ -1,3 +1,3 @@
 module.exports = {
-    footer_content_description: `Lorem [...] elit ut.`
+    footer_content_description: `Cadre de Cohérence Technique du ministère de l'intérieur.`
 }

_data/metadata.js

@@ -1,6 +1,6 @@
 module.exports = {
-    title: "Nom du site / service",
-    url: "https://url_du_site.gouv.fr/",
+    title: "Cadre de cohérence Technique / Ministère de l'intérieur",
+    url: "https://cct-mi.interieur.gouv.fr/",
     newsletter: [
         {
             url: "",
@@ -19,11 +19,11 @@ module.exports = {
     sourcehut_url: "",
     repository_url: "https://github.com/codegouvfr/eleventy-dsfr",
     language: "fr",
-    description: "baseline - précisions sur l‘organisation",
+    description: "Direction de la Transformation NUmérique",
     author: {
         name: "Nom du service",
         email: "contact@nom.du.service.gouv.fr",
         url: "https://url_du_service.gouv.fr/"
     },
-    service: "Nom de l’entité (ministère, secrétariat d‘état, gouvernement)"
+    service: "ministètre de l'intérieur"
 }

content/fr/about.md

@@ -1,6 +1,6 @@
 ---
 eleventyNavigation:
   key: À propos
-  order: 3
+  order: 5
 permalink: false
 ---

content/fr/blog/posts/architecture.md

@@ -0,0 +1,28 @@
+---
+title: Guide de bonnes pratiques d’architecture
+description: ensemble d’exigences non fonctionnelles et de bonnes pratiques d’architecture SI, s’appliquant à l’ensemble des applications et SI du MIOM et Inter Ministériel
+date: git Last Modified
+tags:
+  - cloud
+  - virtualisation
+  - architecture
+  - dev.
+  - ci/cd
+---
+
+{% from "components/component.njk" import component with context %}
+<div>
+{{ component("card", {
+    url: "/guide-architecture/sommaire",
+    title: "Guide de bonnes pratiques d’architecture",
+    description: "ensemble d’exigences non fonctionnelles et de bonnes pratiques d’architecture SI, s’appliquant à l’ensemble des applications et SI du MIOM et Inter Ministériel;",
+    tags: [],
+    date: "2023-06-21" | jsDateObject,
+    badges: [],
+    image: {
+        path: "../../../../public/img/undraw_urban_design_kpu8.png",
+        alt: ""
+    },
+    orientation: "horizontal"
+}) }}
+</div>