> ## Content Index > Fetch the complete content index at: https://blog.rickzeleznik.com/llms.txt > Use this file to discover other available public pages before exploring further. # SharedSamples.org: A Visual Front Door to Microsoft 365 Community Samples - URL: https://blog.rickzeleznik.com/sharedsamples-org-a-visual-front-door-to-microsoft-365-community-samples/ - Published: 2026-09-09T01:14:20.000Z - Updated: 2026-09-09T01:14:20.000Z - Author: Rick Zeleznik - Tags: Microsoft 365, SharePoint, M365, Consulting, AI I’ve been tinkering with a sort of GUI for the [Microsoft 365 community](https://pnp.github.io/?ref=blog.rickzeleznik.com) GitHub. The idea started while I was navigating in and out of a few different repositories looking at examples of column formatting, trying to find a shortcut for something I was working on. It occurred to me that we could do more to make the community’s samples accessible to business and power users, while also making them easier to browse for inspiration. There is already an enormous amount of useful content in the [Microsoft 365 & Power Platform community repositories](https://pnp.github.io/?ref=blog.rickzeleznik.com). The issue wasn’t a lack of content… it was that GitHub is fundamentally optimized for source control, contribution, and development workflows. That makes perfect sense for the people building and maintaining the samples. But it’s not always the easiest place for someone who simply wants to answer a question like: > **“What could I build with this?”** That is the problem I wanted to explore: From repository to visual catalog The result is [**SharedSamples.org**](https://www.sharedsamples.org/?ref=blog.rickzeleznik.com), a visual, browsable catalog of community samples, published this past weekend. Instead of beginning with folders, filenames, and repository structures, the site begins with what the samples actually look like. The goal is to let someone browse visually, discover an example that catches their attention, understand what it does, and then drill into the underlying source when they are ready. In that sense, I think of [SharedSamples.org](https://www.sharedsamples.org/?ref=blog.rickzeleznik.com) as a **visual front door** to the community repositories. ![](https://storage.ghost.io/c/d3/2f/d32fe8cd-8fa0-40a5-af79-76549307063e/content/images/2026/09/1788646443868.jpg) It’s not intended to replace GitHub. GitHub remains the source of truth and the home of the samples. [SharedSamples](https://www.sharedsamples.org/?ref=blog.rickzeleznik.com) simply provides another way into that content. **If GitHub is the library,** [**SharedSamples**](https://www.sharedsamples.org/?ref=blog.rickzeleznik.com) **can be a showroom.** ## **Making inspiration easier** There is also a discovery problem that goes beyond technical accessibility. Sometimes you don’t know what you’re looking for until you see it. A SharePoint list formatting sample, Copilot component, or other customization may solve a problem someone has never thought to search for by name. A visual catalog changes that experience. Instead of searching for a very specific technical capability, someone can browse through examples and think: > **“That would be useful for us.”** That’s especially important for business users, makers, and power users who may understand the problem they are trying to solve but not necessarily know the terminology used in the underlying repository. ## **Bridging the last mile with Copilot** The part that has become particularly interesting to me is what happens after someone finds a sample. Discovery is useful, but there is still a gap between finding source code on GitHub and implementing that sample inside an organization. That is where Copilot comes in. For supported samples, SharedSamples.org provides **purpose-built Copilot prompts** designed to carry the relevant sample source and implementation context forward. Rather than expecting a business user to interpret the repository, figure out which files matter, and determine how to explain the sample to Copilot, the site provides a ready-to-use handoff. The flow starts to look something like this: ****Community source → visual catalog → purpose-built Copilot prompt → implementation in your environment** That makes [SharedSamples](https://www.sharedsamples.org/?ref=blog.rickzeleznik.com) more than just a gallery. The visual catalog helps people find the right starting point. The Copilot integration helps bridge the last mile between inspiration and implementation. ## **Built around the community** The most important part of all of this is that the value originates with the community. [SharedSamples.org](https://www.sharedsamples.org/?ref=blog.rickzeleznik.com) does not create or take ownership of the underlying samples. The goal is to shine a brighter light on the work contributors have already created and make that work accessible to a broader audience. If the site succeeds, I hope it helps more people discover community content, gives contributors greater visibility, and makes it easier for organizations to benefit from ideas that are already being shared. The catalog currently includes samples across areas such as SharePoint List Formatting, SharePoint Skills, and SPFx Copilot Components, with room to expand into additional community repositories over time. **Still experimenting** This is very much an evolving project. I’m still experimenting with the experience, the organization of the catalog, and how far the Copilot handoff concept can go. But the basic idea has stayed consistent: > **Make community samples easier to discover, easier to understand, and easier to put to work.** You can take a look at [**SharedSamples.org**](https://www.sharedsamples.org/?ref=blog.rickzeleznik.com), and I’d genuinely welcome feedback - good, bad, or indifferent. The community built the samples. My hope is simply to help more people find them.