Details
-
Type:
Task
-
Status: Done (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: design, plugin-site
-
Labels:
-
Similar Issues:
Description
There's going to be some overlap in the styles between these two applications that we should share in some form or another.
The site generation is using awestruct in the jenkins.io repository, and the plugin site is a different application entirely that we should be hosting under plugins.jenkins.io.
The simplest/dumbest approach would be to copy and paste styles between the two applications, but that isn't great.
Here are some things to consider:
- Packaging shared styles in a npm module or some other referencable artifact that both applications can pull down at build time
- Handling the top nav bar content, i.e. ensuring the links listed in the top navigation bar are consistent between the two sites
We already use bower to install some node packages in the jenkins.io generation process so that might work, but I'm not familiar enough to make a decision on which direction to go here
Attachments
Issue Links
- is related to
-
INFRA-563 Deploy plugins.jenkins.io
-
- Closed
-
-
WEBSITE-96 Introduce a Sass compiler into the jenkins.io build process
-
- Done
-
-
INFRA-496 Setup a local (to CI) NPM registry mirror
-
- Resolved
-
Some Sass infrastructure shared between a number of sites including the product, will make sense, but I don't view this as a ship requirement.