I agree we could easily do something to get a more pleasant view of this content, even if it's deprecated. Here is a PR fixing the CSS with screenshots, and a suggestion for another PR to simply replace the logo image in the footer by one with a (fire) butler and a deprecation message for exameple. (Suggesting this as a quick way to deal with it)
https://github.com/jenkins-infra/docker-confluence-data/pull/30 WDYT? On Monday, October 3, 2022 at 6:26:09 PM UTC+2 m...@basilcrow.com wrote: > On the other hand, I do not think it is a good look for the project to > have a major web property with a noticeably broken stylesheet. We want > to look like a vibrant and inviting community, not a run-down > neighborhood. > > If the goal is to communicate that the old wiki content is deprecated > and needs to be updated and moved to the official documentation at > jenkins.io, I suggest putting a banner on each page that explicitly > states that, linking to the official documentation and examples of how > to migrate legacy content. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e94b2136-6164-459b-a1f5-9efd03fd56can%40googlegroups.com.
