Skip to content

Update "who we are", "what we do", contact, and sponsor pages - #353

Open
mattstauffer wants to merge 4 commits into
mainfrom
mes/elizabeth-updates-round-2
Open

mattstauffer wants to merge 4 commits into
mainfrom
mes/elizabeth-updates-round-2

Conversation

@mattstauffer

Copy link
Copy Markdown
Contributor
  • Who we are (/structure)
    • Updated the Community list
    • Added public Board meeting minutes link to the Board section
    • Moved the Governance section here from "What we do."
  • What we do (/foundation)
    • Rewrote the intro around three focus areas
    • Added Language Development, Community Engagement, and PHP Representation sections; wrote to-be-reviewed content for Community Engagement and PHP Representation
    • Moved existing RCF content under Language Development)
    • Stripped years from the Team Timeline
  • Contact (/contact)
    • Added a Bluesky link
  • Sponsor (/sponsor)
    • De-yeared the Silver-tier example sentence
    • Replaced the outdated Sponsorship Deck with links to the annual Impact & Transparency Reports (2025 button + 2022–2024)

- Add link to board minutes
- add social media for matt stauffer
- add community members
- move governance section from foundation to structure page
@github-actions

github-actions Bot commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

@ElizabethN

Copy link
Copy Markdown
Contributor

@mattstauffer this looks awesome! I can't believe how quickly you knocked these out compared to how long this sat in my to-do list 🥴 I really appreciate your help here!

I have 2 quick questions:

  1. As a part of this PR, are you able to change the mission statement back to what it was?
  2. In thinking about how we share the Impact reports, would it make sense to link to all of them through this tag: blog/tag/report/ ? That way we wouldn't have to update this part at all; any new reports will just get added to the list automatically. What do you think?

Thank you again for making these updates! (And if you see things that could be better, we can iterate on this for sure. You're way more of an expert in this than I am!)

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants