Thank you so much, Kris! - Nina (the writer)

Nina, many thanks for your work on the documentation. I found it very useful. Just a few comments: Consider adopting a style guide and sticking to it. There are several

All page numbers shown are using the total pages, not the one at the bottom. ---------- pg 12 When using the menu>submenu>page section, it seems to me that an additional notation should be used. As

I'll second "adopt a style guide and stick to it." I also prefer the IBM guide, but following the guide consistently is much more important than the guide chosen. As much as you can, embody the style

Maybe this is my ignorance talking, but what style inconsistencies are there in the doc right now? Thanks, Mark

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

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

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

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

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

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

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 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

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

On Sat, Mar 14, 2020 at 11:07 AM, Mark Fletcher wrote: 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

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

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

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

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

On Tue, Mar 24, 2020 at 01:46 PM, Mark Fletcher wrote: At some point there will be a search feature.A future search feature seems redundant. When viewing HTML and also PDF (online) Ctrl/F give a