Whilst I agree I'm slightly concerned about the multilang sample install as that enables the language filter plugins etc and I don't want to make that part too hidden. However I also agree it being available on the dashboard after it being used makes little sense

The thing is that on a multilingual site you can use the blog sample data multiple times, one time for each language. So to hide Blog Sample Data after having been used once would not be good.

how about placing two buttons below to let the user decide "ask me later" or "no thanks" and thenn hide the module after being used or after the decision

So or so, when moving around I would pefer the system dashboard. The content dashboard is too hidden in my opinion. But that's just my personal taste.

there is already a pr for only displaying multilingual sample data on a multilingual site

Hmm, the system dashboard is so full already, better not move it to there.

@brianteeman I guess you meant PR #20749 , right?

Please, please... Sample data install not being any more possible during J installation, they have to be available in a very obvious way, and that is in the first CPanel dashboard.
As for #20749 I have already commented on it.
Hiding stuff is not the right way to help users. J is not only for integrators...

simple disable the relative plugins if you don't want those in the dashboard
plus the relative sample data admin module

Maybe it would be good to have a simple / advanced switch in the installation process ? Is that a idea to suit all target groups?

Not really a solution as anyone using a hosting companies installer will never see that

@brianteeman good point. Then maybe a one-click hide button would be nice.

That already exists - see animation below

@brianteeman - Yes I meant a one-click solution to make it as easy as possible. But that's fair enough.

so can we close this one ?

Since the sample data module can also be used by 3rd parties, hiding it isn't the best way as you wouldn't see sample data installation for your newly installed component.
A better solution would be to have that unpublish function also for each sample data (plugin) listed in that module. Then one could just easily hide the multilingual and blog sampe data while the module would still be able to display newly added sample data plugins.

A recent PR has now implemented the suggestion from @Bakual so I guess this can be closed

Closing as fixed by #33168 and #33169 . Feel free to re-open if this is a mistake.