adev-writing-guide

From README

Angular Documentation (adev) Writing Guide This skill provides comprehensive guidelines for authoring content in adev/src/content. It combines Google's technical writing standards with Angular-specific markdown conventions, components, and best practices. I. Google Technical Writing Guidelines Tone and Content Be conversational and friendly: Maintain a helpful yet professional tone. Avoid being overly casual. Write accessibly: Ensure documentation is understandable to a diverse global audience, including non-native English speakers. Audience-first: Focus on what the user needs to do, not just what the system does. Avoid pre-announcing: Do not mention unreleased features or make unsupported claims. Use descriptive link text: Link text should clearly indicate the destination (e.g., avoid "click here"). Language and Grammar Use second person ("you"): Address the reader directly.