Closed (fixed)
Project:
Documentation
Component:
Correction/Clarification
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
5 Feb 2012 at 21:01 UTC
Updated:
13 Mar 2012 at 15:30 UTC
The /support page is a locked page. It probably doesn't need to be unlocked, but we need a place to put changes. An issue existed #314325: Redesign the support page that involved redesigning, but that one is old and closed. This is for new changes. I discussed with lisarex adding descriptions to the different links to clarify the different areas of support, and probably removing the link to that issue at the bottom.
Comments
Comment #1
davidhernandezGet help with Drupal software
Comment #2
silverwing commented"Documentation" needs to be "Community Documentation"
"Professional support and services" - might include Hosting in the description
Comment #3
lisarex commentedAgree w/ silverwing's comments.
For Documentation, I'd say "written and maintained"
For Forums, I'd rephrase "Contributing knowledge in the forums is a great way to help others."
For IRC, I would also link the Do's and Don'ts page. /node/1259224
If these are cool, I'll add them to the Support page.
Comment #4
lisarex commentedAlso, some suggestions for Get help with Drupal.org websites section
Learn more about Drupal.org
How Drupal.org is built and maintained, and ways you can contribute.
Report spam
Found a spammy comment or posting? Report an issue, so someone from the webmasters team can remove it.
Report a site content issue
Is page content missing or confusing? Feel free to edit the content yourself, or post an issue to the Documentation queue if you need help with it.
Report a site functionality issue
For problems with Drupal.org that doesn't fit into the above categories.
Comment #5
davidhernandez> "Documentation" needs to be "Community Documentation"
yes
> "Professional support and services" - might include Hosting in the description
"Professional support, services, and hosting"?
> For Documentation, I'd say "written and maintained"
yes
> For Forums, I'd rephrase "Contributing knowledge in the forums is a great way to help others."
I think I copied that verbatim from the forum main page, so probably change it there, too? For consistency.
> For IRC, I would also link the Do's and Don'ts page. /node/1259224
I don't disagree, but the Do's and Don'ts page doesn't have intro text. I'd be concerned about people new to IRC not understanding.
Comment #6
silverwing commentedRE: Hosting - I think it should be in the description, not the title. "Services" covers hosting there. Otherwise, for consistency, we'd need to give it it's own entry (like Training has.)
RE: Forums - I don't like the term "knowledge bank"
RE: IRC - "Do's and Don't" doesn't fit with the page.
Comment #7
jhodgdonI keep wondering why we have both http://drupal.org/support (which I don't see linked anywhere in the top or bottom nav on d.o) and http://drupal.org/community (whose link in the d.o header says "Community and Support").
How about if we just get rid of /support and redirect it to /community? (and maybe re-alias that page community-support with another redirect, and actually name it Community and Support)?
Then we could discuss a redesign of that page... It just seems like the /support page is a relic, if we aren't going to have a link to it from anywhere.
Comment #8
jhodgdonNo, I'm wrong. In the d.o footer, there is a link whose title is "Need help?" in the Community and Support column, which goes to /support... Still... If you actually need support and click Community and Support in the header, you get to the /community page, which is not obviously about support at first glance.
Comment #9
davidhernandezYeah, we discussed these issues. Lisa had a fun little UX experiment watching me struggle to find where the help link was. It goes back to the idea of splitting the Community & Support link in the top nav to separate the two areas. That is a bigger issue, for sure. The average new user is probably looking for documentation, forums, and professional services, and is probably not interested in irc and meetups. (regarding support) The way it currently is, the priority seems to be Community over Support, when most people might prefer it the other way around. If you actually read the way the current Community & Support page is written, the help aspect is lacking for a newbie.
Comment #10
juan_g commentedThat's for example the issue #1242094: Restore "Support" in header navigation.
There is also the community initiative Community/Support/Getting-involved Landing pages.
Comment #11
arianek commented"Not only are they a great way to get fast, effective support, but they allow users to learn more and to get involved." under IRC - the first time I read that wrong as "Not a great way to get fast effective support, but..."
Maybe get rid of the negative at the start just incase others do the same? Instead, "A great way to get fast, effective support, as well as learn more and get involved."
Comment #12
lisarex commentedFYI I've submitted a patch to fix the primary nav and footer support issues: #1242094: Restore "Support" in header navigation
In the meantime, I'm rolling in these content updates: http://drupal.org/support
Better for sure, and I linked to the hosting page (ad revenue to support d.o.!) ... any more suggestions?
Comment #13
arianek commentedIt looks good but... "Get help with Drupal.org websites" should probably be "Get help with Drupal.org", it's really confusing (if that's what it's supposed to be about, which it looks like it is from the categories below). ;)
Comment #14
jhodgdonThe new support page looks pretty good!
I have a couple of thoughts:
a) Get help with Drupal software section...
It is all over the map in terms of writing style. I think it would be easier to scan if it used a more parallel construction for the descriptions. Would it be OK if I did some copy editing, or do you want to discuss the planned edits here first?
b) More support options section...
This section doesn't make much sense to me. Reporting security problems is not really a support activity, is it? Maybe we could remove that item, and move the "localized communities" item into the main "Get help with Drupal software" section?
c) Agree with #13.
d) The item "Report a problem with content"... I really don't want to encourage people to file issues in the Documentation project for content issues. I think they're likely to click that link before they read the description. So maybe we could make that into a header, and put the issue link into the text? Something like:
Site content issues
Is page content missing or confusing? Log in and edit the content yourself, add a comment to the page, or as a last resort (link)post an issue to the Documentation queue(endlink).
Comment #15
jhodgdonlisarex pinged me in IRC and suggested I go ahead and make the edits in #14, so I did.
http://drupal.org/support
Comment #16
arianek commentedMade a few more minor tweaks http://drupal.org/node/5/revisions/view/1916932/1916964 this looks good to me otherwise...
Comment #17
jhodgdon+1 on those changes. Yeah team editing! :)
Comment #18
davidhernandezhooray for teamwork.
Comment #19
jhodgdonI think I'll venture to mark this "fixed" at this point. Of course, if you disagree, feel free to mark back to another status.