Just a quick heads up.
The link to Creating a Custom Item towards the end of the Readme doesn't work.

When we're creating a custom slide, we need to know the padding that we should add at the bottom, and I couldn't find this value anywhere in the docs, so I had to dig into the code until I found this: android:paddingBottom="164dp".

My suggestion is to create a value on the dimens folder for that particular padding, like customSlideBottomPadding, since it's a must have on custom slides.

Currently, tours are persisted as JSON files and written to the “.tours” directory of your repo. However, we could also explore allowing tours to be defined via actual code comments. For example, the following could represent a step definition above a line of code:

// CodeTour: <tourTitle> <stepNumber> <stepDescription>

While this approach could help mitigate tour decay,

Hi, I didn't see in the documentation or the example a guide on how to link up the continue button to link the click action to another view controller did I miss something?

Also it would seem you would want to run this in a first run situation, do you have a preferred method of detecting first run and launching SwiftyOnboard?

It seems there are plenty of companies / projects using Trip.js for now. So I think it's a good time to add showcase page for Trip.js :)

By default, the child_action_btn_url is an old codex URL that is https://codex.wordpress.org/child_themes and that does not exist.

It should be https://codex.wordpress.org/Child_Themes but this page was moved to https://developer.wordpress.org/themes/advanced-topics/child-themes new URL. So, please update that parameter with the new value.

I want to have the ability to change the view of the circles below (page indicators) and I want to do custom content, Because I want to Implement this on,

So Can I do that?

Hi, it would be nice if you could add skip button for a sequence show case with more than 5 show case.
I has around 10 show case and it kinda annoying for user to click all the way to the end.

If you try to open a tutorial on an iPad when Tutti is built from Xcode 11, the screen will dim but no view controller will be presented.

Checking in on the Stalebot implementation– does it feel too aggressive? Many issues are getting marked stale/closed.

It's a bit more churn than I can personally keep up with, curious to hear how others feel.

@lightandluck weighed in on Slack:

I think extending the time from when Stalebot closes an issue from 1 week to 2 weeks would help.