-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
📣 Promote SPFx Toolkit #355
Comments
Great idea! A bluesky account can be a next step, linked to every merge 😉 |
TBH we did that in CLI for M365 that we have dedicated channels/accounts for CLI. |
Totally fine. Can these official PnP Accounts be used to spread tips like "did you know that with the SPFx toolkit, you can validate your project"? 🤔 next to that:
|
Yes totally, this is what we already do in LinkedIn where we use the official PnP account to post many tip updates. Also regarding CLI for M365 and also about SPFx Toolkit. The biggest advantage is that we don't need to work on gaining followers as we already have a lot of them that just follow PnP community. So this is what we want to do.
Those are very good ideas, keep those coming 👏👏👏! I will add those to the initial post of this issue and let's start gathering ideas on blog post topic or what we could show in each tutorial etc. |
@nicodecleyre I updated the initial post based on your suggestions. I think those are very good areas 👍. |
Really cool! Very clear now that you have split it up by domain 🤩
|
@nicodecleyre those are some awesome ideas 👏🤩 as for Social media engagement I like all of the suggestions 👍. I will try to create a separate issue and start working on the content so we may schedule those kind of posts from December for next 2 months as for Blog ideas:
as for Video tutorials and for Community call demos those are good ideas. Not yet specific but I may work on it and create some initial list based on the functionalities we have Thanks @nicodecleyre for engaging in this brainstorm. This is a great help 👏👏👏. You Rock 🤩 Based on our discussion I will try to create some initial list ASAP and let you know what you think about it. And then lets just create issue per item (blog post, video, community call demo) so that we may try to engage others to help out 😍 |
There are so many great ideas here and this one is my favorite. I think weekly feature spotlights could do wonders to promote this tool. Also, if community leaders in the SharePoint space could mention it on LinkedIn/BlueSky, it could encourage more developers to check it out. |
@Saurabh7019, @nicodecleyre I spec'ed out a couple of issues for creating blog posts and doing a demo on one of the PnP community calls. |
A lot of awesome stuff was done and brought to the product. We may always do better and improve and add more and more features but if we won't promote and tell anyone then it just does not make sense.
The aim is to help others in their SPFx development so we need to spread the word to make it easy to find and checkout this extension.
In this issue I want to gather ideas/suggestions of couple of promoting activities we may do and then create separate issues for them so they could be even taken by contributors of this repository.
I am open for any suggestion so if you are reading this issue feel free to just leave comment 👍🙏.
Some ideas:
Social media engagement
Blog posts on PnP blog
Video tutorials - in the past when this still was Viva Connections Toolkit I did some shorts about this tool and it got some engagement. It was our intro in shorts in our YT and it was a total pain to do 😅. But maybe it's worth recheking
Community call demos
Promo video about SPFx Toolkit - I was thinking of a short (3 min) short movie that would just showcase some functionalities of the product and would just do a general brief overlook of the tool
💡 [Feature]: Create docs web page for this product #352 - having a webpage which is indexed, searchable will also help and it may also be a place to store common use cases/ examples of SPFx Toolkit features
Previous marketing things done are all grouped in this wiki page
The text was updated successfully, but these errors were encountered: