update contributing.md and add issue and pr templates

Author: evzzk

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,26 @@
+---
+name: 📚 Documentation Bug Report
+about: Report an issue with the AWS CDK documentation
+title: "[Documentation Bug]: "
+labels: bug
+assignees: ''
+
+---
+
+### Documentation Page
+<!-- Add a link to the affected documentation page -->
+
+### Issue Description
+<!-- Clearly describe what's incorrect, unclear, or missing in the documentation -->
+
+### Expected Information
+<!-- Describe what you expected to find or how you expected the documentation to be structured -->
+
+### Screenshots
+<!-- If applicable, add screenshots to help explain the issue -->
+
+### Suggested Fix
+<!-- If you have a specific suggestion for how to fix the issue, please describe it here -->
+
+### Additional Context
+<!-- Add any other context about the problem here -->

.github/ISSUE_TEMPLATE/improvement_request.md

@@ -0,0 +1,26 @@
+---
+name: 📝 Documentation Improvement Request
+about: Suggest an improvement or addition to the AWS CDK documentation
+title: "[Documentation Improvement]: "
+labels: improvement
+assignees: ''
+
+---
+
+### Documentation Area
+<!-- Describe which part of the documentation needs enhancement (e.g., specific guide, section, or topic) -->
+
+### Enhancement Description
+<!-- Clearly describe what you'd like to see added or improved in the documentation -->
+
+### Why is this enhancement needed?
+<!-- Explain why this enhancement would be valuable for users of the AWS CDK -->
+
+### Proposed Content
+<!-- If you have specific content suggestions, please outline them here -->
+
+### Examples
+<!-- If applicable, add examples, code snippets, or references to other documentation that could help -->
+
+### Additional Context
+<!-- Add any other context about the request here -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,34 @@
+## Description
+
+**Documentation Change Type:**
+
+- [ ] Typo/grammar fix
+- [ ] Clarification or minor improvement
+- [ ] New example or code snippet
+- [ ] New section or topic
+- [ ] Major restructuring or enhancement
+
+**Affected Documentation Page(s):**
+<!-- Add links to the affected pages -->
+
+## Description of Changes
+<!-- Provide a clear and concise description of your changes -->
+
+## Motivation and Context
+<!-- Why are these changes required? What problem do they solve? -->
+
+## How Has This Been Validated?
+<!-- Have you previewed the changes locally using asciidoctor or GitHub's preview functionality? -->
+
+## Screenshots (if appropriate)
+<!-- Include screenshots of the documentation before and after your changes -->
+
+## Checklist
+
+- [ ] My changes follow the [AsciiDoc syntax](./CONTRIBUTING.md#asciidoc-syntax-reference) guidelines
+- [ ] I have previewed my changes using GitHub's preview or a local AsciiDoc renderer
+- [ ] My changes maintain consistent formatting with the rest of the documentation
+- [ ] I have checked that all links work correctly
+
+## Additional Information
+<!-- Any additional information or context that might be helpful for reviewers -->

CONTRIBUTING.md

@@ -60,6 +60,11 @@ We recommend creating or finding an issue first for:
 - Significant reorganization of existing content.
 - Any change that might benefit from discussion before implementation.
 
+When creating a new issue, you'll find these templates to help structure your feedback:
+
+- **Documentation Bug Report**: Use this template to report incorrect, unclear, or missing information.
+- **Documentation Improvement Request**: Use this template to suggest new content or enhancements.
+
 For simple changes like typos, grammatical errors, or minor clarifications, you can directly submit a pull request without an issue.
 
 ## Getting started
@@ -136,6 +141,8 @@ When making changes to the documentation:
 
 ### Pull Request review process
 
+When you create a pull request, a template will automatically be loaded with sections to help you provide all the necessary information about your changes. Fill out all relevant sections to help reviewers understand your contribution.
+
 After submitting your PR:
 
 1. Maintainers will review your changes.