Official foundations
Standards bodies, official documentation and public authorities are used as primary reference points.
Web resources
Organization, collaboration and automation
Workflow tools should first make decisions, owners, dates and versions visible. Simplify a process before automating it, and plan what happens when an automation fails.
Take a real content approval: author, reviewer, decision, published version and correction. Test who receives a notice and how to find the decision three months later.
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.
Professional tools
Established services are grouped by actual use: building, hosting, measuring, securing, publishing or promoting a website.
Independent reading
Inclusion is editorial and unpaid. A listing does not imply a partnership or guarantee.
Compare on three practical questions
| Criterion | Question to resolve |
|---|---|
| Owners | Do tasks, decisions and approvals have identifiable owners? |
| Failure cases | How are duplicates, synchronisation errors and stopped workflows detected? |
| Documentation | Can another person find decisions and resume the process? |
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.
17 resources displayed
The link restores the search and filters, including resources selected for comparison.
No resource matches these filters. Try a broader search.
Compare up to three resources
Select resources from the cards below. Compare their role and practical use, then verify current terms, costs, data export and support on official websites. Geographical origin describes the publisher; it does not establish where your data will be hosted.
No resource selected.
Documentation, knowledge bases and collaborative organization.
Use it for : Define the reference source, sharing permissions and exports before centralising procedures; test handover.
Apply it to a project
notion.comVisit official website
Visual databases and process automation.
Use it for : Define data, relationships and export before building a shared base.
Apply it to a project
airtable.comVisit official website
Task and project organization using boards.
Use it for : Make steps and decisions visible without making every task a separate board.
Apply it to a project
trello.comVisit official website
Planning and coordination of team work.
Use it for : Connect tasks and owners to a realistic delivery schedule.
Apply it to a project
asana.comVisit official website
Tracking for projects, requests and software development.
Use it for : Choose a simple workflow the team can actually maintain.
Apply it to a project
atlassian.comVisit official website
Team messaging and work integrations.
Use it for : Turn important decisions into retrievable documentation.
Apply it to a project
slack.comVisit official website
Microsoft communication, meetings and collaboration.
Use it for : Define where project documents, decisions and conversations live.
Apply it to a project
microsoft.comVisit official website
Google email, documents and collaborative tools.
Use it for : Organise shared documents and review cycles before files proliferate.
Apply it to a project
workspace.google.comVisit official website
Task automation between online services.
Use it for : Test errors and duplicates in a pilot flow before wider automation.
Apply it to a project
zapier.comVisit official website
Visual automation of scenarios across applications and data.
Use it for : Document inputs, outputs and manual recovery for each scenario.
Apply it to a project
make.comVisit official website
Extensible, self-hostable workflow automation.
Use it for : Plan monitoring and maintenance of workflows as well as creation.
Apply it to a project
n8n.ioVisit official website
Collaborative whiteboard for workshops, journeys and architecture.
Use it for : End a workshop with decisions, owners and accessible documents.
Apply it to a project
miro.comVisit official website
Project management, documents, tasks and dashboards.
Use it for : Limit views and statuses to those that genuinely help tracking.
Apply it to a project
clickup.comVisit official website
Simple organization of projects, discussions and team documents.
Use it for : Separate messages, deliverables and decisions to ease project handover.
Apply it to a project
basecamp.comVisit official website
Automation of tests, checks and deployments from GitHub repository events.
Use it for : Define test and release steps while limiting automation permissions.
Apply it to a project
github.comVisit official website
Official guidance for designing and operating GitHub webhook integrations.
Use it for : Define repetition, delays, recovery and source reconciliation.
Apply it to a project
docs.github.comVisit official website
Guide to dataset publication methods and accompanying information.
Use it for : Assign an owner and provide usable documentation before publication.
Apply it to a project
guides.data.gouv.frVisit 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.
Organization, collaboration and automation
Workflow tools should first make decisions, owners, dates and versions visible. Simplify a process before automating it, and plan what happens when an automation fails.
Questions to check- Define the source of truth for documents and approvals.
- Test access roles, exports and useful notifications.
A practical use : Take a real content approval: author, reviewer, decision, published version and correction. Test who receives a notice and how to find the decision three months later.
What this cannot prove : Automating an unclear step can spread an error faster. Check access roles and data export before moving the team.
Related guide : Take over or hand over a website with confidence
Troubleshooting methods
A workflow tool becomes useful when work status, version and ownership remain understandable. These cases examine recovery after failure, approval and document recovery. They can be tested with a small process copy and demonstration data.
Restarting an automation creates two tasks
- What you observe
- After a delay or response error, the same event is retried and triggers several tasks, notifications or records.
- Before drawing a conclusion
- Recovery may process an already accepted operation again. Visible status needs to distinguish a new event from a repetition.
- Verification step
- In a demonstration flow, cause an interruption then replay the same event. Inspect identifiers and outcomes. Define expected handling of repeats before enabling the flow for real messages or actions.
An approved document changes without a fresh review
- What you observe
- The version used for publication no longer matches the version its owner reviewed and approved.
- Before drawing a conclusion
- An “approved” status attached only to a document can become ambiguous when its content changes. The decision must connect to the relevant version.
- Verification step
- Check the approval date, content and owner. Define how a change reopens review and how the published version can be found. Do not infer current permission from an old comment.
An export retains titles but loses attachments
- What you observe
- The exported table retains tasks and status, while documents, useful discussions or relationships cannot be recovered from the file.
- Before drawing a conclusion
- Exporting a list does not establish recovery of the entire process. External files and links need separate checks.
- Verification step
- Choose a complete task with attachments and decisions. Rebuild it from the export in a copy, then list missing elements and required recovery formats before approving the exit process.
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.
Export relationships
Check tasks, owners, useful comments and links between objects. A title list can lose dependencies required for follow-up.
Identify automation
Inventory triggers, conditions, messages and connected systems. A forgotten rule can keep sending notifications after migration.
Test continuation
Repeat a small process with failures and final decision. Check who owns the data and where the team finds the current state.
Transparency
Suggest a resource or correction
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.
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.
Choose a repetitive task whose input, outcome and owner are already clear. Check missing-data cases, failures and recovery before expanding it. Automation does not resolve undefined approval or responsibility.
Specify the reference location, owner and approval rules. Connect shared copies to that source and identify their date or version. Test what another person finds through usual links, particularly after a change or handover.