Themes page in About: Drupal Features needs content and screenshots
The new About page has a section called Drupal Features. The content that is or should be linked from each subsection doesn't currently exist.
The copy that appears in this section on the About page is open for improvement as well.
What you need to do:
*If you want to work on this, please assign this issue to yourself*
1. Gather and revise marketing copy for this section (in this case, 'Design and Display'), and the new Design and Display section itself, based on the content suggested on http://redesign.drupal.org/about
2. Follow the Editorial Guidelines
3. Gather screenshots (or ideas for screenshots, since they'll need to look consistent)
4. The community will review the copy for consistency and completeness
5. There are no rules yet about length but each page should probably have a least one paragraph per linked term on the About page.
**If you don't have edit access on d.o., lisarex can add the content for you on the live site. Content is updated automatically to the redesign site every 24 hours**
Live (but not linked from anywhere):
http://drupal.org/about/features/design
Redesign:
http://redesign.drupal.org/about/features/design
Editorial Guidelines:
https://infrastructure.drupal.org/drupal.org-style-guide/editorial.html
Comments
Comment #1
Content Shaman commentedComment #2
lisarex commentedMarking as critical.
Comment #3
alex ua commentedChanging the title to reflect the new About -> Drupal CMS Features category.
Please note: we need to change the urls to reflect this change.
Comment #4
alex ua commentedThe actual link is http://drupal.org/features/design. I'm removing the assignment to @content shamen, as I'm going to put some work into this page today.
Comment #5
lisarex commentedAssigning this to Diana
Comment #6
alex ua commentedI added this to the features page, however, I think we need something about design-and/or-display-oriented Views plugins there (Views Slideshow, Views Accordion, Semantic Views), and also maybe an example or two of jQuery/JavaScript modules that might help a designer (beautytips and vertical tabs for UX, modal dialogs and popups, calendar form popups, etc) .
Comment #7
lisarex commentedI've added Diana's content and marking as Needs Review
Comment #8
gdemetThis isn't too bad as-is, but all of the modules and themes referenced should have links to their project pages. I'd also like to see a paragraph talking about usability and accessibility, which are both very important part of the front-end user experience.
Comment #9
Everett Zufelt commentedtagging
Comment #10
diana.k commentedHi George,
When you mentioned a paragraph about usability and accessibility, do you mean a paragraph about how Drupal theming is already accessible to front-end users, or a paragraph speaking to designers about how they should make themes accessible to front-end users?
Comment #11
Everett Zufelt commentedDrupal's presentation layer allows designers to create highly usable, interactive experiences that engage users and increase traffic.
* usable, accessible, interactive
We have a page (under work) at http://drupal.org/about/accessibility some of which can inform the accessibility portion of this discussion.
Comment #12
alex ua commented@diana.k - for accessibility, I think we basically want to say:
Drupal strives to empower all site builders regardless of physical limitations (is 'disabilities' un-pc?), and 508 compliance (is this too American?) will always be a vital part of the project... We should also mention that Drupal core now has an official "Accesibilty Maintainer" (http://drupal.org/user/406552 - who just commented in #11 while I was writing this)
In regards to usability, we should talk about:
- the many usability studies that have been completed
- the many usability improvements to Drupal 7 (my recommendation would be to avoid talking about the overlay, which was meant as a usability improvement, but it's not at all clear that it has provided anything of value. Take with a grain of salt: I am biased)
- modules like Vertical Tabs, Better Formats, Admin Role, Admin Menu (others?)
- the "usability maintaner" for the project (http://drupal.org/user/87969)
Comment #13
Everett Zufelt commented@diana.k - for accessibility, I think we basically want to say:
Drupal strives to empower all site builders regardless of physical limitations (is 'disabilities' un-pc?), and 508 compliance (is this too American?) will always be a vital part of the project...
1. Some limitations are not physical, they can be perceptual, cognitive, etc. I think "all" is sufficient.
2. s. 508 is too american (and too federally american). The accessibility team has generally taken the stand that we should focus efforts on the international W3C accessibility guidelines (WCAG, ATAG, ARIA). Which go a long way to furthuring compliance with more specific regulations like s. 508.
We should also mention that Drupal core now has an official "Accesibilty Maintainer" (
http://drupal.org/user/406552
We actually have two accessibility maintainers in D7. Myself, and BrandonOJC (see maintainers.txt for D7 for his user id).
Comment #14
diana.k commentedThanks Alex and Everett. I added two paragraphs to the end of Design and Display based on your suggestions.
Comment #15
gdemetI'm not seeing anything about accessibility on http://drupal.org/features/design - where should I be reviewing this copy?
Comment #16
aschiwi commentedI added links to mentioned projects and changed a few bits here and there. Couldn't think of anything that could be used as screenshots though. Thought about color module but... meh. Thought about putting a few of the prettiest Drupal themes together but... meh.
What about mentioning HTML 5 though?
Comment #17
lisarex commented@gdemet - I've added the new copy now and have made a giant notice on the Google doc to not edit it anymore
@aschiwi Feel free to propose some HTML5 copy.
I could have some screenshots here but for now I think it would be fine to ship with this page as it is....downgrading to normal.
Comment #18
aschiwi commented@lisarex: Did some research - we probably shouldn't add the HTML 5 part yet. It's easy to build themes in HTML 5, but Drupal still adds some HTML (menus, $styles, $submitted etc.) that needs to be overridden. There are tools (HTML5 Tools, HTML5 Base) but they don't seem finished/stable yet.
I changed the link to Themes to not filter to just Drupal 7 themes. I think I had added that during our Drupal 7 sprint camp, I was surrounded by Drupal 7 and got confused - this is not a Drupal 7 specific handbook page though.
Other than that the page looks good to me, much easier to read now that it's divided by headlines.
Comment #19
lisarex commentedThere haven't been any additional comments in nearly 2 years, and we'll eventually revisit / update this section in #1832566: Revisit & improve the Features section of drupal.org