[
https://issues.apache.org/jira/browse/SLING-7242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482074#comment-16482074
]
Chris Millar commented on SLING-7242:
-------------------------------------
I put the documentation page design mostly to HTML to see what it would look
like and I made a bunch of tweaks to the PNG that's above. The code blocks have
much less contrast, and the header design is going to be slightly different.
Here's a sample HTML:
https://auniverseaway.github.io/sling-site-demo/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html
> [Shiny] Sling Website Design
> ----------------------------
>
> Key: SLING-7242
> URL: https://issues.apache.org/jira/browse/SLING-7242
> 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 distracting.
> * 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
(v7.6.3#76005)
