Also relevant for #3255.

Happy to take care of the PR when we have the wording, might take a shot this week while I browse the docs.

cc @Zaxounette

This is a great idea!

I think we can expand the scope of it, for not just the pages mentioned, but also some sub-pages. For example I think Payments page in Store Settings deserve explanation. For example Configure your store payment settings that global for all payment methods. We'll probably need copywriter to help with these.\

@pavlenex Tend to agree it would be helpful to provide more context for the some of the sub-pages that are integral to the functionality of the "core" features.

I've been thinking about this more as I step through all of these views, and the big question in my mind is not that we should explain the feature, definitely clear we should, but where?

1. For example, even having a 1-2 sentence explanation on the Payment Request / Payout / Pull Payment, etc.. list view would be incredibly obtrusive and become quite a nuisance after a short while if it's always "present".

We could alleviate this by treating the short explanation like an alert (could be styled slightly differently) that can be dismissed once the user has read or feels they understand.

2. Exploring the concept from no.1 further ... we have the (?) asset, which has historically linked directly out to the external documentation. We could leverage this to drop an accordion explaining the feature in a simple way, and providing a link to read more in the docs. More permanent and less obtrusive than no.1. Even further, we could even "expand" it on first-time users, and when they close the section, it's then always accessible afterwards, incase they forget, want to read docs, etc..

For example. I used @BenGWeeks' copy, and obviously we can refine this, simplify with a simple line-by-line (second item), etc.. bu this should give an idea of what's possible:

3. We also have the "Create" views for some of the features (Pull Payment / Payment Request / Invoice) where the same logic from no. 1 applies .. there are some drawbacks to this approach, but it's also worth considering...

Still thinking on this, but wanted to push it further for more discussion / feedback!

Concept ack.

concept ack