This issue is intended to capture feedback for the new design and content implemented on /download in #2987842: Improve clickpath for Downloading Drupal.

CommentFileSizeAuthor
#2 Download_Drupal___Drupal_org.png129.97 KBgrasmash
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

grasmash created an issue. See original summary.

grasmash’s picture

Feedback has been largely very positive. Two constructive pieces of feedback from twitter include:

  • Include a Composer command as a download alternative
  • Display the version number for the Drupal zip

Attaching a screenshot that would add the Composer command.

I've also changed the text in the bottom panes to "Demo Drupal" and "Getting Started" to more narrowly define the scope of the pane content.

drumm’s picture

Composer instructions should come with a link to Composer-related documentation.

svettes’s picture

Like the new format, just a few comments!
- It's definitely easier to get going. You have 2 clear paths: download & get started, or try out some hosting options. +1
- Get started link takes you to ch3.3 about installation, any reason we don't start them at the beginning? For example, someone might not know what "drush" is and this page references it w/o any preamble.
- Grey bkg could use a header of some kind, like "Learn more"
- Like the footer

hansfn’s picture

  1. The composer command in the screenshot is wrong - "some-dir" is missing. (You probably have spotted it already.)
  2. I think the "Demo Drupal" - the quick-start option - isn't visible enough. There is too much vertical space because of the Composer command and hosting information. Could we have three horizontal panes: "Demo Drupal" - "Install with composer" - "Drupal hosting" (like we currently have "Demo Drupal" and "Getting started")? "Getting started" could be alone below the 3 panes. Not sure before I have seen it.
gabesullice’s picture

This just tripped me up:

  1. I went to drupal.org/download
  2. I cmd+clicked the tarball link
  3. I chose "Copy link address"
  4. I ran curl -SO {link address}
  5. I ran tar -xvzf tar.gz (the resulting filename)
  6. Nothing happened

That's because the links lead to a 302 Redirect so curl didn't download anything.

Perhaps there can also be a copyable curl command with the -L option for CLI junkies like me.

That could eventually become the copyable composer command when the Drupal + Composer story is all buttoned up.

grasmash’s picture

Perhaps there can also be a copyable curl command with the -L option for CLI junkies like me.

This will be in both the Evaluator and Getting Started guides that we're working on publishing ASAP in #2996033: Set up feeds to import Official Docs .asciidoc files as Drupal.org nodes

Also see #2993155: Draft "Evaluator Guide" Outline & Guide, #2993153: Draft "Getting Started" Outline & Guide

rszrama’s picture

I have a few points of language / consistency feedback:

  1. You've pulled language from the homepage of Drupal and placed it here, "Drupal allows you to create a unique space in a world of cookie-cutter solutions." On this page, it appears to elevate it to some sort of tagline reminder at the point of download, when the tagline is actually the bit about being a platform (or open source CMS) for ambitious digital experiences. If there's to be any text between the title page and the primary action button, it should be instructions or descriptions of the options you're presenting. (e.g. "There are multiple ways to download and try Drupal, including... We recommend new users download the zip file and try it out first, but experienced PHP developers should consider the command line instructions below...")
  2. The call to action is "Download Drupal zip" with a secondary "download tar.gz". This isn't consistent with the calls to action on other download pages ("Download tar.gz" as a button and "Download zip" without Drupal in there.) Can we just use the same button format as a release node? e.g. https://www.drupal.org/project/commerce/releases/8.x-2.9
  3. Is there a reason we don't show the current version number here? That would be appropriate for the descriptive text between the page title and buttons, e.g. "The current version of Drupal is 8.6.0."
  4. "read release notes" is fairly context-less ... it could probably be retitled to indicate the version number and set expectations. (e.g. "read the 8.6.0 release notes")

That's all that comes to mind. Thanks for simplifying the page! It makes me wonder, too, if "Translations" doesn't need to be added to the "Download & Extend" menu in the footer.

dsnopek’s picture

When I first came to this page, my initial impression was, "Whoa, there's nothing here! How is this helpful?"

My brain was interpreting the grey rows (with super useful info like "Demo Drupal" and "Getting Started") as a footer, and I completely ignored them.

It wasn't until I re-read the blog post here and saw it specifically mention "Demo Drupal" and "Getting Started" and then went back and searched for that specific text, did I finally actually notice that it was there! It was kind of weird experience, actually, like suddenly seeing the sailboat in a magic eye picture. :-)

I'd recommend changing the visual style of those sections so they don't look like a footer. I don't consciously ignore footers, but I guess years of internet usage have caused my brain to develop some kind of "not-my-problem field" where I don't consider them actually useful content. I suspect I'm not alone in this.

Andrej Galuf’s picture

In addition to #8, two things are missing imo:

  1. Composer create-project
  2. docker container

If I want to evaluate a project in this day and age, I won't bother with zips and tarballs. I'll spin up a container image and composer-install whatever I want.

hansfn’s picture

The screenshot in comment 2 should probably be moved to the issue summary ;-) composer create-project is there already.

A standard Drupal container is discussed in some other issue and might be listed here when settled.

gabesullice’s picture

My brain was interpreting the grey rows (with super useful info like "Demo Drupal" and "Getting Started") as a footer, and I completely ignored them.

+1

I only just saw them after reading your comment and going back to look again.

thamas’s picture

If I see "Try a hosted demo" on a button I think I'll be guided to a demo installation of Drupal, or a page where I can find the username / password to log in and a link to a demo installation.

But if I'm guided to a page instead where I find info about hosting providers who "can help you try a demo installation of Drupal in 20 minutes" then I feel fooled and I think the button was a lie…

Wim Leers’s picture

Looking at the screenshot in #2, my suggestions would be:

  1. Remove download tar.gz. Anybody who knows what that is, and how to extract it, also knows how to extract a zip. It's unnecessary noise. (Same goes for every project page btw, for example https://www.drupal.org/project/cdn.)
  2. Put downloading first (whether via ZIP or composer)
  3. Then list release notes.
  4. Release notes are long and tedious and very detailed. Perhaps it's worth automatically linking to the last new big release (latest minor), because that's when the new stuff was announced. Bonus points if we also automatically say "the next big exciting release is in X months". Because that gives newcomers a sense of pace, progress, excitement. The dates are in https://www.drupal.org/core/release-cycle-overview.
  5. The entire gray bar at the bottom is automatically ignored by my brain (much like #9 and #12 said).
  6. This suggests there's too much on this page. There's basically 4 things: download, demo, get started and … hosting. I think there could be a clearer visual flow to this. From top to bottom, it should IMHO be:
    1. "TRY IT NOW": Live demo. Embedded in an iframe. Click a button to make it full screen. The key thing is that it's literally only a single click away
    2. "GET IT NOW": download Drupal, either as a zip or through composer.
    3. "MAKE IT YOURS": the current getting started stuff
    4. "SHIP IT": the hosting stuff

    Make a clear visual vertical hierarchy. Make every bit of information displayed count. Anybody who's been through one of the previous steps will automatically skip it, simply by scrolling further downwards. Hell, even I would find that page useful!