cleaning: Default config file needs updating to match current state

[trigg]

[AKArien]

I'd like to take the occasion to talk about cutting down on fragmentation. Between the xmls, the wiki and the comments on the example config, there's currently 3 sources of information.

I would propose that we could have the XMLs as the sole source of information for configuration-related things. How doable would that be ? Especially for adding descriptions to the individual widgets.

The idea would be to make sure the xml has all the information and drop the example config file. Then, we could generate a man page (wf-shell currently has none) for each configuration section, as well as the github wiki.

Not quite a direct answer to the subject at hand, but on a longer term, i would think it would be beneficial to have something of the sort.

[trigg]

No objection to dropping the example config so long as one is generated with comments on each build.

[trigg]

I can't think of a way to do similar with wiki. Between how to push to it on actions and how disparate the information there is.

But the config should be doable provided we move preceding comments into XML and generate it

[AKArien]

I can't think of a way to do similar with wiki. Between how to push to it on actions and how disparate the information there is.

I would move the pages containing configuration information into their own documents, so, with the panel, the ## General configuration section would be be replaced by a link to the new wf-panel-conf.md page, which would be generated from xml in actions.

For pushing, if i’m getting these things correctly, we (someone with the right privileges that i/we would have to convince beforehand) could install a github app on the repo, which with secrets for actions, would have give the permissions to push the new versions to the wiki repo.