On #2757921: Import AsciiDoc HTML output into nodes, we are working on importing the User Guide into the Drupal.org documentation section. Hooray!
One of the things we need for the import to be successful, is for each chapter and topic in the Guide to have short summary added to it. On #2775503: Make a way to have summaries, this functionality was added to the AsciiDoc display module. Also, summaries were added to the contributor guide.
So, on this issue, what we need to do is add paragraphs like this to each topic:
[role="summary"]
What a reader of the User Guide should do to report a problem (file an issue).
For topics, the summaries should go after the ID and topic title lines, which look something like this:
[[topic-id-here]]
Title Of The Topic
And before the index lines, which look something like this:
(((Index entry,sub-entry)))
For chapters, they go into file guide.txt, between the chapter title:
[[id-of-chapter]]
== Title of the chapter
and the include declarations for the topics in the chapter:
include::copyright.txt[]
Some help on figuring out what to write for each topic can be found in the "Covers" column of the topic tracking spreadsheet for this project, which is at:
https://docs.google.com/spreadsheets/d/1ov0FyJhKrJe7PYvohzV5UrrLyRaVCy2A...
Comment | File | Size | Author |
---|---|---|---|
#34 | summaries_topics_batch5_v2-2775689_34.patch | 8.17 KB | jojyja |
#33 | summaries_topics_batch4-v2-2775689_31.patch | 6.38 KB | jojyja |
#30 | summaries_topics_batch5-2775689_30.patch | 8.66 KB | jojyja |
#29 | summaries_topics_batch4-2775689_29.patch | 6.37 KB | jojyja |
#28 | summaries_topics_batch3-2775689_28.patch | 7.51 KB | jojyja |
Comments
Comment #2
jhodgdonOh, I should mention that there are examples of what is needed in the "guidelines" directory in the project (the contributor guidelines book), because I recently edited the main guidelines.txt file for the chapters (which is like the guide.txt file for the main User Guide), as well as the individual topic files, to have summaries.
Comment #3
jhodgdonOne other note: I have just learned that the Summary lines must be no more than 140 characters long, for Drupal.org purposes. I will need to update 3 of the ones I made for the Contributor guide.
Comment #4
jojyja CreditAttribution: jojyja at Red Crackle commentedI'm taking this up!!! :)
Comment #5
jhodgdonI realized I need to provide a bit more information on how the summaries will be used.
So, basically, on drupal.org, the plan is to import the User Guide (and guidelines pages too) into the new structure for Documentation pages. In this structure, there is a content type called "Guide", which is basically a table of contents page, and another one called a "Page", which is where you put information.
The Index page for the user guide, as well as the chapter pages, will become "guides". These pages display the titles and summaries of the pages and guides they contain. So, each topic in the user guide and each chapter needs to have a 140-character summary.
I have already imported the Contributor Guidelines book (with the summaries I wrote) into a dev site for drupal.org. Here is what it looks like:
https://guide-drupal.dev.devdrupal.org/documentation/user_guide_contribu...
(htaccess login: drupal/drupal as usual on dev sites)
Then if you click through to a chapter, you get something like this:
https://guide-drupal.dev.devdrupal.org/documentation/user_guide_contribu...
That will give you an idea of what the summaries might look like.
So, let's look at an example from the User Guide itself. How about chapter 7 (managing user accounts) as an example?
We might have the following summaries:
- chapter: Overview of user account concepts and details of common user account tasks.
- user-concept topic: Overview of user accounts, permissions, and roles.
- user-new-role topic: How to create a new role.
...
So... I think we need to adopt a common format for the summaries. I propose:
- Task topics: Start with "How to [verb]..."
- Concept topics: Start with "Overview of..."
- Chapters: "Overview of [....] concepts and details of [....] tasks"
hm... or maybe "Overview of concepts and details of tasks related to [....]".
How does that sound?
Comment #6
jojyja CreditAttribution: jojyja at Red Crackle commentedThanks for the detailed update! I'm clear on this task now.
Comment #7
eojthebraveI like the idea of having a standard for writing these, and I'm totally fine with what Jennifer has proposed in comment #5. A quick scan makes me feel like that should apply pretty easily to all existing task/concept topics. And I guess if for any reason it doesn't we can address that on a case-by-case basis.
One thing that might be nice to keep in mind for people reading these summaries is to ask yourself the question, "Does this give me enough information to know if I can skip this page?" I should be able to get a pretty good sense of the content, and be able to decide if I'm pretty confident that I already know what I need to know about this topic. I think that that will help make the guide easier to scan, and thus more useful as a reference for people who are landing on these pages with a specific question vs. someone who intends to read from cover to cover.
@jojyja, thanks for taking this on! :)
Comment #8
jhodgdonOf course, there is only so much information we can put into 140 characters! That is a limitation of the design of the new Documentation Guide and Documentation Page content types on drupal.org -- the summary has that character limit.
Comment #9
jojyja CreditAttribution: jojyja at Red Crackle commentedThanks :). I will keep the reader's perspective in mind while adhering to the character count specified by Jennifer.
Comment #10
jhodgdonAlso, if you want to make an initial patch for just part of the summaries, instead of waiting until you've written all of them, that would be fine! :)
Comment #11
jojyja CreditAttribution: jojyja at Red Crackle commentedSure, here's the first patch. It features the summaries for the chapters.
Comment #12
jhodgdonThis looks great!
I think I would take out the word 'custom' here, because it also covers how to place blocks (which may not be "custom" blocks). Replace with "common".
The tasks here are not just translation, also setting up the site to be multilingual... maybe
...details of tasks needed to make a site multilingual.
So I made these two small changes and committed this patch.
Comment #14
jhodgdonAs a note: we need summaries added for the Preface and Appendix too if possible. They look at little bare at the moment on the dev site where I'm testing out the imports. ;)
Comment #15
jojyja CreditAttribution: jojyja at Red Crackle commentedSure, I will create summaries for them as well.
Comment #16
jojyja CreditAttribution: jojyja at Red Crackle commentedHere is the first batch of topic summaries.
Comment #17
jojyja CreditAttribution: jojyja at Red Crackle commentedHere is the second batch of topic summaries.
Comment #18
jojyja CreditAttribution: jojyja at Red Crackle commentedComment #19
jhodgdonThanks! It looks like the patch in #17 includes the patch in #16, so I just reviewed that one.
This looks mostly wonderful! A few small notes:
It's more of an overview of what regions are, in the context of themes?
needs copy edit. (creating -> create)
I think we shouldn't mention the home page specifically. The topic should be applicable to editing *any* content item.
I'm not sure about "update data" either?
needs copy edit (its -> their).
I'm not sure about "its different types" either?
So it's an overview of the concept of menus, and also what menus are automatically created with the Standard install profile.
Very nice! :)
is -> can be
(maybe?)
When I read this, I felt like it was saying that there was only 1 content entity type that would be used for all content. Maybe needs a slight rewording?
Hm. I think I would talk about good presentation rather than user-friendliness.
Hm. I am not sure about this one.
For one thing, it is only about the forms used to edit content.
For another thing, there are other changes you can make besides just changing widgets (like hiding some fields, and changing the order).
This sounds like I'm displaying multiple variations of the same image on the same page?
Maybe:
... to reformat an image
... to resize or otherwise alter an image
or something like that? We can probably lose "on a page" too.
needs copy edit (its -> their)
maybe "taxonomy vocabulary" would be clearer here? Also besides creating a vocabulary, this topic also covers adding it as a field to a content type.
Let's not use the word "post" here. "content" is preferred.
let's not be specific about "basic HTML". The steps could be used for any text format.
The other summaries used plurals, so should this be "view modes and field formatters"?
end in .
featured? Maybe "used" would be better, or "making up" or something like that?
needs copy edit (its -> their)
Not only contributors, but people who use the software, or modify it for their own purposes, need to follow and understand the license.
Let's not use acronyms in summaries without explaining them.
well it doesn't really tell you how to do anything. Maybe:
Overview of themes and where to obtain them.
Comment #20
jojyja CreditAttribution: jojyja at Red Crackle commentedThanks for the feedback! I'll work on these updates.
Comment #21
jojyja CreditAttribution: jojyja at Red Crackle commentedHi, here is the patch with the summaries featuring your feedback.
Comment #23
jhodgdonThis is great! Nearly perfect! I fixed a few very very very minor things:
- planning-structure - missing newline after the [role="summary"] line
- structure-text-format-config - some edits from your last patch were reverted. Put those back in.
- structure-widgets - misplaced .
Committed! Thanks!
I think this patch covered a bit over half of the guide, so setting the issue back to "Active" to get the rest done. Great work so far!
Comment #24
jhodgdon@jojyja - do you still plan to make summaries for the rest of the topics? This is a higher priority than the copy editing right now, if you have time... Thanks!
Comment #25
jojyja CreditAttribution: jojyja at Red Crackle commentedI have prepared the next batch of summaries. Having issues with the patch :)
Will share a nice patch soon :)
Comment #26
jojyja CreditAttribution: jojyja at Red Crackle commentedFinally, here is the patch! :)
And there is only one more set of summaries left.
Comment #27
jhodgdonThanks for the next batch! These look pretty good. I have a few suggestions:
This topic also covers which modules you need to install, and turning on the language switcher block, so maybe we should include that in the summary?
One of the main points of this topic is that it's not just content that is translatable ("content" has a particular meaning in the context of Drupal), and the topic covers how to translate content, configuration, and UI text.
Given that... how about:
Overview of translation on a site.
Well it's not just labels, and not all labels are configuration, so it doesn't cover how to translate all labels.
So... how about something like:
How to translate field labels in a view, and other configuration.
Maybe:
Overview of the User 1 account, also known as the root account or administrative account.
how about "...assign authorship of content items..."
I don't think I would call them "sections"... Maybe "the administrative parts of a view" or "what you can edit in a view" or something like that?
Comment #28
jojyja CreditAttribution: jojyja at Red Crackle commentedHere is a patch based on your feedback.
Comment #29
jojyja CreditAttribution: jojyja at Red Crackle commentedHere is a patch with the 4th batch of summaries. There are a few remaining - I'll share them in the last batch.
Comment #30
jojyja CreditAttribution: jojyja at Red Crackle commentedHere is the 5th and final batch of summaries.
Comment #31
jhodgdonWow, three patches, thanks!
The patch in #28 looks great, committed.
The other two look pretty good, but I think need a few updates before committing:
Review of batch 4, comment #29:
Maintenance mode, besides denying access, also puts up a message saying the site is undergoing maintenance. I think that is probably more appropriate to say than "denying access".
I think I would say "the cache" rather than "a cache"?
... of the cache ... ?
Review of batch 5, comment #30:
That is what the page *used* to contain. But now it just has information about some of the contributors. We recently moved the individual topic authors and editors to the topic files, so this file just has information about project management and people like you who did guide-wide editing and writing tasks.
I am not sure about "copyright perspective".
How about just:
Copyright information for this guide.
I don't actually think we can put a summary in the Glossary file. I may have told you we needed one, but ... glossaries have a very specific special format in AsciiDoc, and every time I've tried to add something to this file, it has broken the build. So, let's just leave it without a summary.
I think we'd better leave this out too. Indexes are also special.
Extra blank line in middle here.
Let's leave the word "Drupal" out, as we do throughout the guide.
Maybe "advanced site-building skills" would be good?
Comment #33
jojyja CreditAttribution: jojyja at Red Crackle commentedThank you for the feedback! Here is the updated patch for the 4th batch from #29.
Comment #34
jojyja CreditAttribution: jojyja at Red Crackle commentedHere is the updated patch for the 5th batch from #30.
Comment #35
jhodgdonThe patch in #5 had a couple of small glitches, which I fixed (like the cron summary getting into the cache topic, whoops!). Anyway, thanks! These look great. Committed. I think this issue is done but will need to verify by building/importing the site again, later today. Marking fixed; will reopen if necessary.
Comment #37
eojthebraveWoohoo! Thanks @jojyja and @jhodgdon for taking care of this. And so quickly. I'm impressed.
Comment #39
jhodgdonI imported this into the new dev site (a preview of how it will, hopefully very soon, look on Drupal.org)... looks great! See
https://guide-drupal.dev.devdrupal.org/docs/user_guide/en/index.html
(access: drupal/drupal as usual) The landing page shows the chapter summaries. Then click through to a chapter to see individual topic summaries.
I looked through all of the chapters, and the summaries are excellent -- thanks @jojyja!! I made a few very minor updates.
Anyway, this is looking very good! One step closer to having this live on drupal.org....