[SLING-6850] Address Launchpad homepage information architecture - ASF JIRA

XML

Word

Printable

JSON

The launchpad homepage could use some love...

The page is not responsive.
Design is dated.
The page has several links that are either out of date (composum always installed now), repeated (OSGi console), or not helpful (sign up).
Does not speak to audiences of different skill levels.

My proposal addresses these concerns with the following updates:

Page is responsive
Page is designed to address three audiences:
1. Brand new developer - Why did I just type `java -jar org.apache.sling`?
2. Experienced developer - Give me a list of the guts in this site / app. Give me external resources to help keep me going.
3. Potential Contributor - How do I get involved?
Bad / duplicated / unused links have been removed. - I'm looking at you signup page and client test page (which 500s in snapshot).
Apache logo has been added.
Retained most of the excellent welcome text (with updated links to Oak and Felix).
Friendlier colors have been used.
Custom font (Open Sans, AL 2.0) has been used instead of Tahoma (not AL 2.0)
Slightly larger typography to meet current trends.
Used old yellow / blue horizontal rule as the design inspiration for the left rail rule (that uses feather color palette).
Built out concise list of top resources for both the current site as well as external resources.

Items worth discussing:

Should the first heading under "Resources" be "This Site" or "This Application"?
Should the HTL REPL be included in the list of links.
Should the Bootstrap clientlibs (used in HTL REPL) be used to build the page even though they are MIT? If not, should we refactor the clientlibs folder so REPL can be self contained and other libraries can also use /etc/clientlibs?
1. I have a flexbox based grid system I'd be willing to donate / use / document.
Other things I'm not thinking of that may be contentious...

is related to

SLING-6666 Make Sling shiny

links to

GitHub Pull Request #233