[ 
https://issues.apache.org/jira/browse/SLING-6850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016524#comment-16016524
 ] 

ASF GitHub Bot commented on SLING-6850:
---------------------------------------

GitHub user auniverseaway opened a pull request:

    https://github.com/apache/sling/pull/233

    Launchpad Homepage update for Sling 9

    This PR is to address 
[SLING-6850](https://issues.apache.org/jira/browse/SLING-6850)
    
    The new launchpad homepage is completely redesigned for better information 
architecture while retaining the spirit of the original.
    
    The new homepage is responsive, and leverages flexbox to vertically center 
the content when the viewport is beyond a certain size.
    
    To address front-end productivity, I have added a launchpad clientlib which 
uses SCSS to generate the minified CSS.
    
    To not be heavy handed with an FE build process, I have ***not*** added the 
[frontend-maven-plugin](https://github.com/eirslett/frontend-maven-plugin), so 
overall build time should not be affected. The idea is that the CSS is the CSS, 
and if you want to change it, you can run `npm install` and `gulp` manually.
    
    Let me know if you want any changes @rombert.
    
    
![sling-home](https://cloud.githubusercontent.com/assets/1972095/26224923/ee34fa68-3be1-11e7-83f6-dea63b00dc18.jpg)


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/auniverseaway/sling 
SLING-6850_Launchpad_Homepage

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/sling/pull/233.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #233
    
----
commit c3742b5a2a7671475b76e881ac5a4fe731362f0e
Author: Chris Millar <cmil...@adobe.com>
Date:   2017-05-18T21:40:09Z

    Launchpad Homepage update for Sling 9

----


> Address Launchpad homepage information architecture
> ---------------------------------------------------
>
>                 Key: SLING-6850
>                 URL: https://issues.apache.org/jira/browse/SLING-6850
>             Project: Sling
>          Issue Type: Improvement
>            Reporter: Chris Millar
>            Priority: Minor
>             Fix For: Launchpad Content 2.0.10
>
>         Attachments: Launchpad - Current Design.png, Launchpad - Proposed 
> Design.png
>
>
> 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:
> ## Brand new developer - Why did I just type `java -jar org.apache.sling`?
> ## Experienced developer - Give me a list of the guts in this site / app. 
> Give me external resources to help keep me going.
> ## 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?
> ## 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...



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to