Official foundations
Standards bodies, official documentation and public authorities are used as primary reference points.
Languages, frameworks and code tools solve different constraints. A team benefits from choosing what it can test, update and hand over instead of accumulating technology.
Pick one function and prototype its normal path, failure state and update process. Check that a second person can explain the code, dependencies and deployment.
Browse the resourcesEach entry has a clear role and an official destination. The catalogue avoids link farms, copied descriptions and artificial rankings.
Standards bodies, official documentation and public authorities are used as primary reference points.
Established services are grouped by actual use: building, hosting, measuring, securing, publishing or promoting a website.
Inclusion is editorial and unpaid. A listing does not imply a partnership or guarantee.
| Criterion | Question to resolve |
|---|---|
| Compatibility | Do versions, licences and environments fit the existing project? |
| Maintenance | Who can fix a defect, update a dependency and rerun tests? |
| Delivery | Can the code be built and deployed reproducibly? |
Keep a short decision record: requirement, source, observed result and unresolved point. Test the same task with each candidate instead of comparing marketing lists of features.
Compare their role and documentation before selecting a tool. Inclusion is not a ranking.
46 resources displayed
No resource matches these filters. Try a broader search.
Official documentation for the PHP language and its ecosystem.
Use it for : Use the language documentation and supported versions for the project.
Reference dependency manager for PHP projects.
Use it for : Inspect resolved versions and updates in the actual PHP project.
Public directory of packages installable with Composer.
Use it for : Review package maintenance and dependencies before installation.
PHP framework and reusable components created in France.
Use it for : Check needed components and the version’s maintenance period.
Modern PHP framework for Web applications and services.
Use it for : Assess conventions, tests and the team’s ability to maintain the application.
Server-side JavaScript runtime and development tooling platform.
Use it for : Check supported releases and dependencies before adopting a tool.
Package registry and manager for the JavaScript ecosystem.
Use it for : Check provenance, versions and dependencies of added packages.
Typed language built on JavaScript for more robust applications.
Use it for : Define type boundaries and check generated JavaScript at interfaces.
JavaScript library for building user interfaces.
Use it for : Test component structure and final rendering on a real journey.
Progressive JavaScript framework for interfaces and Web applications.
Use it for : Compare interaction needs with loading and maintenance costs.
Google framework for building structured Web applications.
Use it for : Check project structure and skills needed for handover.
Compiled framework for building reactive Web interfaces.
Use it for : Measure compiled output and document reusable components.
React framework for server-rendered applications and modern websites.
Use it for : Test rendering, caching and deployment for each planned page type.
Vue framework for server-rendered websites and applications.
Use it for : Check routes, rendering and shared data on a representative page.
Component and style library for responsive interfaces.
Use it for : Remove unused components and test accessibility of chosen variants.
Utility-first CSS framework for composing custom interfaces.
Use it for : Define component conventions to avoid duplicated styles.
Official Python language site, used for Web, data and AI.
Use it for : Choose a maintained version and isolate project dependencies.
Full-featured, secure and maintainable Python Web framework.
Use it for : Test administration, data migrations and deployment security.
Ruby framework for rapidly developing Web applications.
Use it for : Check conventions, updates and coverage of critical journeys.
Distributed source-code version control system.
Use it for : Document the branches and rollback procedure the team actually uses.
Git logo by Jason Long, licensed under CC BY 3.0.Code hosting, collaboration, automation and project management.
Use it for : Review repository checks, permissions and automation.
DevSecOps platform for repositories, continuous integration and deployment.
Use it for : Document the delivery pipeline and change owners.
Git repository hosting integrated with the Atlassian ecosystem.
Use it for : Check review rules and repository integrations.
Containers and tools for reproducible environments.
Use it for : Verify that images are reproducible, maintained and documented.
Technical questions and answers for developers and digital teams.
Use it for : Check date, version and official documentation before adopting an answer.
Front-end demonstration and experimentation environment.
Use it for : Use a prototype to isolate behaviour, then test its real integration.
Long-standing JavaScript library still used by many websites.
Use it for : Assess the existing dependency before adding or removing the library.
Technical reference for HTTP methods, status codes, headers, caching and browser policies.
Use it for : Check response codes, headers and methods before fixing a browser-server exchange.
Official schedule for actively supported PHP versions and security-fix coverage.
Use it for : Check the support lifecycle of the installed version before planning an upgrade.
Reference guide for building installable, resilient Web applications across devices.
Use it for : Evaluate offline and installable features only when they support a real journey.
Documentation for the API used to intercept requests, manage caches and provide offline features.
Use it for : Check update lifecycle and caching risks before adding a service worker.
Open data describing browser and version support for Web technologies.
Use it for : Check feature support before deciding on a fallback or polyfill.
Documentation for HTML form constraints and their API, including the need for server-side validation.
Use it for : Test HTML constraints, then confirm the server also rejects invalid data.
Public API for finding French municipalities, administrative and postal codes and available geographic fields.
Use it for : Use the INSEE code as the identifier, date the extraction and distinguish a municipality from its postal codes.
Reference for the version identifier used in conditional HTTP resource validation.
Use it for : Test an unchanged and then changed resource rather than inferring behaviour from a status alone.
Reference for HTTP response codes grouped by result family.
Use it for : Document empty, refused and failed responses in the service contract.
Documentation for the browser API used to make requests and handle responses.
Use it for : Test network loss and error responses as well as successful requests.
Documentation for structured browser storage and its asynchronous operations.
Use it for : Define what may remain on the device and how local data evolves.
Documentation for browser-accessible local and session storage.
Use it for : Check retention, deletion and shared-device use before storing a draft.
Reference for JavaScript internationalisation, including number and date formatting.
Use it for : Test amounts, dates and languages against audience conventions.
Documentation for the HTML control used to select files.
Use it for : Announce limits and enforce the same rules on the server.
Documentation for building and transmitting form fields and files.
Use it for : Test interruption, missing fields and receipt before announcing success.
Guide to service worker installation, activation and updates.
Use it for : Test a new version with an earlier cache and an already-open session.
Documentation for version constraints used in Composer dependency resolution.
Use it for : Keep resolved versions and test the effect of changed constraints.
PHP reference for encoding, decoding and checking JSON errors.
Use it for : Test missing data, characters and errors rather than assuming decoding succeeded.
Documentation for reading and writing CSV files with explicit dialects.
Use it for : Keep delimiters, encoding, identifiers and missing values in the exchange contract.
These examples illustrate uses, not rankings or endorsements. Verify each provider’s current documentation and terms before a decision.
Languages, frameworks and code tools solve different constraints. A team benefits from choosing what it can test, update and hand over instead of accumulating technology.
Questions to checkA practical use : Pick one function and prototype its normal path, failure state and update process. Check that a second person can explain the code, dependencies and deployment.
What this cannot prove : Stars or popularity cannot replace fit with the team and the actual requirement.
Related guide : A practical website prelaunch checklist
This non-exhaustive directory was last reviewed on 30 August 2026; its links were checked on 25 September 2026. Some websites restrict automated checks. It contains external links to independent websites. Their availability, content, prices, cookies and terms may change. Française du Numérique does not control them and receives no commission for their inclusion.