Hi All, I've updated the help center. It now has the completed Owners Manual, as well as the FAQ and the very much still work in progress Members Manual. Thanks, Mark

The new help center looks good. As helpful as a help center should be. Clear and straightforward. Well organized. Notes: Liked the glossary tool tips. "Settings for Groups.io features" section:

Even though some of the items are just placeholders promising content yet to come, the new Help Center represents a quantum leap forward. Up till now there have been various

Speaking with my user hat on (rather than my tech writer hat :-) ), a search feature that's available throughout the help center would (I hope) provide search results in context—similar to wiki

Hello, Thanks for the suggestions for improvements of the PDF versions of the manuals. I've made the following changes to the PDF version of the Owners Manual: - There are now page breaks before each

A future search feature seems redundant. When viewing HTML and also PDF (online) Ctrl/F give a fairly easy to use and comprehensive search facility. -- Bob Bellizzi

This is such a useful document and I know a great deal of work has gone into it. I hesitate to ask for more, however... I have some suggestions. 1. Section 26.3 Bounce, bouncing Consider also

Hi All, I've put up an alpha version of the new help center, here: https://groups.io/helpcenter It contains a link to the most recent version of the Owners Manual (the other manuals are not yet

I don't understand your suggestions. I see no need for the blurb. The questions you asked are answered elsewhere and the document is correct as is. BTW, the answers are No and Yes. Duane

Page 5 - Group Title Add blurb that the Group Title may include spaces, plus signs, slashes, periods, and underscores (if true)Page 10 - Messages Messages from members can only be tagged with

Since you're comfortable with that term, and have used it as a reference here, I think it should be used in the documentation as well. As I mentioned on the GMF group, "section" didn't seem quite

If Nina selects a style guide, it will outline the terminology to use for UI components. Best, Kris

I used the term panel because that's what those things are called in the web framework that I use to build the site (called Bootstrap). I personally have no opinion on what they should be called in

Based on an almost minor comment that Mark made, I think the entire document should be edited so that references to a "section" of a page, such as "The page contains sections for these categories of

I did not see style inconsistencies. I suggested a style guide because it can be useful in the following ways: Authors can follow the rules that the style guide lays out, rather

Thank you, Shal! I appreciate your taking time to review the document and welcome your comments whenever you have a chance. Best, Nina

Nina, My apologies. I didn't mean to imply that you didn't. Ok, that's good to know. I was concerned that it did not have that capability. I guess I over-interpreted what you meant by having to

I'm fully aware of best practices for page breaks, and yes, Google Docs does have "keep lines together" and "keep with next" options, which I am applying as needed. But getting the content written and

Mark, I haven't really paid attention to that, but Nina's earlier reply to me made me wince: It implies to me manual insertion of page breaks, and that never ends well. I don't know what formatting

Marv wrote: I'll agree for the online (HTML) document; some form of permalinks to the headings would be ideal for citation. For the PDF, which one might print, a human-readable heading identifier