No obvious way to report issues with the parent logging site

[sebbASF]

As the subject says: where should one report issues with logging.apache.org?

[ppkarwasz]

Feel free to report the problem here.

[sebbASF]

Thanks.

This report in itself is an issue: i.e. no obvious documentation on where to raise such website issues.
(I'll raise separate issues for unrelated problems)

[vy]

@sebbASF, logging.apache.org has a menu item, Support, at the top. That page documents User support communication channels and several other things in the context of support. I presume you already figured this out yourself, but still didn't find any of the comm. channels listed there suitable to your needs. How can we adapt that page to help you?

[sebbASF]

The section at https://logging.apache.org/support.html#issues links to various issue trackers for sub-projcects, but does not provide info on how to report generic issues.

A related problem is the reporting template for issue lists such as this one is not really suited to reporting website issues. The project might wish to consider enabling issues on the logging website repo(s) and link to them from the relevant website pages

[vy]

The section at https://logging.apache.org/support.html#issues links to various issue trackers for sub-projcects, but does not provide info on how to report generic issues.

Got it. Updated l.a.o/support.html to guide on "not project¹-specific" inquiries.

¹ I know, Log4j is not a project, but a subproject. Though almost all users (including several ASF members! 🤦) are not aware of this fact.

A related problem is the reporting template for issue lists such as this one is not really suited to reporting website issues. The project might wish to consider enabling issues on the logging website repo(s) and link to them from the relevant website pages

On 2024-09-03, we migrated the websites of Log4j and related projects to Antora. We deliberately worked hard to ensure each Antora page is decorated with a working Edit button at the top. It helped enormously – since then users contributed several website fix PRs and issues. We intend to migrate l.a.o to the same setup too.

I would refrain from disclosing the website repositories and documenting them. They are an internal implementation detail, they are intertwined in a sophisticated manner, and their setup is on the flux (for instance, the cited Antora change significantly disrupted that landscape, in a positive way).