Wieser

Manual: The Linz WordPress Meetup Model

Together instead of lonely: Over 10 years of lived WordPress Meetup – open source culture

Our Identity: More Than Just a Meetup

We are not a classic event format. We are an open source lab. Since 2011 open WordPress (officially since 2015 WordPress Meetup) we prove in Linz that the strongest power of WordPress is not in the code, but in the interaction. We meet monthly – without slides, without passive consumers, but with maximum effect.

The three pillars of our success:

1. Radical Participation (The “No-Presentation” Principle)

There is no stage with us. Every participant – from the absolute newcomer to the core contributor – is a co-creator.

  • Live experiments: We use tools like the WordPress Playground to test ideas in the browser right away.
  • Innovation from the round: For example, a Blueprint Creator plugin was created, which was developed directly during our meetings through joint testing and feedback.

2. Documentation & Knowledge Transfer (Help for Self-Help)

Knowledge is not a one-way street.

  • With projects like clipperton.at, we are creating a German-language bridge to the official WordPress documentation.
  • Not only do we translate, we add our own experiences to making WordPress more accessible to the local space.

3. Toolbox: From talking to prototyping

In the Linz round, “software” is not a finished product that we only use, but material that we work with like in a workshop.

3.1 WordPress Playground as a Sandbox

The use of WordPress Playground has revolutionized our dynamics. Since it runs completely in the browser, the hurdle of the local installation is eliminated.

  • Live blueprints: We create ad hoc configurations to test plugins or themes immediately.
  • The “Blueprint Creator”: In our rounds, a plugin was created that makes it possible to visually compile your own blueprints. This allows participants to save and share their experiments with one click.
  • Iterative testing: If someone has an idea for a new Gutenberg block, we build and test it right in the round.

3.2 AI Integration & API Experiments

We do not consider AI a threat, but as a tool for expanding WordPress.

  • AI regulars‘ table & WP meetup: These two projects are merged with us. We develop plugins (e.g. for AI agents or internal AI interfaces that use WordPress data intelligently.
  • API-Lab: We experiment with the WP-REST API to connect WordPress to other open source tools (e.g. for the Homeassistant laboratory).
  • Using code editors and AI inspirations for coder and also AI GEO, WordPress MCP develop into very current topics Blocks

3.3 Real projects as a development driver

Instead of learning on abstract examples, we are working on “living objects.” This ensures relevance and sustainability:

 

Project Focus in the Meetup Benefits for the community
www.offinne.at Portal for Repaircafés Networking of sustainability initiatives throughout Austria.
www.otelolinz.at Club homepage For 10 years the “test site” for new functions and designs.
Taterman & Gigas Gaukler Niche magazines Complex layouts and content structures.
Leonardo Workshop Education Platform Mediation of technology and craftsmanship via web.
Meetup Participants Project Help for self-help Visitors and actors help each other and gain experience for their own projects

3.4 The Synergy: The Otelo Ecosystem

The WordPress Meetup Linz is not an isolated event, but a hub in the Otelo network (Open Technology Labs).

  • Merger of the disciplines: When we deal with WordPress in the Meetup, projects such as the Homeassistant Laboratory (Smart Home) or the Leonardo Workshop (Works and History Leonardo Da Vinci) and many others benefit at the same time.
  • Resource sharing: We use the infrastructure of the association and give back technical know-how. WordPress is often the “adhesive” that makes the information of the various laboratories visible on the web.
  • Community cross-over: A participant arrives because of WordPress and ends up at the AI regulars table or helps with a repair café. This permeability makes the community stable and vibrant.

4. Content strategy: From discussion to documentary

The example of clipperton.at

Often, knowledge is lost after a meetup. We have developed a process to turn fleeting conversations into lasting values.

  • The transfer moment: As soon as a solution to a problem (e.g. B. a plugin configuration) is found, we document it not only for ourselves, but prepare it for the general public.

  • Bridge to the official documentary: clipperton.at serves as a local hub. We translate core content from WordPress.org and supplement it with practical examples from our rounds.

  • Writing together: The documentation itself is a community project. Participants write tutorials about things they have just learned in the meetup (the “learning-taught-learning” effect).

5. Networking: Interfaces to Associations & Repair Cafes

WordPress as an adhesive of civil society

We see the meetup as a service provider for the common good.

  • Demand-oriented development: Instead of solving fictitious problems, we take the websites of real associations (e.g. B. www.offinne.at for repair cafes and visitors website) as case studies.

  • Integration into existing structures: By embedding in the Otelo network (Open Technology Labs) we have physical spaces and a direct connection to other topics (AI, crafts, sustainability).

  • Interface projects: We show how WordPress communicates with home assistant or AI agents, and thus bring people from other tech bubbles into the WordPress world.

6. Scaling: From participant to mentor

How the core team grows organically

With us, there are no up-and-coming concerns, because the border between “organ” and “guest” is fluid.

  • The “help for self-help” culture: Those who receive a solution are encouraged to help the neighbor with a similar problem next time. That creates confidence.

  • Responsibility in small appetizers: Participants take on small tasks (e.g. B. “Can you look after the Playground projector today?” or “Do you briefly write the plugin list?”).

  • Visibility: Who shows expertise (e.g. for example, in design or API programming), targeted as a mentor for this evening, without having to hold an official office.

7. Checklist: Your first meetup without a lecture

Step by step to the open format

If you want to start a meetup based on the Linz model, follow these steps:

  • [ ] Change setting: Remove the stage. Chair circle or U-shape, so that everyone can see everyone.

  • [ ] Provide hardware: A large screen or projector that anyone can quickly get infected with (or share via browser/playground).

  • [ ] The opening question: Don’t start with “Here is my topic”, but with: “Who has a website hurdle, an idea or a tool that we should look at together today?”

  • [ ] Topic Prioritization: Collects 3–5 points on a whiteboard/pad. Decide together what you start with.

  • [ ] Live mode: Goes straight into the backend. Try things live. Failure and troubleshooting are expressly desired – this is the biggest learning effect!

  • [ ] Moderation instead of teaching: Your job as a leader is to make sure that everyone has their say and the experts do not “run” the beginners.

  • [ ] Ensure result: Keep the most important links and insights (e.g. B. for your blog or clipperton.at).

 

Our promise to the community

We show that the barrier between “user” and “developer” is artificial. In the Linzer Runde, websites and people alike are growing. Anyone who comes up with a question today will answer someone else’s question tomorrow. That is the true spirit of WordPress.

 

Concept: WordPress Meetup Manual


CC 2026 – Franz Wieser