Date   

Re: Feedback about documentation: Kudos!

Nina E
 

Thank you so much, Kris!

- Nina (the writer)


Re: Glossary?

Nina E
 

Hi, Bill. As I mentioned in another post, I'm using Google Docs to write the Groups.io documentation. I put the glossary in a document of its own to avoid duplicating it in both the owners/moderators reference doc and the members/reference doc, but then I discovered that linking between Google Docs is...less than ideal. :-(  Rest assured that Google Docs will NOT be the final repository for the official Groups.io documentation. Mark and I (but mostly Mark :-) ) will work on how best to publish the documentation in PDF and online/HTML form such that the links will work.

I'm using the current Groups.io help as well as a lot of info from GMF (especially the wiki) and Beta as resources for the content in the documentation, so you will see some duplication for a while. By the way, huge thanks to all of you who have contributed to those resources over the years!

- Nina


Re: The description of Time/Date controls in Default Sub Settings is wrong

Nina E
 

Thanks, Shal! Mark and I are working on clarifying that settings page and correcting the information in the documentation.

- Nina


Re: Overall style points

Nina E
 

Hi, all. I'm the writer working on the Groups.io documentation. Thank you for the comments on the owner/moderator reference doc so far!

To address some of the points that Shal raised:

1) How about Title Case for section titles? I think that would help them stand out in the document body.

I used sentence case from force of habit because that was the standard in my last tech writing/editing job. :-) That said, because many headings contain proper nouns (names of web pages, menu items, fields, and so on), I think sentence case helps those proper nouns stand out in the headings. Also, numbering will help the headings stand out (see the next item).

2) How about section numbers?

I agree that heading numbers will help in the printed/PDF version. (I'm not convinced that heading numbers are terribly useful in online presentation, but we'll see how it goes.) I didn't include them initially because I'm writing the documentation in Google Docs (that's the approach Mark and I agreed on when I first contacted him), and Google Docs doesn't have a heading numbering feature built in. However, I recently found an add-on that does the trick, so I'll try that in the next draft.

4) PDF Bookmarks, please!

As I mentioned above, I'm currently using Google Docs, but I'm not very familiar with its export-to-PDF capabilities. Maybe there's an add-on that will add bookmarks to PDF files; I'll look around. (If anyone happens to know of such a Google Docs add-on, please let me know.)

5) For the PDF pay attention to page breaks.

For sure. I'm waiting until the final draft, so I don't have to redo too many. :-)

6) For the PDF consider using a new page for selected headings. All Heading 1 likely, and maybe all of Heading 2 as well.

Good suggestion - I'll give it a try.

Thank you again!

Regards,
Nina

P.S. For the record, I own/moderate a restricted Premium group for a chorus of which I'm a member, and I serve as secretary on its board. We transferred our group from Yahoo Groups to Groups.io two years ago this February, and we couldn't be happier that we did so!


Re: manual v1 Group Email Address error

 

On Sun, Mar 8, 2020 at 11:28 AM Duane <txpigeon@...> wrote:
On Sun, Mar 8, 2020 at 11:57 AM, Nina E wrote:
I asked Mark about the character limit for the group email address, and he told me 34. :-)
Thank you.  I can't believe Mark made that mistake over 2 years ago and no one caught it. ;>)  I did a quick test and verified that 34 is correct.

Duane, I've been making mistakes for much longer than two years. :-)


Mark 


Re: Overall style points

Mark Murphy
 

I agree with section numbering in the main body and TOC, preferably in an outline format like:


Re: manual v1 Group Email Address error

Duane
 

On Sun, Mar 8, 2020 at 11:57 AM, Nina E wrote:
I asked Mark about the character limit for the group email address, and he told me 34. :-)
Thank you.  I can't believe Mark made that mistake over 2 years ago and no one caught it. ;>)  I did a quick test and verified that 34 is correct.

Duane


Re: manual v1 Group Email Address error

Nina E
 

Hi, Duane. I asked Mark about the character limit for the group email address, and he told me 34. :-)

- Nina (the writer)


Re: Overall style points

Bill Hazel
 

On Sat, Mar 7, 2020 at 10:10 PM, Shal Farley wrote:
Perhaps like a Wiki of its own, but with only Groups.io having edit permission.
I like this idea. Then it is easy to search and to link to from other groups.io. I really like linking to the source vs copies of it.
An advantage of the wiki is that all the currently linked to material (see would have their own wikipage to link to.
Also, instead of dealing with multiple static copies we would always be looking at a dynamic current version.

Bill


Overall style points

 

Mark,

1) How about Title Case for section titles? I think that would help them stand out in the document body.

2) How about section numbers? In both the TOC and the body. Though they might be subject to change with each major revision I think they will help in citations to the manual. In the HTML version maybe supplement that with hover permalinks similar to those in the Help page - but keep them the same as the TOC links (if practical) and as short as practical, even when on a Header 2 or Header 3.

3) Will this be all one big HTML page? I'm a little ambivalent. That does enable browser-based search, but it seems like it could be a bit much. I think I'd prefer it broken into chapters (or smaller) with a dedicated search. Perhaps like a Wiki of its own, but with only Groups.io having edit permission.

4) PDF Bookmarks, please! I don't know what tool Nina is using, but hopefully its export to PDF function can be coerced to emit bookmarks. In MS Word that's in an option pop-up you open from the File dialog when you Export. In Acrobat Reader these Bookmars show up as a sidebar on the left with clickable links to go directly to headings.

