React webpart to manage bookmarks

[sudeepghatak]

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 <[email protected]>

Put an x in all the items that apply ([x], no spaces between the [, the x, and the ] ), make notes next to any that haven't been addressed.

• New sample
• Bug fix/update
• Related issues: fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?

The 'Bookmarks Manager' web part allows users to manage and organize bookmarks in a SharePoint list. Users can add, edit, and delete bookmarks, which are displayed in a grid layout. The web part supports both light and dark themes and integrates seamlessly with SharePoint.

Node Version

Node version used: 18.20.6

Checklist

• [ X] My pull request affects only ONE sample.
• [X ] My sample builds without any warnings
• [ X] I have updated the README.md file's Version history. For new samples, created a new README.md file matching this template
• [ X] My README.md has at least one static high-resolution screenshot (i.e. not a GIF) located in the assets folder.
• [ X] My README.md contains complete setup instructions, including pre-requisites and permissions required
• [ X] My solution includes a .nvmrc file indicating the version of Node.js

[Adam-it]

@sudeepghatak awesome work 👏 and sorry for the hold up 🙏
I managed to build and run the sample locally
I left a few minor comments I will try to fixup when merging

[Adam-it]

we should not update any file outside of the sample folder.
Lets revet this change

[Adam-it]

we should not update any file outside of the sample folder.
Lets revet this change

[Adam-it]

the image at the end of the readme template is also needed here. We call it a visitor stats image and you may read about it in the contribution guide. It is needed for telemetry reasons. Lets add it

[Adam-it]

I think this is the wrong title

[Adam-it]

@sudeepghatak unfortunately I cannot perform the fixup for you as your commits are wrongly made directly to the main brand of your forked repo.
When contributing a sample we should create a dev (any name is ok) branch and commit our changes there and then open a PR from the dev branch to this repo main branch, we should avoid doing the changes directly to main as this then blocks maintainers from any possible fixup. So when being on main branch in order to create a new branch for you changes you should run something like git checkout -b your-sample-name main.

Please try to move your changes to a separate branch (you may use the git cherry-pick) command to do that, and close this PR and open a new one. Along the way you may also apply the review comments I left in this PR. If you encounter any trouble along the way please do not hesitate to contact me and we may work it out together 👍
Thanks for contributing to PnP Community. You Rock 🤩

[Adam-it]

We need to move current changes to a separate dev branch different then main before we proceed

[hugoabernier]

Thanks @sudeepghatak for your sample! Always appreciated!

We'd love to have your sample featured in one of our future community calls.

If haven't done so yet, and you'd be interested on showing this great sample in a public community call, please fill in following form and we'll get you scheduled - aka.ms/community/request/demo

Thank you for sharing your sample with others - you rock! 👏🥇👩‍💻