Making your first contribution to the SharePoint PnP community can be scary!

felt the same way before his first contribution.

That's why his new initiative is designed to help everyone with their first contribution, or anyone who has already contributed but want to do more in the PnP community.

His goal is to make it less scary for everyone.

And it can be plenty scary!

You are not alone

I remember my first contribution to the SharePoint PnP community.

I was terrified!

I've been working with SharePoint since before it was called SharePoint. Heck, I've known SharePoint longer than I've known my wife!

But still, the first time I contributed to an issue in GitHub, I was convinced that I would be discovered as a fraud.

Inevitably, someone was going to find out I had made a mistake and ridicule me.

I wasn't well versed in GitHub. I was concerned that my code would irrevokably destroy the SharePoint repository --including every backup -- and ruin it for everyone.

I'd have to legally change my name, move somewhere far away, and go back to cooking professionally.

Every time I found a code or documentation issue, I would assume that someone much smarter than I would see the same problem and that they would fix it.

"It isn't my place," I would tell myself.

"They probably already know about this..." was my mantra. It was the thing I repeated to myself every time I considered contributing to the community until the urge to fix an issue would go away.

And I'm not a timid person! I'm very strong-willed, stubborn, and opinionated. I'm blunt and direct (hey, if you wanted someone who'll tell you what you want to hear, you should have hired someone else!).

But the idea of contributing to the PnP community felt like what Superman must feel when he's near Kryptonite.

Until one day --when I probably had a momentary lapse in judgment-- I submitted my first contribution and waited for the world to explode.

When I got my first email telling me that my pull request was merged, I realized that I had been worrying for absolutely no reason. In fact, the reviewer who had accepted my pull request was very kind and grateful!

It gave me the courage to contribute a little more often.

With every new contribution, I grew more and more comfortable with GitHub, repos, and discussions, but I still felt nervous every time.

One day, when I was preparing to speak at a SharePoint Saturday, I started chatting with other speakers and talking about how nervous I was when contributing to the PnP community.

One after the other, they all admitted that they all felt the same way their first time.

I couldn't believe it!

Those were people whose blogs I read, podcasts I listened to, and videos that I watched! They were the people whose presentations I attended at every conference I went to!

And they all said that they were scared at first!!!

Just like me!

And, if you're reading this, probably just like you too!

You too can contribute!

It doesn't matter whether you have found an error in documentation, have a code sample to share, or want to participate in an open-source initiative, you have a voice!

And it deserves to be heard, no matter how scared you may be!

That's why David Warner created the Sharing Is Caring initiative.

Sharing Is Caring

Sharing Is Caring is an official PnP GitHub repository that is intended to be a safe "sandbox" for those who want to learn to contribute and/or become more familiar with the PnP GitHub repos.

It is something that David, with the help of , put together to help grow the PnP community and encourage contributions from new (and experienced) contributors.

Every month, David hosts live hands-on workshops where he'll walk you through step-by-step instructions to contribute to a PnP repository.

The workshops are conducted over Microsoft Teams, and you are encouraged to use your camera and microphone to create a fun and relaxed atmosphere.

During the sessions --hosted at different times of the day to accommodate people from all around the globe-- you'll get to use your own space in a GitHub repository. You can follow along, as David demonstrates how to make a contribution.

The first workshop shows you how you can fix a simple spelling mistake in the documentation. Future sessions will include things like creating list formatting samples, contributing to a PnP open-source initiative or creating your own SPFx web part or list extension code sample.

By the end of the session, you've made an official contribution (you'll even get recognized on the monthly PnP calls!). More importantly, you realize that contributing isn't as scary as it sounds and that it is very difficult to mess up. Github isn't going to blow up after all!

I had the privilege to help David host the very first Sharing Is Caring sessions last week. I watched as he patiently explained to 15 new PnP contributors on how to create their first pull requests.

It was great to meet people whose names I had seen countless times on the PnP calls and to interact with them. Because the sessions had few attendees, we got to chat (and we didn't have to ask people to "Please please please mute yourself") and joke a little.

As I was watched on the call, I remembered how nerve-wrecking my first contribution was, and how relieved I was when I realized that many others experienced that same thing. I didn't do much, but I took a moment to tell the attendees that I had been where they were, and that contributing to the community can be very rewarding.

I couldn't help but feel that I was witnessing something important, because the Pnp community became 15-people stronger.

That's 15 new people who are also passionate about SharePoint and Office 365 and who want to help others by sharing their knowledge.

If you'd like to contribute to the PnP community, but need a little help getting through your first contribution, fill the attendee registration form, and David will send you an invitation to his upcoming sessions.

And I'll be there to help!


I'm constantly amazed at how generous people in the PnP community are. David will hate my saying this, but it is pretty amazing that he's willing to spend his time to help other people learn to contribute.

The attendees are incredibly generous, because they spend the time out of their day to learn a skill that will help them donate more of their time to help others!.

Finally, it also says a lot that both Microsoft and Vesa understand the importance of growing a strong community and that they are willing to let people like David (and I) host such sessions and officially recognize the attendees' contributions.

I hope to see many of you on upcoming calls, and I can't wait to meet you all!

Photo Credits

Image by Wokandapix from Pixabay

Note: There are a lot of screenshots in this post. Here's why: there is nothing that I dislike more than having to download/install something to find out exactly what's inside. Yes, there are a lot of screenshots, but you'll know exactly what to expect if you decide to download my PowerPoint template.


As the self-proclaimed World's Laziest Developer, I always look for shortcuts and ways to avoid doing work.

When I start a SharePoint project where I have to design an Information Architecture, I like to use low fidelity wireframes instead of spending countless hours creating SharePoint sites.

I'm not a designer or a user experience specialist, but I'll take the time to do paper napkin drawings, whiteboard drawings, and any other available tools to help work through how my sites are going to be structured and laid out.

I'll even use tools like Balsamiq, UXPin, Adobe XD, and Visio, but I like to spend as little time as possible building my low-fidelity wireframes. Also, I find that few people have experience with those tools (even though they are awesome).

I do it because it is faster convey to my stakeholders what I'm planning on doing and getting feedback with a minimum effort. And I'm all about minimum efforts.

Since PowerPoint now has sketchy shapes, I decided to create a PowerPoint template that contains a sketchy design for SharePoint pages and a few of the commonly used web parts.

My template is not intended to replace the SharePoint Toolkit, but it requires Adobe XD and most client workstations I use do not have Adobe XD. If you can use Adobe XD and the SharePoint Toolkit, do so. If you can't feel free to use my PowerPoint template.

If you want to use it, you can .

Note: This template will only work in the desktop version of PowerPoint. And it may require the Office Insider version of PowerPoint.

A few rules, though:

  • If you add more page designs and web parts that you think other people would enjoy, share it with me and I'll add it to the template
  • Don't go selling this template
  • Share it with others (#SharingIsCaring)

The components

Here are the elements you can use for now:

The Communication Site master

Communication site master

There is also a read-only version of the communication site if you want to show what the experience looks like for visitors:

Communication site read-only

Guided layouts

If you choose a slide master, you can pick a layout to help you place your web parts on the page.

1 column guide
1 column guide

2 column guide
2 column guide

3 column guide
3 column guide

Simply place your web parts so that they fit within the gray area. Once you're done moving the web parts, select the No guide version, which hides all the guides.

Hero web part

Hero web part

(I had a lot of fun drawing the placeholder pictures. Very therapeutic.)

News web part

News web part

Events web part


Documents web part

Documents web part

People web part

People web part

Generic grid layout web part

If you want to write your web part with the grid layout and would like to mock them up in your wireframes, you can use the Generic Grid Layout Web Part. It comes in 1/3 column, 2/3 columns, and full-width variations.

Generic Grid Layout Web Part -- Full width
Generic Grid Layout Web Part -- Full width

Generic Grid Layout Web Part -- 2/3 columns
Generic Grid Layout Web Part -- 2/3 columns

Generic Grid Layout Web Part -- 1/3 column
Generic Grid Layout Web Part -- 1/3 column

Generic filmstrip layout web part

If you want to write your web part with the filmstrip layout and would like to mock them up in your wireframes, you can use the Generic Filmstrip Layout Web Part. It comes in 1/3 column, 2/3 columns, and full-width variations.

Generic Filmstrip Layout Web Part -- Full width
Generic Filmstrip Layout Web Part -- Full width

Generic Filmstrip Layout Web Part -- 2/3 columns
Generic Filmstrip Layout Web Part -- 2/3 columns

Generic Filmstrip Layout Web Part -- 1/3 column
Generic Filmstrip Layout Web Part -- 1/3 column

Generic carousel layout web part

If you want to design a custom web part that uses the carousel layout, use this template. Like the other generic web parts, it comes in 3 flavours: Full-Width, 2/3 columns and 1/3 column.

Generic Carousel Web Part -- Full Width
Generic Carousel Web Part -- Full Width

Generic Carousel Web Part -- 2/3 columns
Generic Carousel Web Part -- 2/3 columns

Generic Carousel Web Part -- 1/3 column
Generic Carousel Web Part -- 1/3 column

Generic list layout web part

I couldn't do the other generic layouts and omit the list layout! This one is also available in Full Width, 2/3 columns and 1/3 column.

Generic List Web Part -- Full Width
Generic List Web Part -- Full Width

Generic List Web Part -- 2/3 columns
Generic List Web Part -- 2/3 columns

Generic List Web Part -- 1/3 column
Generic List Web Part -- 1/3 column

Color palettes

Although many believe that low-fidelity wireframes should use grayscale and contrast instead of colors, sometimes I like to include colors. It really depends on my mood (and the audience).

Whether you're in the "no-colors" camp or in the "with colors" camp, every slide includes the SharePoint color palettes on the right of the page -- outside of the viewable area.

SharePoint color palettes

When you're editing your pages, you can pick the Eyedropper tool to pick the colors you need from the palette.
Eyedropper tool

Don't worry: because they are outside of the viewable area, the color palettes won't show up while you're presenting or when you print.

Color palettes won't print

If you need to find out more about what each color is, there is a section at the end of the PowerPoint template that explains the SharePoint colors.

SharePoint Colors Slide

Other stuff

There is also some token lorem ipsum placeholder text in case you need it, but I try to avoid it.

Also, there are sticky notes to help annotate your wireframes.

Sticky notes and wireframes

What else would you like to see? Let me know in the comments.

Using the template

Here are simple tips to use the template:

  • The template uses an 11"x17" page template. It may seem big, but it prevents you from having to deal with 4pt fonts. Don't worry, it presents well on a screen, and prints great posters for your team project room walls.
  • It uses the new sketchy line styles. It may not work in the web version of PowerPoint or if you don't have the Office Insider edition of PowerPoint. Let me know if you need a non-sketchy version and I'll try to oblige. If you get an error opening it in the web browser, try opening it on your desktop
    Error message with PowerPoint
    If you get this message, it is most likely because I used sketchy lines
  • To emphasize on the "work in progress" look, I used the Segoe Print font because I found that it was available on most workstations that I use. If you don't have this font, feel free to use any font you like. Ink Draft and Segoe Marker work well too. Just resist the urge to use Comic sans !
  • For now, every slide uses the communication site layout (and the read-only variation). I'll add the team site layout if I get requests to do so
  • The title of the slide is the site title
    Site title is the slide title
  • Every site element is grouped to make it easier to move them around. Feel free to un-group them and edit them as you need
    Grouping within the slide
  • I used some theme colors, but feel free to make the designs monochromatic if you want
  • If you need to edit the navigation, feel free to copy the navigation elements (called Site Navigation ) from the master slide and paste the customized navigation on your slide. It already has a white background to hide the navigation from the master slide
    Site Navigation

To edit site navigation

To edit the site navigation, follow these steps:

  1. From your PowerPoint slide, go to View then select Slide Master in the Master Views group
    Slide Master from the View ribbon
  2. PowerPoint should automatically take you to the master slide called Communication site. Select the site navigation by clicking on the site icon and click Copy.
    Copy site navigation
  3. From the Slide Master menu, select Close Master View to go back to your slide
    Close Master View
  4. Paste the navigation on top of the existing navigation. The white background behind the site navigation you just copied should hide the existing one from the master slide.
  5. Edit the navigation and site icon as you wish

To create your own wireframe

Although I have a sample wireframe in my template, you can create your own using these simple steps:

  1. In PowerPoint, insert a new slide in your presentation by going to New Slide and select the layout you want
    New Slide Menu
    You can pick from the Communication Site -- Edit Mode to show what an author would see, or Communication Site -- Read-only Mode to show what a visitor would see.
  2. Try to start with one of the guides. You can choose from 1 column guide, 2 column guide or 3 column guide.
  3. From the Web Part Templates section, find the web parts you want from the other slides in the PowerPoint template, copy them and paste them onto your new slide.
  4. Make sure to place the web parts within the gray areas on the guides.
  5. Edit the web part elements (like web part title and content). It may help to ungroup them first.
  6. Once you're done placing your web parts, go to Layout and pick the No guide version of whatever master you chose. It will remove the background guides, but will not affect where you placed your web parts.

Tips when preparing low fidelity wireframes

As Page Laubheimer from the Nielsen Norman Group puts it:

Sharing low fidelity user-interface prototypes with stakeholders is a great way to transfer knowledge and get buy-in early.

Tell your audience that this is work in progress. It may be obvious to you, but I have had clients get upset that their site was going to look "all wobbly" (and others who asked if the site was going to only be "in French" because I used lorem ipsum). Explain that you used this style of wireframe to help focus on the content and structure, not the look.

Explain to your audience that this is a great opportunity to share knowledge: for them to transfer their knowledge to you by getting their feedback early.

Don't worry about the look and feel, worry about the content/structure and function. Resist the urge to put lorem ipsum and try to put some text that is as real as you can make it for now.

Another way to use these wireframes is to print them and get your audience to mark them with their notes. You'd be amazed by what information you can get from watching people circle, underline, and annotate paper wireframes.


My is available for you to use.

I'll continue adding web parts and designs. If you need anything else added to it, let me know in the comments.

Maybe I'll create a higher-fidelity version of these if people like them. I'd also love to create a version that you can print out and cut so that you can layout page designs on paper.

Let me know what you think?


  • August 5, 2019: Thank you for pointing out the broken link. Moved files to GitHub repo to make it easier for those of you who wish to contribute.
  • August 3, 2019: Added more web parts (List, carousel, filmstrip) and explanation why I have so many damned screenshots. Also added introduction how to use the guides and section explaining color palettes.
  • August 2, 2019: Added more web parts (generic grid 1/3, 2/3, and full width) and guide layouts