5) For the PDF pay attention to page breaks. This goes beyond simple orphan/widow control in paragraphs (which seems to be mostly under control); there needs to be more use of Keep With Next (or whatever it is called in Nina's authoring tool) to avoid having headings orphaned at the bottom of a page; examples on pages: 12, 13, 15, 24, 26, 45, 52, and 73. Or widows at the top of a page; examples: 4, 7, 11, 12, 20, 54, 66, 69, and 71.

6) For the PDF consider using a new page for selected headings. All Heading 1 likely, and maybe all of Heading 2 as well.

Shal


The description of Time/Date controls in Default Sub Settings is wrong

 

Mark,

In "Setting default subscription options for group members", p 18-20, each of Timezones, Time Display, Date Display and Monday Start ends with the note:
Note: A change to this setting applies only to new members of the group; a change here does not affect existing members.
That text actually applies to all of the other settings on this tab of the Settings page, not to those. This note should be placed prominantly at the beginning of the section, not duplicated for each of the non-time settings.

Timezones, Time Display, Date Display and Monday Start apply only to new Users of Groups.io - people whose email address, prior to joining this particular group, had not joined another group or had otherwise set those controls in their Account settings.

The placement of these settings was topic #71740860 recently in Beta, and their exact operation has been a FAQ in GMF for some time.

Shal
(And yet, somehow, I'm not finding it in our Wiki. Gotta go fix that.)


Re: Owners and Moderators Reference - Review Comments

 

Andy,

* Also on p22, the bullet point spacing for the notes in the Message
Footer section are not consistent with those on the previous and
following pages
That one I count as a good thing. In a way it is a different kind of list as its elements are short phrases, not paragraphs. There are more examples of this sort of thing.

BTW, it took me a while to figure out the Adobe page numbers (I was reviewing a printed copy). They are ten higher the document page numbers owing to the TOC and other content prior to page 1.

Shal


Re: Owners and Moderators Reference - Review Comments

Andy Wedge
 

On Sat, Mar 7, 2020 at 05:00 PM, Bill Hazel wrote:
I only noticed the Glossary file link mentioned in my post.
There are quite a few on p17 (Adobe reader page number) under the Member Directory Visibility heading and others through the document.

I understand that these files might not be ready for prime-time but if not, maybe they should all be uploaded to the files section here and linked to. If they also need possible tweaking you already have volunteers - anyone part of this group - who have already signed up.
Yes, a good idea.

Andy


Re: Owners and Moderators Reference - Review Comments

Bill Hazel
 

On Fri, Mar 6, 2020 at 10:32 PM, Andy Wedge wrote:
There are lots of hyperlinks that point to a Google Drive account. Is it really the intention to force readers to use a cloud storage solution to get extra info?
I only noticed the Glossary file link mentioned in my post.
I understand that these files might not be ready for prime-time but if not, maybe they should all be uploaded to the files section here and linked to. If they also need possible tweaking you already have volunteers - anyone part of this group - who have already signed up.

Bill


Feedback about documentation: Kudos!

Kristen James Eberlein
 

Kudos! I gave it a quick look, and then immediately used it perform some tasks -- merging and splitting topics -- that I had not quite been comfortable with. The documentation gave me all the information that I needed.

Kris


Re: Owners and Moderators Reference - Review Comments

Andy Wedge
 

In addition:

  • At the top of p22 (Adobe reader page number) - the text Viewing and managing your group’s storage space is underlined and coloured as though it's a link but it doesn't point anywhere
  • Also on p22, the bullet point spacing for the notes in the Message Footer section are not consistent with those on the previous and following pages
Andy


Glossary?

Bill Hazel
 

According to the PDF on page 2, we are directed to "See the Groups.io Glossary for a list of common terms used in Groups.io and their definitions." but to actually view it requires access to a Google Docs account.

It would seem that this should be readily available to every member of Groups.io.

I looked at the beta wiki and the "Help" at the top of the page, the 2 places I would most expect to find it (I also looked at the Groups.io webpage but it didn't have a wiki) I also checked GMF wiki with zero result but that isn't "Official" anyway.

Is the Glossary the same as Definitions on the "help" page? If so, one of the titles could be changed so the same thing is always called the same thing - a wayfinding technique I learned over 10 years ago at Boeing.

Bill


Owners and Moderators Reference - Review Comments

Andy Wedge
 

Hi Mark,

on my first quick scan I can see:

  • There are lots of hyperlinks that point to a Google Drive account. Is it really the intention to force readers to use a cloud storage solution to get extra info?
  • On p12 (Adobe reader page number) - remove mailto: link from +owner example
  • The limited number of graphics look fuzzy. For more visually oriented people, more higher resolution graphics would help.

Regards,
Andy


Re: manual v1 Group Email Address error

 

On Fri, Mar 6, 2020 at 5:20 PM Duane <txpigeon@...> wrote:

Quick question while I'm here.  Should we report one item per post or is a list acceptable?  I'm not expecting too many errors though! ;>)


I think a list would be fine.

Thanks,
Mark 


manual v1 Group Email Address error

Duane
 

I haven't had a chance to read much yet, but noticed that on page 2, under Creating a Basic Group, item 5, it says the length of the Group Email Address can be 34 characters.  Per https://beta.groups.io/g/main/message/16085 I think that should be 32 characters.

Quick question while I'm here.  Should we report one item per post or is a list acceptable?  I'm not expecting too many errors though! ;>)

I'll probably get to the rest of it in the morning.

Thanks,
Duane

361 - 380 of 381