Vai al contenuto
Home / Blog / Manifesto

Manifesto.

Why we keep this blog, how we write it and what we do when we get it wrong. Artificial intelligence is part of the method, and we do not hide it.

Five sections, five questions

MahoCommerce moves fast: every week brings merged pull requests, releases and decisions that change the way a store is built. The blog does not cover everything, it picks what matters and splits it into five sections, each one built around a precise question.

  • News

    The Maho news, one release at a time: what changed, what to update and what to read before deploying. Each release links the In depth posts on the features that deserve the space.

  • In depth

    The new Maho features in detail: what they do, where they live and what changes in the daily work. Releases link here for the deep dive.

  • Guides

    User guide and tutorials for MahoCommerce: how the admin features work and how to configure the store, step by step, with what it takes to reach the result. Written for the people who run the store, not only for those who write code.

  • #Dev

    Technical guides for people who develop on Maho: local environment, themes, modules, commands and tooling. They start from a working result, then go into the code.

  • #Insider

    The workshop of Maho: open pull requests, merged ones that are not released yet, weekly roundups and work on the repository. For whoever wants to see what comes next before it ships.

What changed? That is the question behind News: the note for every version, with what moves and what to check before upgrading. When a feature deserves more room than the paragraph it gets, it becomes an In depth post, tied to the release it comes from: the release leads to the deep dive, and the deep dive back to the release.

How do I use it? The Guides answer that, step by step in the admin. How is it built? That is the ground of #Dev, across environments, themes and modules. What is cooking? #Insider tells it, the only place where pull requests not released yet and work on the repository are discussed.

Outside #Insider an article describes what has already shipped, dated the day it shipped. Whoever reads finds a photograph of the product, not a promise about what it will be.

Facts, opinions, sources

When there is a fact we tell it and link the source, whether it is the pull request, the release or the code; when there is an opinion we write it as such. If something is not verified, we say so instead of making it look certain. When an article touches work of ours, for example an open source module or the hosting, we name it with its technical name: the reader must know who made what.

How an article is made

Every text starts from the source. Artificial intelligence helps us read, summarise and write faster what the sources say; a person checks the facts, the numbers, the commands and the conclusions before publication. A text that is only generated is not published.

Mistakes are still possible: a detail that changes after the writing, a wrong version, a command renamed in the meantime. If you find one, tell us below: we fix the article and the date, not just the sentence.

AI in the MahoCommerce project too

The use of AI is no secret in the project either: without artificial intelligence a project like MahoCommerce would not have been possible, and we say it plainly. MahoCommerce documents its transparency on AI use in the repository README, and pull requests developed with its help say so in the description. Every change is still reviewed and validated by a person before it is merged. The same rule applies to this blog: AI speeds up the work, the responsibility stays human.

Report a mistake

A mistake found is worth more than a hundred compliments. Write two lines below, naming the article and what does not add up: we answer as soon as we can.

We answer only if a clarification is needed.

Thank you, we received the report.