Skip to content
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

react-page-navigator Question #5121

Closed
chasquad opened this issue Apr 11, 2024 · 6 comments
Closed

react-page-navigator Question #5121

chasquad opened this issue Apr 11, 2024 · 6 comments

Comments

@chasquad
Copy link

Disclaimer

Yes

Sample

react-page-navigator

Contributor(s)

@hugoabernier

Question

Has anyone been able to build this solution. I'm not a developer, and we're so small that we don't have any. Could someone build and provide the SP package? That would be awesome!

Copy link

Wrong or missing contributor @mentions

Thank you for your submission, but you appear to have forgotten to @mention the sample author(s).

To help increase your chances of getting assistance from the original authors of the sample, you should make sure to @mention the actual authors (and not the repository maintainers).

Make sure to include the @ character before the GitHub username so that the author(s) get notified; using the person's name is not going to work.

Please note that the sample authors will not get notified about this issue unless you update this issue accordingly.

You can find the author(s) of each sample in the sample's README.md, under Solution.

We'll automatically close this issue in 7 days unless you update the issue.

For more information on how to create a good issue, refer to our wiki for more information: How to Create Good Issues

@ivy86
Copy link

ivy86 commented Apr 24, 2024

We are struggling as well. A downloadable app package would be greatly appreciated.

@hugoabernier
Copy link
Collaborator

We are struggling as well. A downloadable app package would be greatly appreciated.

Requests for packaged solutions

Thank you for reaching out! Please note that the samples in this repository are intended solely for educational purposes. Unfortunately, we are unable to provide a built or packaged solution.

For your safety and security, we strongly advise against downloading or installing any packaged solutions from the internet without thoroughly reviewing their contents first. Additionally, please ensure to consult your organization’s security guidelines before employing any samples from this repository in a production environment.

For more detailed information, please review our support guidelines.

Feel free to open a new issue if you'd like to request for help building the solution. Make sure to provide all the requested information so that we can help you as quickly as possible.

We appreciate your understanding and cooperation!

@chasquad
Copy link
Author

Thank you for sharing your insights. I completely resonate with your concerns regarding the shift towards SPFx. As a SharePoint Administrator since the early days of SharePoint, I've witnessed various evolutions within the platform. The move to SPFx, while bringing many benefits in terms of modern web development capabilities and integration options, does indeed present a significant challenge for those of us who are not traditional developers.

The expectation to adapt to a more development-oriented framework can be daunting. It's not just about learning new skills but also about the time and resources needed to effectively make this transition while maintaining our current responsibilities. Microsoft's emphasis on SPFx certainly advances the platform's capabilities, but it also highlights a growing gap that needs to be addressed: the support and resources available to admins who now have no choice but to upskill.

One potential pathway forward could be advocating for more structured learning paths specifically tailored for SharePoint administrators who don't need to develop (write code) but simply need to be able to download and build github samples/solutions. Additionally, more comprehensive community support and real-world examples of SPFx implementations could help bridge this gap.

Recognizing the diversity of roles affected by this technological shift, it's crucial for Microsoft and the community to support a broader base of professionals to adapt effectively.

Remember that we're not all developers. We don't necessarily have all of the tools loaded onto our computers. We definitely don't have every version of every component that is needed to use these "samples" correctly. And, many of us work for non-profits and/or small companies who do not have the resources to have full time developers on staff.

@hugoabernier
Copy link
Collaborator

Thank you for sharing your insights. I completely resonate with your concerns regarding the shift towards SPFx. As a SharePoint Administrator since the early days of SharePoint, I've witnessed various evolutions within the platform. The move to SPFx, while bringing many benefits in terms of modern web development capabilities and integration options, does indeed present a significant challenge for those of us who are not traditional developers.

The expectation to adapt to a more development-oriented framework can be daunting. It's not just about learning new skills but also about the time and resources needed to effectively make this transition while maintaining our current responsibilities. Microsoft's emphasis on SPFx certainly advances the platform's capabilities, but it also highlights a growing gap that needs to be addressed: the support and resources available to admins who now have no choice but to upskill.

One potential pathway forward could be advocating for more structured learning paths specifically tailored for SharePoint administrators who don't need to develop (write code) but simply need to be able to download and build github samples/solutions. Additionally, more comprehensive community support and real-world examples of SPFx implementations could help bridge this gap.

Recognizing the diversity of roles affected by this technological shift, it's crucial for Microsoft and the community to support a broader base of professionals to adapt effectively.

Remember that we're not all developers. We don't necessarily have all of the tools loaded onto our computers. We definitely don't have every version of every component that is needed to use these "samples" correctly. And, many of us work for non-profits and/or small companies who do not have the resources to have full time developers on staff.

While I understand the diversity of our community, and that not everyone is a SPFx developer, it does not change the fact that this repository is only for education purposes; it is not intended to be used for downloading samples.

I agree with the gap in learning paths, and that's why we -- the community -- have started the community docs initiative, to help address these gaps as a community. You can contribute to it, and/or create an issue to ask if someone else in the community is able to help.

You can also join a {Sharing is Caring]{https://aka.ms/sharing-is-caring) online workshop to learn how to configure your workstation, but -- as you mentioned -- this may not be a viable option for those who don't have the dedicated resources to do so.

The feedback you provided is one that we have often provided Microsoft with. To add your voice to ours, I would encourage you to provide your feedback directly to Microsoft. Keep in mind that this repository is a Community-led initiative, and therefore not supported by Microsoft. While there are many Microsoft contributors here, they do so outside of their day-to-day work at Microsoft, on a volunteer basis.

For more extensibility options, I would recommend that you look at the SharePoint app store for pre-built packages.

I hope that this helps?

@chasquad
Copy link
Author

I was under the impression that the SP app store was going away. Did I misunderstand this?

"In parallel with the SharePoint Add-In retirement, adding, updating and acquiring SharePoint Add-Ins via the public marketplace (a.k.a. store) will also be retiring. As of March 1st, 2024 Microsoft will not accept new SharePoint Add-Ins for listing in the public marketplace, from July 1st, 2024 SharePoint Add-Ins cannot be acquired anymore from the public marketplace. Using a tenant app catalog will stay supported and enables 3rd parties to offer their SharePoint Add-Ins until April 2nd, 2026."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants