Digital accompaniment

Digital accompaniment for artists, teachers, and cultural projects who want to organise archive, documentation, and publishing without depending on closed platforms. It turns a scattered digital archive (folders, Google Docs, platforms, disconnected website) into an autonomous, legible, and sustainable system over time.

It’s not just “building a website”: it’s about organising your archive, connecting documentation and publishing, and leaving you with a method you can maintain without depending on me.

I work from a file over app1 approach: prioritising readable, portable files (Markdown) and a workflow you can keep on your own computer (folders, backups, Git), without a proprietary CMS2. When it makes sense, I integrate external services (e.g. Are.na), but without losing ownership and exportability.

This website is built with the same logic, on a simple architecture that prioritises autonomy and long-term preservation. Instead of depending on commercial services such as WordPress or Wix, the pages are generated automatically from text files stored on my own computer and published from an environment I manage directly.

What this means in practice
  • Defining a clear, sustainable archive structure.
  • Connecting that archive to your website to avoid duplication.
  • Reducing dependence on proprietary formats and services.
  • Leaving a documented method you can maintain without me.
In 30 seconds
  • For: artists, researchers, and cultural teams who need to organise and structure their digital archive offline and online, turning a burden into a growth tool.
  • What you get:
    • 🗂️ Archive system: folder structure, naming conventions, templates, and continuity criteria.
    • 🌐 Autonomous, integrated website: a new website or a restructuring of an existing one, connected to your archive and sustainable over time, without depending on a proprietary CMS.
  • With: open tools (Markdown, Git, Jekyll), exportable systems, and services (Readwise, Obsidian Publish, Are.na, online shop).
  • Real example: this website is built this way.

Request info

Who it’s for

This accompaniment is for people who want to strengthen their digital ecosystem and transform a scattered set of proprietary files3 (Google Docs, Word documents, etc.) into a system based on open, universal, and sustainable formats, coherently synchronised with their website or online portfolio.

  • Individual practices: artists, photographers, researchers, and teachers who need to organise archive, documentation, and online presence.
  • Cultural projects: collectives, centres, festivals, small publishers, and teams who need an infrastructure for publishing, consultation, and continuity.
  • Training / bridging the tech gap: people, groups, or educational/community contexts who want to learn tools and criteria without being captured by platforms.

How we work

  1. Context: you tell me what you have today (website, archive, tools) and what you want to achieve.
  2. Diagnosis and map: we set priorities, dependencies, and a realistic path.
  3. Implementation with you: we build structure, workflows, and templates; if needed, we migrate.
  4. Handover and continuity: minimal documentation so the system doesn’t depend on me.

Topics covered

🗂️ Archive and documentation

  • Folder system, naming conventions, and organisation criteria.
  • Markdown templates and an interoperable structure.
  • Knowledge base (Obsidian / equivalent alternative).
  • Cleanup, migration, and file recovery.
  • Backup and synchronisation across devices.

🌐 Publishing and autonomous web

  • Content architecture (portfolio, archive, navigation).
  • Static website without a proprietary CMS.
  • Connection between archive and publishing.
  • Online shop (if applicable).

🔁 Continuity and digital sovereignty

  • Dependencies and data ownership.
  • Exportability and long-term preservation.
  • Minimal documentation for teams.
  • Rhythms, maintenance, and basic automations.
  • Critical digital literacy (if applicable).

If you’re interested in the training side, I work from a critical digital literacy perspective: learning tools and workflows linked to sustainability, archiving, method, autonomy, and care for time and attention.

Contact

If you’d like more information, you can leave your details via this form. I usually reply within 2-3 business days.

If you can, mention: where you are right now (website, archive, tools), what you want to achieve, and whether you have a specific date or need.

  1. Steph Ango, “File over app,” accessed February 12, 2026, https://stephango.com/file-over-app. ⤶

  2. CMS: Content Management System. ⤶

  3. By “proprietary files” I mean files created with programs or formats controlled by specific companies, whose use, compatibility, or continuity depend on their terms and policies. ⤶

↑