sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Klco (JIRA)" <>
Subject [jira] [Commented] (SLING-7242) [Shiny] Sling Website Design
Date Mon, 21 May 2018 02:27:00 GMT


Dan Klco commented on SLING-7242:

First, the new design looks awesome!

Two thoughts / recommendations:
 * Set a .5em padding-x on the .page-container to keep the text from being right on the edge
of the screen
 * Set overflow-x: scroll on pre elements so that the viewport doesn't expand in mobile view


> [Shiny] Sling Website Design
> ----------------------------
>                 Key: SLING-7242
>                 URL:
>             Project: Sling
>          Issue Type: Task
>            Reporter: Chris Millar
>            Priority: Minor
>         Attachments: Sling - Page.png, Web 1920 – 1.png, browser-comparison.jpg
> As part of SLING-6666, it was mentioned the Sling website needs a re-design to help attract
new developers and make the site easier to use on mobile devices.
> Now that the site is on JBake, it probably makes sense to start working on this.
> The attached mockup is an initial take on the homepage. It's not meant to be all-encompassing,
but should provide a view into what the site could look like and how it could match the new
Sling Launchpad design.
> *Notes*
> * The image is pulled from Adobe Stock. Hopefully this can be donated, or we can pull
from the community to get an image we want to use. Was thinking "greenfield" and not overly
> * I was looking for something punchy for the title text. "Effortlessly build resource-driven
web-applications." is what I came up with.
> * About text has been un-touched.
> * Easy build instructions are right on the homepage. Docker first, with Java just a tab
click away. This follows Docker now being the priority on the getting started page.
> * News, Get Involved, and Additional Resource should be mostly self-explanatory.
> * The navigation is designed around the common areas of the current left hand rail, but
with tutorials being broken out. This is a result of the many devs I've on-boarded that prefer
walk-throughs over raw docs.
> Overall the idea is to give a single page of the main topics, but kick out to the pages
already established.
> Let me know your thoughts.

This message was sent by Atlassian JIRA

View raw message