aod-docs-and-writing

To write consistent Markdown documentation, apply standardized style conventions for syntax, tables, and diagrams to ensure uniform structure across README files and docstrings. This process enforces specific formatting rules to maintain project documentation quality and readability.

Style guidelines for code documentation and docstrings require adherence to specified house style conventions covering Markdown syntax, content structure, and formatting. Following these defined rules ensures your project documentation maintains consistency and quality across all written materials.

Structuring a README file for an Area Occupancy Detection project involves applying predefined documentation management guidelines to organize content, features, and Markdown formatting. This approach ensures the resulting documentation follows established house style and content structure conventions.

Standard Markdown formatting for tables and diagrams is supported when it aligns with the defined house style conventions. The documentation management process specifies exact syntax and formatting rules to ensure tables and diagrams maintain consistency across the project.

The best way to update project documentation when adding a new feature is to apply the established style conventions to the new content. This documentation management process ensures new feature descriptions integrate seamlessly with existing Markdown formatting and content structure guidelines.

You should not use automated documentation style guidelines when writing content that falls outside the scope of project documentation, README files, or docstrings. These style conventions are specifically tailored for the Area Occupancy Detection project and may not apply to external documentation formats.