Working with Google Docs

Google Docs can produce a good source document when headings, lists, links, tables, and images are created structurally.

Use paragraph styles

• Apply Title to the document title.
• Apply the appropriate Heading styles to sections and subsections.
• Keep heading levels logical; do not choose a level only because of its appearance.
• Use the document outline to confirm that the structure makes sense.

Use accessible document elements

• Use numbered and bulleted list controls.
• Use descriptive link text rather than click here.
• Use tables for data and include a heading row.
• Add and verify alternative text for informative images, drawings, charts, and graphics.
• Use words such as Important or Warning when meaning might otherwise depend only on color, bold, or highlighting.
• Prefer left-aligned text; avoid long passages of justified text.

Before copying from Google Docs

1. Confirm that the correct document and version are open.
2. Resolve comments and suggestions.
3. Remove drafting notes, placeholders, and print-only page elements.
4. Review the document outline and heading order.
5. Verify link text, table headers, lists, and image descriptions.
6. Make an approved copy or preserve version history according to district policy.

Google Docs does not replace publication review

Good structure in Google Docs improves the source, but copied content must still be inspected after it is placed in schoolboard.net.

Convert a Google Doc to Expandable HTML

For the standardized v1 AI-assisted workflow, finalize the Google Doc, download it as a PDF, and use the approved PDF as the input to Gemini. This preserves one approved comparison source and avoids granting the conversion process access to Google Drive.

Follow Appendix: Google Docs and PDF to Expandable HTML for preparation, download, prompting, human review, and placement in the Source editor.