feat: Update ROADMAP with personal data handling and user moderation features

- Added goals for defining personal data categories and retention obligations.
- Included exit criteria for user-level moderation, personal collections, and self-service data export.
- Expanded Phase 2 goals to include remote actor moderation and shareable block lists.

chore: Update flake.nix to specify main program

- Set the main program for the project in the flake configuration.

feat: Add issue templates for bug reports, feature requests, and questions

- Created structured templates to streamline issue reporting and feature suggestions.

docs: Add pull request template for consistent contributions

- Introduced a PR template to guide contributors on providing necessary information.

docs: Establish a Code of Conduct for community behavior

- Implemented a Code of Conduct to promote a respectful and inclusive environment.

docs: Create Diversity, Equity, and Inclusion (DEI) statement

- Outlined commitment to diversity and inclusion within the FeDIY community.

docs: Define Code Review Guidelines for constructive feedback

- Established guidelines to ensure respectful and effective code reviews.

docs: Implement Security Policy for vulnerability reporting

- Created a security policy detailing how to report vulnerabilities and our commitment to addressing them.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,58 @@
+---
+name: Bug Report
+about: Report something that isn't working
+title: "[BUG] "
+labels: bug
+assignees: ''
+
+---
+
+## Describe the Bug
+
+A clear and concise description of what the bug is.
+
+## Steps to Reproduce
+
+Steps to reproduce the behavior:
+
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+## Expected Behavior
+
+What should happen instead?
+
+## Actual Behavior
+
+What actually happened?
+
+## Environment
+
+- **OS:** (e.g., Linux, macOS, Windows)
+- **Rust version:** (run `rustc --version`)
+- **How you built FeDIY:** (cargo build, nix build, etc.)
+- **FeDIY version or commit:** (if applicable)
+
+## Logs and Error Messages
+
+```
+Paste any relevant error messages, logs, or stack traces here.
+```
+
+## Screenshots or Videos
+
+If applicable, add screenshots or video recordings to help explain the problem.
+
+## Additional Context
+
+Anything else that might be helpful?
+
+## Possible Solution (Optional)
+
+If you have thoughts on how to fix this, share them here!
+
+---
+
+**Thank you for reporting this!** We appreciate your help making FeDIY better.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,38 @@
+---
+name: Feature Request
+about: Suggest an idea for FeDIY
+title: "[FEATURE] "
+labels: feature
+assignees: ''
+
+---
+
+## Description
+
+What would you like to see in FeDIY? Describe the feature or enhancement you're suggesting.
+
+## Motivation
+
+Why do you want this? What problem does it solve? How would it help you or the community?
+
+## Example Use Case
+
+Can you describe a specific scenario where this feature would be useful?
+
+## Proposed Solution
+
+Do you have an idea for how this could be implemented? (Feel free to skip this if you don't!)
+
+## Alternatives
+
+Are there other ways to solve this problem?
+
+## Additional Context
+
+Any other information that would be helpful? Links to related issues, discussions, or external resources?
+
+---
+
+**Thank you for sharing your idea!** Even if we can't implement everything, your feedback helps us understand what the community needs.
+
+**Note:** Large features might be discussed further before work begins. Check [ROADMAP.md](../../docs/ROADMAP.md) and [OPEN_QUESTIONS.md](../../docs/OPEN_QUESTIONS.md) to see if this aligns with our current direction!

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,30 @@
+---
+name: Question or Discussion
+about: Ask a question or start a discussion about FeDIY
+title: "[QUESTION] "
+labels: question
+assignees: ''
+
+---
+
+## Your Question
+
+What would you like to know or discuss?
+
+## Context
+
+Help us understand the context of your question. What are you trying to do? What's your background with FeDIY?
+
+## What Have You Tried?
+
+Have you already looked somewhere for the answer? (Docs, existing issues, etc.)
+
+## Additional Information
+
+Anything else that might help us answer your question?
+
+---
+
+**Thank you for asking!** We're here to help. No question is too small or basic.
+
+If you think this discussion should result in documentation changes, let us know—we'd love to improve our docs based on questions!

.github/pull_request_template.md

@@ -0,0 +1,45 @@
+## Description
+
+Please describe what this pull request does. What problem does it solve? What feature does it add?
+
+**Closes:** #(issue number, if applicable)
+
+## Type of Change
+
+- [ ] Bug fix (non-breaking change that fixes an issue)
+- [ ] New feature (non-breaking change that adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to change)
+- [ ] Documentation update
+- [ ] Refactoring (no functional change)
+- [ ] Test improvement
+
+## How Has This Been Tested?
+
+How did you test your changes? Please describe:
+
+- [ ] Existing tests pass
+- [ ] Added new tests
+- [ ] Tested manually (describe how)
+- [ ] Other (describe)
+
+## Checklist
+
+- [ ] Code follows the project style (`cargo fmt`, `cargo clippy`)
+- [ ] All tests pass (`cargo test`)
+- [ ] New tests added for new functionality (if applicable)
+- [ ] Documentation updated (if applicable)
+- [ ] Commit messages are clear and follow conventions
+- [ ] I have read the [Code of Conduct](../../CODE_OF_CONDUCT.md)
+- [ ] My changes don't introduce security or accessibility issues
+
+## Screenshots or Examples (Optional)
+
+If your change affects the UI or user experience, add screenshots or examples here.
+
+## Additional Notes
+
+Anything else reviewers should know? Any trade-offs or decisions you made?
+
+---
+
+**Thank you for contributing!** We appreciate your effort. If you have any questions while preparing this PR, don't hesitate to ask in comments.