[
https://issues.apache.org/jira/browse/COMMONSSITE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17687649#comment-17687649
]
Sebb commented on COMMONSSITE-165:
----------------------------------
There were good reasons for creating Commons Skin originally; I think this was
partly because of problems with the default skin and the limited customisation
options that it provided. I seem to remember a lot of effort was needed to
solve some relative path issues with the default skin.
I don't know if these are still an issue with the Maven skin now.
You say that problems can be solved with CSS - that may be so, but if the
solution cannot be done at project level, it is going to be a lot of work to
maintain.
There are several differences between your sample build and the current site:
- missing version number in the sub-header
- missing 'Apache Commons ...' in sub-header
- different fonts and sizes
I think quite a bit more testing and evaluation is needed before considering
dropping the Commons Skin.
> [SKIN] Update Commons Skin Bootstrap
> ------------------------------------
>
> Key: COMMONSSITE-165
> URL: https://issues.apache.org/jira/browse/COMMONSSITE-165
> Project: Apache Commons All
> Issue Type: Bug
> Components: Commons Skin
> Reporter: Bruno P. Kinoshita
> Priority: Minor
> Labels: gsoc2023, part-time
>
> Our Commons components use Commons Skin, a skin, or theme, for Apache Maven
> Site.
> Our skin uses Bootstrap 2.x, but Bootstrap is already at 5.x release, and we
> are missing several improvements (UIUX, accessibility, browser compatibility)
> and JS/CSS bugs fixed over the years.
> Work happening on Apache Maven Skins. Maybe we could adapt/use that one?
> https://issues.apache.org/jira/browse/MSKINS-97
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
