[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? Replace placeholder contributor initials with the corresponding GitHub account photos and update discussion/video guidance.
• New sample? No new sample is added.
• Related issues: requested gallery refinements; no issue is automatically closed.
• Needs API permissions? No. Avatar images are public GitHub account images; no authenticated GitHub API calls are added.
• Has other prerequisites? Existing gallery requirements are unchanged.

What's in this Pull Request?

• Show each contributor's own GitHub account image, with lazy loading and an accessible profile link.
• Preserve initials as an explicitly logged fallback if an account image cannot load. Keep visible fallback labels and accessible names consistent.
• Make https://community.powerplatform.com/ the primary destination for questions and discussion in the Community hero, shared footer, home/getting-started ribbon, sample resources, and repository guidance.
• Keep invitations to join community calls and present a live demo.
• Add Microsoft Community Learning recordings/demos and Microsoft Power Platform product videos to the Community page and shared footer.
• Centralize shared community destinations and refresh the README promo to reflect the forum guidance.
• Preserve existing sample documentation, metadata, catalog behavior, contributor counts, and view tracking.

Validation evidence

• npm test in site: passed, 26 tests.
• npm run build and final npx astro build: passed.
• npx astro check: passed, zero errors, warnings, or hints.
• npm run validate:links: passed, 95 HTML pages and 599 unique internal targets in the local build.
• npm run test:e2e: passed, all 30 desktop/mobile tests, including accessible avatar success/failure states, exact account-image/profile mappings, forum/video destinations, both themes, filtering/history, and responsive overflow checks.
• All 36 actual contributor image URLs returned successful image responses. Real photos and the revised Community page were visually inspected.
• Verified the forum and both YouTube destinations. Channel metadata confirms @MicrosoftCommunityLearning and @mspowerplatform; the retired @Microsoft365Community handle is not used.
• The unchanged sample reference checks and the complete publication build run in GitHub CI/deployment.

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: this changes shared website/community guidance, not a sample implementation.
• My sample includes a completed assets/sample.json metadata file. No sample metadata is changed.
• I have updated the sample's README.md. Repository/site guidance and the sample README template are updated.
• My README has at least one static high-resolution screenshot (i.e. not a GIF). The existing root promo PNG is refreshed.
• My README contains complete setup instructions, including prerequisites and required permissions. Existing setup instructions are preserved.
• 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. Existing sample trackers and the template's final tracker position are preserved.

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)

[VesaJuvonen]

GitHub Linux CI passed, including the full 30-test desktop/mobile browser suite, accessible avatar loading/fallback states, forum and video links, sample reference checks, metadata/types/build, and generated links. All 36 real contributor avatar URLs were also verified as image responses. Publishing the approved update through the existing main-branch Pages workflow.

[VesaJuvonen]

Published and live-verified at https://pnp.github.io/powerplatform-samples/ . Deployment run https://github.com/pnp/powerplatform-samples/actions/runs/39937683613 succeeded, including the live revision/catalog/sample-route checks. Independent public-page checks confirmed commit 6e98fdf, all 36 account-specific contributor image URLs, the primary Power Platform Community forum CTA, and both verified YouTube channels. Local preview has been stopped and the worktree is clean.