Documentation: Add a minimal Services.yaml file ready for customization, explain best practices

[knbknb]

I have installed your nice extension and see some value in it. My intention is to write analytics-queries and monitoring-info as Tasks for the Symfony console (for the typo3cms CLI tool), and move some of those into custom dashboard widgets.

Writing and Registering own widgets is still quite daunting.

Regarding custom_dashboard_widgets code, I have alread patched some of the existing widgets, e.g, recentlyCreatedPages, and have overridden some Fluid templates and partials.
However I have no idea how deal with the Services.yaml file. Should I add my own stanzas to the existing Services.yaml file in the EXT:custom_dashboard_widgets directory? What needs to be imported, do I need to reference other classes in the \Bo PHP namespace?. What to include, where to include it? Never done this before.

Should I create my own extension with a few widgets, however minimal, and add everything there, including a Services.yaml file. That would be more modular and safer when upgrading. Configuration changes in a small own extension would not affect the main configuration.

I think this part is missing in the documentation of custom_dashboard_widgets code.
Also the fact that the extension must be deactivated and then (re-)activated to trigger configuration changes.