Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
documentation
Priority:
Minor
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
18 Sep 2015 at 15:36 UTC
Updated:
19 Oct 2015 at 02:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
ifrikComment #3
duaelfrComment #4
yoroy commented"Manage content types, including default status, front page promotion, comment settings, etc."
for Content types,
"Add new menus to your site, edit existing menus, and rename and reorganize menu links."
for menus,
could be made a bit more to the point.
"Configure what displays are available for your content and forms."
For Display modes is using the same words to explain which is not so helpful.
I don't see any big issues with the current state though.
Comment #5
Andrew Gleeson commentedI am currently working on this at Drupalcon Barcelona FIRST TIME sprint session
Comment #6
Andrew Gleeson commentedI am working alongside Mairi Fraser (mairi) who is doing the same for the below issue:
https://www.drupal.org/node/2570997
This is the contributor task that we *think* we're doing:
https://www.drupal.org/node/2276597
The attached file lists the *links.menu.yml files that need to be reviewed and updated where required, identified using the following command:
find . -name "*links.menu.yml" -print | xargs grep "parent: system.admin_structure" | awk -F: '{print $1}' | sort -u > 2570997-files_list.txt
All files listed are currently marked as TODO - We will update as DONE the ones that we get through today
Comment #7
Andrew Gleeson commentedThis patch attempts to address the first 2 points in #4.
It's not clear to me what needs done about the 3rd point, so I have not done anything there.
See files list attached with files which have been checked.
Comment #8
ifrikComment #9
ifrikThanks for the patch, but I suppose comment #4 meant to make the description text shorter, rather then adding more information to it.
The reference to "comment settings" is probably still left over from Drupal 7, but makes less sense now that comments are a field.
How about this:
Content types
Create content types and manage their default settings.Taxonomy
Configure vocabularies and taxonomy terms.That way site builders who have already come accross vocabularies in other parts of the site, recognize the link easier; rather then explaining what taxonomy is used for.
Comment #10
rajeevkDone as per suggestion in #10. Attaching patch & interdiff..
Comment #11
rajeevkComment #12
ifrikThanks RajeevK for the update of the patch.
It all looks good. The link descriptions are consistent and follow the same format. They are all a bit shorter then before, but still give the relevant information.
I think this is ready to go.
beta evaluation added
Comment #13
jhodgdonHm.
Manage menus and menu links for your site.
Do we really need "for your site" in there? Everything is for your site.
Also:
I actually thought that the previous description was useful, because maybe someone doesn't know what "vocabularies" or "taxonomy terms" are, but they probably know what tagging and categories and classification mean.
Comment #14
Bojhan commentedCan we please be careful that we are not removing months of hard work in the Drupal 7 cycle? We spend a lot of time on copywriting, I find the latest slew of issues often not taking that part of usability into account and very hard to review.
I agree wholeheartedly with jhodgdon here.
Comment #15
jhodgdonComment #16
rajeevkDone as per ongoing discussion.
Comment #17
ifrikThanks for the updated patch.
I thought using "vocabularies" here would be good, because the term comes up at other places, and users might look for that, but I also see the reasons for talking about classification etc.
Since this takes up the issues raised, I think it's ready to go.
Comment #18
jhodgdon+1, these two changes seem fine to me. Much more concise without losing information or readability.
Comment #19
Bojhan commentedGreat :)
Comment #21
jhodgdonTest bot failure.
Comment #22
xjmThanks everyone for your work on this issue.
I believe this was referring specifically to the changes for the Taxonomy help text, which I agree were problematic. I infer from @Bojhan's comment in #19 that the other two changes are okay in the current patch:
The extra words in this one didn't add any information, so I think this one is fine.
This one is losing examples of what those default settings might be. However, the comment settings actually aren't managed there anymore anyway, so the updated text is more accurate. So I think this one is still an improvement (again with the assumption that Bojhan signed off on it above).
So based on that assessment and the overall improvement, it seems to get this in before string freeze. Committed and pushed to 8.0.x. Thanks!