Skip to content

feat: add org profile landing page#7

Merged
psjamesp merged 1 commit into
pr/06-docsfrom
pr/07-profile
Apr 21, 2026
Merged

feat: add org profile landing page#7
psjamesp merged 1 commit into
pr/06-docsfrom
pr/07-profile

Conversation

@HeyItsGilbert
Copy link
Copy Markdown
Member

Stack position: 7 of 7 — merge last

The org landing page shown at github.com/PowerShellOrg.

What's in this PR

profile/README.md:

  • One-sentence org description
  • Tool roster table: Plaster and PSDepend with status badges (status-active)
  • "Want us to adopt your tool?" CTA → links directly to the tool_adoption_request.yml template
  • "Want to help?" CTA → links to good-first-issues and help-wanted label searches across the org
  • Links to GOVERNANCE.md and CODE_OF_CONDUCT.md

Council questions

  1. Org description: "PowerShellOrg is a community-run GitHub organization that adopts and maintains open-source PowerShell tools that would otherwise go unmaintained." — Does this capture what we are?
  2. Tool roster: Plaster and PSDepend are the two initial entries. Should Plaster's status badge be active or stable? It's been maintained longer.
  3. Status badge style: currently using shields.io static badges. Would you prefer something dynamic (e.g., pulling from actual CI status)?
  4. Anything missing from the landing page that a first-time visitor would want to see?

Base: pr/06-docs — merge PRs 1–6 first. This is the last PR in the stack.

profile/README.md: tool roster (Plaster, PSDepend) with status badges,
adopt-your-tool CTA linking to the adoption request template,
help-wanted CTA linking to good-first-issues and help-wanted across
the org, links to governance and CoC.
@psjamesp psjamesp merged commit 7fdeb90 into pr/06-docs Apr 21, 2026
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