2026-03-26 Green Software Principles & Patterns agenda #394
Description
Date
2026-03-12 - 15:00 GMT - See the time in your timezone https://everytimezone.com/
Roll Call
Please add a comment to this issue during the meeting to denote attendance.
Agenda
- Convene & Roll Call
- Review the agenda and suggest new agenda points
- New GSF Website
- Patterns 2.0
- New User Experience
- AOB, Q&A & Adjourn
Patterns 2.0 - New User Experience
- Do the three journeys below reflect the users we actually see coming to the site today?
- Are there journeys we've missed that the new structure should serve?
- For each journey -- where does the current site fall short, and does the proposed restructure fix it?
Journey 1 -- "I have a specific problem to solve"
User: A developer who has been asked to reduce the carbon footprint of a specific part of their system -- for example, a data pipeline or an AI inference workload.
Entry point: Direct link, web search, or colleague referral.
Goal: Find a pattern that addresses their specific context quickly and with enough detail to act on.
Steps:
- Lands on the site and immediately understands what it is and what it offers
- Searches or filters by category (e.g. AI and ML Lifecycle, Data and Networking)
- Scans pattern titles and summaries to identify candidates
- Opens a pattern and assesses whether it applies to their situation
- Takes the pattern away to implement or share with their team
What good looks like: The user finds a relevant pattern within 2-3 clicks without needing to understand the GSF's internal taxonomy.
Key UX questions this raises:
- Is the category structure intuitive to someone who doesn't know how we built it?
- Are pattern summaries scannable enough to support quick triage?
- Does the cross-cutting topic filtering (e.g. Observability, AI and ML) help or add noise?
Journey 2 -- "I don't know what I don't know"
User: A sustainability lead or engineering manager who wants to understand what green software practices exist, with no specific problem in mind. They are building a picture.
Entry point: GSF homepage, conference reference, or search.
Goal: Get a meaningful overview of the landscape without having to read everything.
Steps:
- Lands on the site and understands the scope of the catalogue at a glance
- Browses by lifecycle phase or cross-cutting topic to understand the shape of what's available
- Dips into a small number of patterns to assess depth and quality
- Leaves with a mental model they can use in their organisation
What good looks like: The user can describe what the catalogue covers and identify 2-3 areas relevant to their organisation after a single visit.
Key UX questions this raises:
- Does the homepage communicate scope and structure clearly without overwhelming?
- Do the category and cross-cutting topic labels make intuitive sense to a non-GSF audience?
- Is there a way to surface the most adopted or highest quality patterns for browsers?
Journey 3 -- "I want to see if this is credible"
User: A senior decision-maker -- a CTO, Head of Platform Engineering, or sustainability director -- who has been pointed to the catalogue and wants to assess whether it's worth their team's time.
Entry point: Referral from a colleague or GSF member contact.
Goal: Form a quick confidence judgment about the quality, breadth, and authority of the catalogue.
Steps:
- Lands on the site and immediately reads credibility signals -- number of patterns, member organisations, specification links
- Spot-checks 2-3 patterns for quality and rigour
- Checks whether their industry or technology domain is represented
- Decides whether to share with their team or engage further with the GSF
What good looks like: The user feels confident recommending the catalogue to their team within a single session.
Key UX questions this raises:
- Are quality and authority signals visible without digging?
- Does the catalogue feel complete enough to be taken seriously?
- Is there a clear next step for someone who wants to go deeper (e.g. become a contributor or GSF member)?