Use (existing!) meta data from composer.json for Settings.cfg

[marble]

Let's say we only have a composer and a README file: This should be sufficient.

[sypets]

Does this mean it will be possible to not have a Settings.cfg?

Then, we should later update Migrate and Settings.cfg.

Just ping me and I can take care of it.

[marble]

What of this could also be picked from composer.json?

A minimal Settings.cfg file for a documentation project looks like this:

Q: Which of this information could I - maybe - take from composer.json as well,
if Settings.cfg is missing?
Q: Is there a rule how to look for that information?

[kaystrobach]

Everything, if you use the extra section.

There is an author in the composer json and you can pick the version from the git branch or tag.

[mbrodala]

I agree that this could/should be handled via extra. Guessing from the toplevel composer.json fields won't lead to reliable results which in turn will make people ask for override fields anyways.

[gilbertsoft]

But if you anyway have to declare this values via extra section it could also stay in the Settings.cfg imho.

[kaystrobach]

We use the package by mounting the docs folder, so the composer.json is not necessary there.

[mbrodala]

@kaystrobach That's a different usecase. ;-) The one here was about how people could get full docs with just a README.*.

[marble]

Ok, after reading the first comments, I've updated the issue title. The whole thing only make sense if it is about re-using existing information. If people would have to add and maintain extra information they should do so in Settings.cfg. That file already has a lot of documentation and is located closer to ./Documentation.

So I think it really boils down to the case where we only have a README(.rst|.md) and a composer.json. In that case ANY information I can guess from the composer file would improve things. My knowledge about the composer file is too much limited.
If somebody can come up with a list of fields MAYBE could exist in the composer file because they are FREQUENTLY used I still could take them into account if there's nothing else.

But please list the exact names.