Skip to content
Permalink
Browse files

[JENKINS-43786] Addressed some carlosrodlop's suggestions

  • Loading branch information
recena committed Jan 15, 2018
1 parent be03c5d commit 331848eaed80bcd8697f8ce8e3a08d0ceec90648
Showing with 5 additions and 5 deletions.
  1. +5 −5 content/blog/2018/01/2018-01-15-overhaul-of-manage-jenkins-page.adoc
@@ -10,13 +10,13 @@ author: recena

== Overview

Recently we have introduced some UI improvements around to the Manage Jenkins page. The visual changes are very subtle but behind of them, there are interesting benefits.
Recently some UI improvements around to the Manage Jenkins page have been introduced. The visual changes are very subtle but behind of them, there are interesting benefits.

Some of the goals that we have tried to achieve:

* Apply a https://en.wikipedia.org/wiki/Semantic_HTML[semantic HTML]
* Applying a https://en.wikipedia.org/wiki/Semantic_HTML[semantic HTML]
* Remove the `<table>` tag usage for implementing layouts and content structures. Read this https://www.hotdesign.com/seybold[article] if you want to know reasons and / or arguments.
* Small re-style focused on spacing, margins, composition, etc..
* Small re-styling focused on spacing, margins, composition, etc..
* Accesibility

In order to provide a quick view of the visual changes, let's take a look at these screenshots.
@@ -37,7 +37,7 @@ image:/images/post-images/2018-01-15-JENKINS-43786/JENKINS-43786_4-before.png[ro

image:/images/post-images/2018-01-15-JENKINS-43786/JENKINS-43786_1.png[role="center"]

In the following section you will find information about how this change can affect to the current implementations of the https://jenkins.io/doc/developer/extensions/jenkins-core/#administrativemonitor[Administrative Monitors].
Information about how this change can affect to the current implementations of https://jenkins.io/doc/developer/extensions/jenkins-core/#administrativemonitor[Administrative Monitors] can be found in the following section

== For core developers

@@ -133,7 +133,7 @@ In your view (a.k.a. Jelly file):

If you don't want to keep a _strict_ backward compatibility, the impact is minimum. In fact, you can see an https://github.com/jenkinsci/github-plugin/pull/177#issuecomment-337266953[example] on GitHub Plugin.

Some helpful links:
Some helpful references:

* https://issues.jenkins-ci.org/browse/JENKINS-43786[JIRA issue] where the proposal was tracked
* https://github.com/jenkinsci/jenkins/pull/2857[Pull Request] with change in Jenkins core. You can find several screenshots

0 comments on commit 331848e

Please sign in to comment.
You can’t perform that action at this time.