
Independent talent
Make expertise clearer, explain experience fairly and reach new opportunities in France and abroad.

FRENCH DIGITAL SOCIETY builds useful connections between French digital professionals and organisations that value quality. The community is intended to be more than a showcase: it should help people understand digital work, learn from one another and create stronger professional relationships.
A strong profile is more than a list of tools. It explains a role, a method, areas of excellence and a way of working. When expectations, responsibilities and limits are clear from the beginning, teams can focus their energy on solving the right problem.
Clarity matters between peers as well. Knowing how to describe your contribution, acknowledge the edges of your expertise and recommend a complementary specialist are all signs of professional maturity.

Precise, verifiable and useful information that supports sound decisions without exaggerated promises.

Cross-border projects, distributed teams and exchanges between professional cultures while respecting local context.

Practical methods, honest experience and simple guidance that improve digital practice over time.
The network welcomes people who value serious work, transparent methods and lasting relationships around useful digital projects.

Make expertise clearer, explain experience fairly and reach new opportunities in France and abroad.

Present complementary skills, team organisation and the capacity to deliver broader pieces of work.

Understand digital roles, shape better requests and identify specialists suited to their context and constraints.
A clear proposal makes it possible to assess relevance without guessing. These are suggestions for contacting the editorial team, not a promise of listing, membership or publication.

Explain the problem you solve, the people you work with, your exact contribution, public examples and the limits of your offer. A specific case is more useful than a long list of tools.

Send the original URL, publisher, intended audience, practical use and any important access conditions. A correction to an existing guide should identify the page and the claim to revisit.

Describe the audience it would help, each organisation’s role, the expected output and the way the result could be checked. State any commercial relationship clearly.

Name the audience, problem and action your proposal would make easier. Avoid a claim of universal quality or an unverifiable impact figure.

Provide a working link, a public example or a source document. If confidentiality prevents sharing a case, explain what can be discussed without exposing client information.

Identify a contact who can answer questions, clarify ownership and review a draft. An entry in the directory remains distinct from membership or endorsement.
Get in touch to join the network, suggest a resource, share experience or propose a partnership with practical value for the community.
Get in touch →Choose a path from your goal to useful evidence →
For a user study, share the task, recruitment limits and observed obstacles without identifying participants. For a data project, preserve the dataset version, licence and transformations. These records help another professional understand what can be reused and what needs retesting.

Choose a task, prepare a neutral scenario, observe obstacles and turn findings into verifiable improvements.
Use the method →
Choose documents, versions, access rights and answer evidence before connecting an assistant to documents.
Use the method →
Decide who verifies content, against which evidence and when to revisit it, without artificial freshness dates.
Use the method →Hypothetical comparison
Fictional case: two providers show convincing work. For a joint project, their approach to scoping work matters alongside the portfolio.

Screenshots explain the context, the provider’s exact role and the verifiable result.
How to read it : They help assess comparable experience, but the coordination method still needs to be discussed.

The proposal allocates roles, approval stages, access to deliverables and maintenance.
How to read it : It makes collaboration understandable, but references still need separate verification.
To choose a team member, combine delivery evidence with a work plan suited to your needs.
| Role | Expected decision | Handover point |
|---|---|---|
| Need owner | Prioritise journeys. | Approve scope before the quote. |
| Content producer | Supply copy and image permissions. | Plan materials before integration. |
| Maintenance owner | Manage updates and access. | Prepare handover before delivery. |