Search
Enter at least two characters without personal information.

    LibraryArticles & FAQ Your projectRequest a quote
    LanguageEN
    Web resources

    Development and code

    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 resources Troubleshooting methods Plan for updates and an exit

    AI-generated illustration

    Editorial method

    A directory made to be useful, not merely long.

    Each entry has a clear role and an official destination. The catalogue avoids link farms, copied descriptions and artificial rankings.

    01

    Official foundations

    Standards bodies, official documentation and public authorities are used as primary reference points.

    02

    Professional tools

    Established services are grouped by actual use: building, hosting, measuring, securing, publishing or promoting a website.

    03

    Independent reading

    Inclusion is editorial and unpaid. A listing does not imply a partnership or guarantee.

    Before choosing

    Compare on three practical questions

    Development and code
    CriterionQuestion to resolve
    CompatibilityDo versions, licences and environments fit the existing project?
    MaintenanceWho can fix a defect, update a dependency and rerun tests?
    DeliveryCan 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.

    Search and filter

    Official starting points for this topic

    Compare their role and documentation before selecting a tool. Inclusion is not a ranking.

    54 resources displayed

    Development and code

    API Découpage administratif

    Public API for finding French municipalities, administrative and postal codes and available geographic fields.

    API Découpage administratif — communes · Source consulted
    The date applies to the linked document, not to a review of every service feature.

    Use it for : Use the INSEE code as the identifier, date the extraction and distinguish a municipality from its postal codes.

    Apply it to a project
    FranceInstitution / standard
    geo.api.gouv.frVisit official website
    Development and code

    MDN Web Storage API

    Documentation for browser-accessible local and session storage.

    MDN — Web Storage API · Source consulted
    The date applies to the linked document, not to a review of every service feature.

    Use it for : Check retention, deletion and shared-device use before storing a draft.

    Apply it to a project
    InternationalCommunity / learning
    developer.mozilla.orgVisit official website
    Development and code

    MDN AbortController

    API for cancelling asynchronous operations, including Fetch requests and consumption of their responses.

    MDN AbortController · Source consulted
    The date applies to the linked document, not to a review of every service feature.

    Use it for : Stop an earlier search from replacing suggestions for the current input.

    Apply it to a project
    InternationalCommunity / learning
    developer.mozilla.orgVisit official website
    Development and code

    MDN Popover API

    HTML and JavaScript API for non-modal overlays that do not automatically disable the background.

    MDN Popover API · Source consulted
    The date applies to the linked document, not to a review of every service feature.

    Use it for : Choose an overlay suited to an action list rather than a modal confirmation.

    Apply it to a project
    InternationalCommunity / learning
    developer.mozilla.orgVisit official website
    Development and code

    MDN URLSearchParams

    Interface for reading and constructing URL parameter pairs, including encoding and repeated values.

    MDN URLSearchParams · Source consulted
    The date applies to the linked document, not to a review of every service feature.

    Use it for : Represent shareable filters without manually concatenating URL fragments.

    Apply it to a project
    InternationalCommunity / learning
    developer.mozilla.orgVisit official website
    Development and code

    MDN Content-Disposition

    Reference for inline presentation or downloading, including filename parameters.

    MDN Content-Disposition · Source consulted
    The date applies to the linked document, not to a review of every service feature.

    Use it for : Deliver exports with readable filenames in the published languages.

    Apply it to a project
    InternationalCommunity / learning
    developer.mozilla.orgVisit official website
    Choose a starting point

    What each category helps you decide.

    These examples illustrate uses, not rankings or endorsements. Verify each provider’s current documentation and terms before a decision.

    Development and code

    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 check
    • State the need each dependency solves.
    • Check documentation, compatibility and update procedure.

    A 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.

    Examples : PHP · Node.js

    Related guide : A practical website prelaunch checklist

    Explore troubleshooting situations

    Troubleshooting methods

    A successful demo can conceal recovery, build or handover problems. These cases help test a component together with its dependencies and failure states. The aim is a procedure another person can reproduce in a test environment.

    The build succeeds, but an action fails

    What you observe
    The code builds without errors, yet a form, download or search fails with certain data.
    Before drawing a conclusion
    A build checks part of the system. It does not prove every task works with the expected remote service, permissions and data.
    Verification step
    Reproduce a normal action, missing data and an error response. Record what the user sees and how they can continue. Add a targeted check for the actual defect rather than a test that merely repeats code structure.

    The project only works on its original computer

    What you observe
    A second environment cannot rebuild the expected result despite having the repository and available instructions.
    Before drawing a conclusion
    A local version, ignored file or undocumented dependency may be part of the actual setup. Copying an entire disk does not create a reliable delivery method.
    Verification step
    Start from a clean copy, record required versions and follow instructions without implicit knowledge. Document every missing step. Keep sensitive values out of examples and use clearly identified demonstration settings.

    Retrying creates a duplicate operation

    What you observe
    After an interruption, a person retries an action with an unknown outcome and finds two records or two processes.
    Before drawing a conclusion
    A missing message does not necessarily mean the server did nothing. The interface and process need a way to check state before repetition.
    Verification step
    In testing, interrupt the response after the operation begins. Inspect the recorded state and recovery procedure. Specify which actions can be repeated and how to find the outcome of an already accepted action.

    Keep useful data when changing tools

    Before making a resource part of website operations, plan for updates and an exit too. These checks concern your trial results without assuming features or prices of a particular plan.

    Reproduce installation

    On a copy, repeat installation from documented versions. Implicit workstation dependencies should become explicit.

    Isolate a dependency

    Identify where the library is used and the contract it fulfils. Test incorrect responses before planning replacement.

    Transfer operations

    Keep build, deployment and rollback instructions. Do not place secrets in documentation or configuration examples.

    Apply it to a project
    Transparency

    Editorial scope and third-party websites

    This non-exhaustive directory had its data consistency and links checked on 2 October 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.

    Suggest a resource or correction
    Related topics
    Directory questions

    Selection, independence and updates.

    The editorial selection prioritises primary and official sources, established standards bodies, widely used professional tools, specialised media and active communities that are directly relevant to creating, operating, securing or promoting websites. An entry should have a clear purpose, an identifiable publisher and an official destination. The catalogue is independent, non-exhaustive and does not attempt to rank every available provider. Inclusion may be reconsidered when a resource closes, changes purpose, becomes misleading or no longer offers enough practical value. Review dates indicate when the catalogue was last checked as a whole, not a guarantee that every external page remains unchanged afterwards. Visitors should therefore confirm current pricing, terms, security and suitability on the third-party website before relying on a service.

    No. A directory entry is a practical reference, not a certification, partnership, security audit or commercial endorsement. The listed organisations remain responsible for their products, content, prices, availability, cookies, personal-data practices and contractual terms. A resource may be useful for one project and unsuitable for another because requirements, jurisdiction, budget and technical capacity differ. Française du Numérique does not receive a commission for inclusion in this editorial directory. Before creating an account, purchasing a service or transferring data, visitors should review the official documentation, current terms, support arrangements, export options and relevant independent evidence. When the decision carries legal, financial or security consequences, an appropriately qualified assessment may also be necessary.

    Yes. The search field checks resource names and editorial topics, while filters narrow the catalogue by category, geographical origin and resource type. Filtering and sorting take place locally in the browser, so the text entered in the directory search is not sent to a separate search provider. Combining several filters may produce no result even when a useful resource exists in a neighbouring category; in that case, remove one filter or try a broader term. The catalogue descriptions are deliberately concise and cannot represent every feature offered by a third party. Open the official website to confirm capabilities, documentation and current conditions before making a decision.

    Use the contact page and provide the resource name, official URL, publisher, relevant category and a short explanation of its value for web professionals or project owners. For a correction, identify the entry and the information that appears inaccurate or outdated, ideally with a primary source. Suggestions are reviewed before publication and may be declined when the destination lacks a clear publisher, duplicates an existing entry, is primarily promotional, creates avoidable risk or falls outside the directory scope. Submission does not guarantee inclusion or a particular position, and paid placement is not offered through this editorial process.

    Include the version, context, demonstration data, steps, expected result and observed result. A reduced example must preserve the difficulty. Do not attach a full log containing credentials or personal data; share only what reproduction requires.

    Check imports, calls, build usage and indirect dependencies. Remove it in a copy, rebuild and verify affected tasks. Absence from main screens is not enough to conclude it is never used.

    Compare using observable evidence

    Before choosing a resource, run a limited trial using the same data and task. Keep the outcome and its limitations rather than a ranking based on familiarity.

    Reproduce a minimal case with identified versions and dependencies. Compare expected result, error and verified fix. A command working on one computer does not establish reproducible installation; document prerequisites and the result in the target environment.

    Use precise terms

    Two distinctions before comparing resources

    Input checks and permissions on resources should be examined separately.