Contribution guidelines

This site publishes architecture as an argument in progress. Contributions are how that argument gets tested. A good challenge is worth more than agreement.

What to contribute

Start your contribution by saying which kind it is:

Type	What it does
Challenge	Disagrees with the argument and says why
Evidence	Adds an observation that supports or weakens the argument
Question	Asks how the argument holds in a situation it does not cover
Alternative	Offers a different way to approach the same problem
Extension	Draws out a consequence the article does not mention

Be specific. Say what you observed, what you infer from it, and where you are unsure. The same standard applies to the articles themselves.

Keep it anonymous

Please do not identify clients, employers, colleagues, suppliers, internal projects or platforms, or combine details in a way that would let someone work them out. Describe the situation instead: "a large retailer", "a federated bank", "a platform team". This mirrors the site's own publication policy.

Contributions that identify an organisation or person will be removed or edited.

How contributions are used

Discussions happen in public on GitHub, through the discussion panel at the end of each Diary entry and argument page. Posting requires a GitHub account.

By contributing, you agree that PAGA BV may quote your contribution on this site, credited to you, for example as a counterpoint to the article, and may refer to it in future revisions. You keep the rights to what you wrote. If you would rather be credited by role only, or not quoted at all, say so in your contribution or email info@pagabv.com, and we will respect that.

Moderation

Discussion is moderated after posting. Contributions may be hidden or removed if they are off-topic, promotional, abusive, or identify people or organisations. Keep disagreement about ideas, not people.

See the privacy notice for how your data is handled.