Digital accompaniment

Digital accompaniment for artists, teachers, and cultural projects who want to organise archive, documentation, and publishing without depending on closed platforms.

I work with you to build a simple, maintainable system: a lightweight website, a browsable archive, and a way to document and share (wiki-style, if you need it) that won’t force you to start over every time the tool changes.

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.

My experience comes from a real case: I built and maintain Libellus (this website) with that same logic.

In 30 seconds
  • For: individual practices and cultural teams that need clarity and continuity.
  • What you get: structure + criteria + templates + minimal documentation; if useful, a wiki (Obsidian Publish) and/or an online shop.
  • With: open tools (Markdown, Git, Jekyll) and exportable systems; hybrids only if they help.
  • Real example: this website is built this way.

Request info

Who it’s for

This accompaniment is for you if you want to regain clarity in your digital ecosystem and sustain it over time without turning it into a burden.

  • 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

  • Content architecture and online presence (portfolio, archive, navigation, maintenance, continuity criteria).
  • Documentation system (Obsidian/Markdown, folders, naming conventions, links).
  • Wiki / knowledge base (Obsidian Publish, or an equivalent alternative) to share notes, materials, or public documentation.
  • Publishing and maintenance strategy (rhythms, templates, minimal automations).
  • Migrations and cleanup (when it makes sense: leaving closed platforms, organising backups, regaining control).
  • Digital sovereignty (dependencies, data ownership, export, preservation).
  • Continuity for teams (internal documentation, criteria, workflows, maintenance protocols).
  • Online shop (if applicable): structure, catalogue, content, and connection to an existing store or an appropriate solution.
  • Digital literacy (if applicable): everyday organisation, communication, security and privacy (passwords, 2FA, basic habits).

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

↑