[VesaJuvonen]

By submitting this pull request, you agree to the contribution guidelines

If you aren't familiar with how to contribute to open-source repositories using GitHub, or if you find the instructions on this page confusing, sign up for one of our Sharing is Caring events. It's completely free, and we'll guide you through the process.

To submit a pull request with multiple authors, make sure that at least one commit is a co-authored commit by adding a Co-authored-by: trailer to the commit's message. E.g.: Co-authored-by: name <name@example.com>

Put an x in all the items that apply ([x], without spaces), make notes next to any that haven't been addressed.

• Bug fix? Documentation focus: the front page should introduce the community and samples, not website infrastructure or repository migration.
• New sample? No sample is added or changed.
• Related issues: user-requested README refinement; no issue is automatically closed.
• Needs API permissions? None.
• Has other prerequisites? None.

What's in this Pull Request?

Rewrite only the root README around the power of community and getting started:

• Lead with the gallery promo and clear links to the published sample gallery, getting-started guide, and contribution guide.
• Explain how to discover, understand, try, and adapt a Power Platform sample.
• Promote the Power Platform Community forums as the primary discussion space, the Copilot/Microsoft 365/Power Platform community hub, and community calls for staying up to date.
• Encourage contributors to share samples, improve guidance, and present live demos.
• Retain both YouTube channels, the contributor badge, responsible sample-use guidance, and the Code of Conduct.
• Remove Astro/local development commands, migration sections, old repository references, and legacy catalog/report promotion from the README.

The website implementation, historical assessment, sample files, and publication workflows are unchanged.

Validation

• git diff --check: passed.
• README content assertions: passed; required gallery/community links are present, both existing images resolve locally, and no stack/migration/old-repository references remain.
• HTTP checks for the published getting-started/contribution/contributor pages, forum, community hub, call schedule, and demo request: all returned 200 after redirects.
• Local application builds/tests: not run, documentation-only change. Repository CI runs automatically on this PR.

Checklist

This checklist is mostly useful as a reminder of small things that can easily be forgotten – it is meant as a helpful tool rather than hoops to jump through.

Put an x in all the items that apply ([x], no spaces), make notes next to any that haven't been addressed.

• My pull request affects only ONE sample. Not applicable: root README only.
• My sample includes a completed assets/sample.json metadata file. No sample metadata is changed.
• I have updated the sample's README.md. This updates the repository README.
• My README has at least one static high-resolution screenshot (i.e. not a GIF). The existing gallery promo and contributor badge are retained.
• My README contains complete setup instructions, including prerequisites and required permissions. It links to the published getting-started/contribution guides and directs readers to sample-specific prerequisites.
• The final line of my README is <img src="https://m365-visitor-stats.azurewebsites.net/powerplatform-samples/{sample-path}" />, with {sample-path} replaced by the repository-relative sample folder path. Not applicable to the repository README; sample trackers are unchanged.

Submitter Guidance (DELETE AFTER READING)

Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.

Pull requests that do not follow this template will be automatically rejected.

Please target your PR to main branch.

Remember that this repository is maintained by community members who volunteer their time to help. Be courteous and patient.

(DELETE THIS SECTION AFTER READING)