La documentation des styles est disponible dans le fichier ./style.md
.
The env
variables you can use for deployment are listed in the .env.example
file.
# To hide the "debug" switch
# If this variable is set to 'true'
# it overrides the `debug-switch` parameters to prohibit debug mode
VITE_NO_DEBUG_SWITCH = false
# To indicate built source while copying the widget
VITE_DEPLOY_URL = https://tee-frontend.osc-fr1.scalingo.io
# To set up global contact email
VITE_CONTACT_EMAIL = contact@mission-transition-ecologique.beta.gouv.fr
# To set up PostHog analytics
# create a posthog account and use the corresponding API key
VITE_POSTHOG_API_KEY = your_key
# To set up Matomo analytics
# Note : if VITE_MATOMO_DEACTIVATE is set to 'true' it prohibits the tracking
# even if VITE_MATOMO_URL and VITE_MATOMO_APP_ID are correctly set
VITE_MATOMO_DEACTIVATE = true
VITE_MATOMO_URL = https://stats.beta.gouv.fr
VITE_MATOMO_APP_ID = 42
# To indicate the backend url
VITE_TEE_BACKEND_URL=https://tee-backend.osc-fr1.scalingo.io
- Aides territoires + Mission transition
- https://www.figma.com/file/tHgzORFkJYTVspsQgR2kg6/TEE-V5
- https://docs.google.com/presentation/d/1zP32OOaRsVEgPTaIXjWUxq3DccR79m4Zv8blfJa-0vQ/edit#slide=id.g22df2b368bb_0_655
- https://whimsical.com/offres-aux-entreprises-dans-la-tee-2gHnT3nFgRZs32pa7aYmPL
- API - Liste des aides Entreprises sur AGIR :
- API - Aides-territoires : https://aides-territoires.beta.gouv.fr/api/swagger/
- API - Aides 1 jeune 1 solution :
- https://mes-aides.1jeune1solution.beta.gouv.fr/api/benefits
- https://github.com/betagouv/aides-jeunes/blob/master/contribuer/public/admin/config.yml
- https://github.com/betagouv/aides-jeunes/tree/master/data/benefits/javascript
- https://contribuer-aides-jeunes.netlify.app/admin/#/
- (contribution w/ Netlify CMS) https://github.com/betagouv/aides-jeunes/tree/master/data/benefits/javascript
- Questionnaires
- Schemas / aid data models
- https://schema.data.gouv.fr/etalab/schema-dispositif-aide/0.0.2/documentation.html#propriete-condition-eligibilite
- https://github.com/MTES-MCT/aides-territoires/wiki/Format-des-donn%C3%A9es-publi%C3%A9es-sur-Aides-territoires
- https://www.insee.fr/fr/information/2406147
- https://publi.codes/
- cf "open fisca"
- cf "mon entreprise"
- Others
- https://www.entreprises.gouv.fr/files/files/secteurs-d-activite/industrie/decarbonation/transition-ecologique-guidedes-aides-pour-les-tpe-pme.pdf
- https://www.gouvernement.fr/france-nation-verte
- https://conseillers-entreprises.service-public.fr/aide-entreprise/accueil/theme/environnement-transition-ecologique
- https://agirpourlatransition.ademe.fr/entreprises/aides-financieres/2022/tremplin-transition-ecologique-pme
All documentation about data models and references are on our SE Notion space
- Type script
- Vuejs 3
- Vite
- Design System de l'Etat
- create vue app + vite : https://github.com/vuejs/create-vue
- vue3 + typescript :
- vue + vite + nuxt + dsfr : https://github.com/laruiss/create-vue-dsfr
- vue3 composition API :
- issues templates : https://github.com/stevemao/github-issue-templates/tree/master
VSCode + Volar (and disable Vetur) + TypeScript Vue Plugin (Volar).
TypeScript cannot handle type information for .vue
imports by default, so we replace the tsc
CLI with vue-tsc
for type checking. In editors, we need TypeScript Vue Plugin (Volar) to make the TypeScript language service aware of .vue
types.
If the standalone TypeScript plugin doesn't feel fast enough to you, Volar has also implemented a Take Over Mode that is more performant. You can enable it by the following steps:
- Disable the built-in TypeScript Extension
- Run
Extensions: Show Built-in Extensions
from VSCode's command palette - Find
TypeScript and JavaScript Language Features
, right click and selectDisable (Workspace)
- Reload the VSCode window by running
Developer: Reload Window
from the command palette.
See Vite Configuration Reference.
npm install
cp .env.example .env
npm run dev
Should run on http://localhost:4242
Lint with ESLint
npm run lint
Run Unit Tests with Vitest
npm run test:unit
Run End-to-End Tests with Cypress
npm run test:e2e:dev
This runs the end-to-end tests against the Vite development server. It is much faster than the production build.
npm run build
Run End-to-End Tests with Cypress on Production Build
It's still recommended to test the production build with test:e2e
before deploying (e.g. in CI environments):
npm run build
npm run test:e2e