An identity, message or medium should help a defined audience understand an offer. Compare editorial methods and usage rights as carefully as visual quality.
Choose by need, then compare evidence
Clarify a value proposition and present it consistently across formats.
Produce photography, video or written content with documented rights.
Organise regular communication without unnecessary channels.
What to compare for each kind of work
Need
Questions to examine
Identity
Uses, variants, source files and brand rules.
Production
Brief, preparation, approvals, captions and rights.
Distribution
Audience, formats, schedule, responsibilities and measurement.
Deliverables to request
Editorial brief defining audience, message and intended action.
Usable files, licences and permissions for people represented.
Approval schedule and rules for maintaining consistency.
An attractive image does not prove delivery or team membership. Label illustrations and check permissions before identifying people as clients or members.
Who owns the files and usage rights?
Commissioning alone does not define all permitted uses. Document delivered formats, media, duration, territory and rights to modify or reuse within the agreed framework.
FRENCH DIGITAL SOCIETY only publishes identifiable organisations and official resources. Inclusion is not a certification or ranking; check references, availability, legal information and contractual terms before appointing a provider.
1 resources shown
Keep a resource shortlist
Select resources in the list to compare their role and scope. Compare your shortlist on screen with your team. Selection stays on this page, with no account or browser storage; filtering does not clear it.
Inclusion does not establish quality or availability. Check identity, scope, source and relevant evidence before using a resource.
Professional guide · France
Afnic · Choisir un nom de domaine
Guidance from the .fr registry on choosing a legible domain name and checking availability.
Use it for: Compare legibility, availability and brand consistency before registration and promotion.
A directory entry is a starting point. Match the resource to a defined need, check the original source and compare approaches before committing a budget.
1. Describe the outcome
Write down the audience, the problem, the expected result and the deadline. A website redesign, a security review and a data project call for different evidence and skills.
2. Check the source
Open the organisation’s own site. Check its legal identity, the scope of its services, the date of its guidance and how to contact it. For public data, review the publisher, licence and update frequency.
3. Compare like with like
Ask providers about relevant work, delivery method, responsibilities, accessibility, handover and support. Compare proposals against the same brief and note what is excluded.
A public resource may help you learn or benchmark; a provider may carry out a mission. Inclusion here does not imply endorsement, affiliation or current availability. Read the expert selection guide for a fuller checklist.
Browse with context
What each directory category can help you do.
The filters group different types of resources. These notes explain the intended use and the checks to make before acting.
Choose this category when the need concerns a website, application, integration or long-term technical maintenance. Distinguish a delivery provider from a public guide explaining how to prepare the project.
Before you decide: Ask about ownership of the domain and code, accessibility checks, security updates, documentation and the support plan.
Use this category for brand messages, visual identity, editorial production and channels. A communication plan should name its audience and the action it is meant to support.
Before you decide: Compare examples of published work, approval steps, usage rights and how consistency will be maintained across formats.
Explore this category for infrastructure, connectivity, cybersecurity and operational support. Start with an inventory of essential services and who can access them.
Before you decide: Confirm response arrangements, backups, recovery responsibilities, subcontractors and the boundary between support and security advice.
Find public datasets, APIs and guidance for analysis or a controlled AI experiment. A catalogue entry describes a source; it does not automatically make the data suitable for a decision.
Before you decide: Check licence, update frequency, coverage, missing values, access conditions and whether a human can review consequential outputs.
Look here for search visibility, campaigns, email and measurement guidance. Begin with a target audience and a meaningful outcome before selecting a channel.
Before you decide: Ask which baseline will be used, how consent and tracking work, and who will maintain content after a campaign.
Use networks to discover organisations, training or support. An entry in a network is a lead for further checking, not proof of availability or quality.
Before you decide: Verify membership criteria where relevant, the person who will carry out the work and the terms of any proposed introduction.
The date records an automated availability check, not a guarantee of data freshness, service quality or eligibility. Some publishers block automated requests. For each dataset or API, check the actual licence, update date, coverage and access terms before reuse.
Select a suitable digital resource
Define the expected outcome and constraints before choosing a service or provider.
Scroll horizontally to read all columns.
Decision guide
Criterion
What to check
Practical implication
Need
Specify users, task, data processed and expected result.
A well-known tool can still be unsuitable for your team or data.
Evidence
Request a representative demonstration with the access rights future users will have.
An administrator demonstration does not establish usability for everyone.
Acceptance criteria
Describe a complete task, its inputs, expected outcome and the person who will validate it.
A delivered screen does not prove the journey works; agree on error handling and support requests as well.
Data scope
List essential fields and connect each to a service purpose.
Broader collection complicates management without necessarily improving outcomes.
Data minimisation
For a defined purpose, collection of personal data should be limited to what is adequate, relevant and necessary. A convenient feature alone does not justify collecting fields with no established use. Source: CNIL — Minimisation
Worked example
Fictional case: a charity needs a booking tool. It tests a scenario with one user, a cancellation and an export, then checks who can see the data and retrieve the calendar. This exposes terms to settle before wider use.
Where should I start when several digital tools look suitable?
Describe a real task, required data, who will access them and the expected result. A limited trial against that scenario reveals more than a context-free feature list.