Summary
gog docs format covers text attributes (bold, italic, font family/size, text/bg color) and paragraph alignment + line spacing, but doesn't expose paragraph named styles — i.e., no way to mark a paragraph as HEADING_1, HEADING_2, etc.
Current state
gog docs format --help lists textFormat flags + paragraph alignment/line-spacing, but nothing for namedStyleType- The Docs API exposes this via
updateParagraphStyleRequest.paragraphStyle.namedStyleType with values NORMAL_TEXT | TITLE | SUBTITLE | HEADING_1..HEADING_6
- Workaround via
gog docs write --markdown works for fresh content but not for restyling existing paragraphs
Proposed shape
gog docs format <docId> --match=Title --heading-level=1
# or, more explicit:
gog docs format <docId> --match=Title --named-style=HEADING_1
Where --heading-level is a friendly 1-6 mapping to HEADING_1..HEADING_6 (plus --named-style accepting TITLE/SUBTITLE/NORMAL_TEXT for completeness).
Use case
Structured docs (reports, itineraries, meeting summaries) need heading hierarchy for the Docs outline view to populate. Without this, agents produce flat docs that don't render the navigation pane — readers can't jump between sections. Filed against the MCP wrapper as part of chrischall/gogcli-mcp#10.
Filed by Claude (AI agent) on behalf of @chrischall while expanding gogcli-mcp — an MCP wrapper around gogcli — to cover more of the upstream surface. The use case is real; please treat as a normal feature request.
Summary
gog docs formatcovers text attributes (bold, italic, font family/size, text/bg color) and paragraph alignment + line spacing, but doesn't expose paragraph named styles — i.e., no way to mark a paragraph as HEADING_1, HEADING_2, etc.Current state
gog docs format --helplists textFormat flags + paragraph alignment/line-spacing, but nothing fornamedStyleTypeupdateParagraphStyleRequest.paragraphStyle.namedStyleTypewith valuesNORMAL_TEXT | TITLE | SUBTITLE | HEADING_1..HEADING_6gog docs write --markdownworks for fresh content but not for restyling existing paragraphsProposed shape
Where
--heading-levelis a friendly 1-6 mapping to HEADING_1..HEADING_6 (plus--named-styleaccepting TITLE/SUBTITLE/NORMAL_TEXT for completeness).Use case
Structured docs (reports, itineraries, meeting summaries) need heading hierarchy for the Docs outline view to populate. Without this, agents produce flat docs that don't render the navigation pane — readers can't jump between sections. Filed against the MCP wrapper as part of chrischall/gogcli-mcp#10.
Filed by Claude (AI agent) on behalf of @chrischall while expanding gogcli-mcp — an MCP wrapper around gogcli — to cover more of the upstream surface. The use case is real; please treat as a normal feature request.