shepherd VS Wagtail

In this tutorial, I will show you how to use React Shepherd to easily implement a site tour on your website. React Shepherd is a lightweight wrapper library for Shepherd.js that allows us to create a walkthrough of a website — either parts of the site or the whole application — by using dialogs that represent steps that you create. At the end of this article, we will have a functioning site tour as shown in this video.

Shepherd is a powerful and customizable open source JavaScript library for creating interactive tours and onboarding experiences in web applications. It uses another open source library Floating UI to render the dialog tours. It offers a simple setup process, dynamic content support, the ability to create custom actions and events, and theming and styling too. More importantly, it is responsive too and never goes offscreen on smaller devices. Shepherd also provides excellent documentation and support, making it a popular choice among developers.

This looks great. What does it do differently to Shepherd[0]?

[0]: https://github.com/shipshapecode/shepherd

Yup you’re right (see usage docs here) - now just need to figure out how to make shepherd look better haha

Using/building something like this would go a long way (https://shepherdjs.dev/) and could also have the benefit of keeping the tours in parity with the current L2 UI

we’ve called them Product Tours https://shepherdjs.dev is good

Looks pretty similar to what shepherd does (looks like some of their codebase even uses Svelte too!).

If you like Python 🐍 then check out this project. Wagtail is a popular CMS, combining Django’s powerful customization capabilities with a slick user interface. The newest update brings Django 5.0 support, a new searchable and filterable listing UI, the accessibility checker built into the admin interface, and a brand new 10-step tutorial for developers. This release marks Wagtail's 10th birthday 🎂. Happy birthday to the team and all the best for the next ten years and beyond 🥳.

Repo : https://github.com/wagtail/wagtail

- The discussion thread we use to track all public feedback: https://github.com/wagtail/wagtail/discussions/9553. Comments very welcome.

Not so long ago, I submitted a Pull Request in wagtail to improve the admin performance, especially for non-superusers. Basically, it caches all the user's permissions on first access. However, I was pretty sure that this would load a lot of model fields that we never need but there isn't a tool that gives us that type of report. Therefore, I started building an app that keeps track of all fields accessed so you can easily know which ones haven't been used and apply the only/defer optimisation for Django querysets.

Wagtail would be a good example https://github.com/wagtail/wagtail/tree/main/wagtail/tests

Paarth moving from no contributions to the 21st most contributions - https://github.com/wagtail/wagtail/graphs/contributors.

Over the last few years, I have had the incredible opportunity to be a core team member of the Wagtail project. In that time, I have reviewed many new pull requests, and I’ve also had the chance to submit many of my own across Wagtail and many other projects.

Wagtail 2.15 is the most recent LTS (Long Term Support) release, so it’s not a bad release to stick to at all, at least until February 2023.