Fix typos, add documentation files, and improve SEO/security

- Fix typos: Browse -> browsing, GitHub capitalization, missing quote
- Add LICENSE file with CC BY-NC 4.0 license
- Add CONTRIBUTING.md with contribution guidelines
- Add CODE_OF_CONDUCT.md for community standards
- Security: Fix font preload CORS (crossorigin: 'anonymous')
- SEO: Add canonical URL and og:type meta tags
- SEO: Use absolute URLs for Open Graph and Twitter Card images

Author: Turtlecute33

CODE_OF_CONDUCT.md

@@ -0,0 +1,113 @@
+# Code of Conduct
+
+## Our Commitment
+
+The Privacy Activist Kit is committed to providing a safe and welcoming environment for everyone who wants to learn about and contribute to digital privacy and security. We expect all community members to treat each other with respect and dignity.
+
+## Our Values
+
+This project exists to empower people to protect their digital rights and privacy. We believe that:
+
+- **Privacy is a human right** that should be accessible to everyone
+- **Collaboration works best** when everyone feels safe to contribute, ask questions, and share knowledge
+- **Respect is fundamental** to building trust and creating meaningful change
+
+## Expected Behavior
+
+We expect all community members, contributors, and maintainers to:
+
+- **Be respectful and considerate** in all interactions
+- **Be patient with beginners** and remember that everyone started somewhere
+- **Give and receive constructive feedback** gracefully and with good intent
+- **Focus on what is best for the community** and the project's mission
+- **Respect different threat models and privacy needs** without judgment
+- **Maintain confidentiality** when discussing sensitive security topics
+- **Credit the work of others** and respect intellectual property
+
+## Unacceptable Behavior
+
+The following behaviors are unacceptable in our community:
+
+- **Harassment or discrimination** of any kind
+- **Trolling, insulting comments, or personal attacks**
+- **Publishing others' private information** without explicit permission (doxing)
+- **Deliberate intimidation, stalking, or following**
+- **Advocating for or encouraging** any of the above behaviors
+- **Promoting malicious hacking** or offensive security tactics that could harm others
+- **Sharing exploits or vulnerabilities** in ways that put people at risk
+- **Disrupting discussions** or derailing conversations
+- **Other conduct** that could reasonably be considered inappropriate in a professional or community setting
+
+## Scope
+
+This Code of Conduct applies to all project spaces, including:
+
+- GitHub repositories (issues, pull requests, discussions, code)
+- Project documentation and website content
+- Community forums and communication channels
+- Events or meetups representing the project
+- Social media accounts associated with the project
+
+This Code of Conduct also applies when an individual is representing the project in public spaces.
+
+## Privacy and Security Considerations
+
+Given the nature of this project, we have additional guidelines:
+
+- **Don't share sensitive personal information** in public spaces (issues, pull requests, etc.)
+- **Report security vulnerabilities privately** before disclosing them publicly
+- **Be mindful of operational security** when discussing activist work or threat models
+- **Respect that people have different levels of risk** and different privacy needs
+- **Don't pressure anyone to share** their personal threat model, location, identity, or affiliations
+
+## Enforcement
+
+### Reporting
+
+If you experience or witness unacceptable behavior, or have any other concerns, please report it by:
+
+- Opening a private issue to the project maintainers (if available)
+- Contacting the maintainers through the project's designated reporting channels
+- Reaching out through GitHub's reporting features for serious violations
+
+All reports will be handled with discretion and confidentiality.
+
+### Response
+
+Project maintainers are responsible for clarifying and enforcing this Code of Conduct. They will:
+
+- Review all reports fairly and promptly
+- Respect the privacy and security of the reporter
+- Take appropriate action in response to violations
+
+### Consequences
+
+Community members who violate this Code of Conduct may face consequences including:
+
+1. **Warning**: A private, written warning explaining the violation and expected behavior going forward
+2. **Temporary Ban**: A temporary ban from interacting with the project for a specified period
+3. **Permanent Ban**: A permanent ban from the community and project spaces
+
+The severity of the consequence will depend on the nature and frequency of the violation.
+
+## Attribution
+
+This Code of Conduct is adapted from:
+- [Contributor Covenant v2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct/)
+- [Citizen Code of Conduct](https://github.com/stumpsyn/policies/blob/master/citizen_code_of_conduct.md)
+
+## Questions
+
+If you have questions about this Code of Conduct, please:
+- Open an issue for public discussion of policy clarifications
+- Contact the maintainers privately for sensitive questions
+
+## Changes
+
+This Code of Conduct may be updated from time to time. Community members are encouraged to check back periodically. Significant changes will be announced through project communication channels.
+
+---
+
+**Last Updated**: January 2025
+
+By participating in this project, you agree to abide by this Code of Conduct.

CONTRIBUTING.md

@@ -0,0 +1,128 @@
+# Contributing to Privacy Activist Kit
+
+Thank you for considering contributing to the Privacy Activist Kit! This project exists to help people protect their digital privacy, and your contributions help make that mission stronger.
+
+## How You Can Help
+
+There are many ways to contribute, and you don't need to be a developer or security expert to make a meaningful impact:
+
+### 🌟 Non-Technical Contributions
+
+- **Star the repository** on GitHub to help others discover the project
+- **Share the project** on social media or with communities who might benefit
+- **Report broken links** or outdated information
+- **Suggest new tools or services** that align with the project's privacy-focused mission
+- **Improve readability** by fixing typos, clarifying language, or improving explanations
+- **Translate content** to make privacy resources accessible in more languages
+- **Share feedback** on what's working well or what could be improved
+
+### 📝 Content Contributions
+
+- **Add new guides** on privacy topics not yet covered
+- **Update existing content** with current best practices
+- **Create checklists** for specific use cases or threat models
+- **Write beginner-friendly explanations** of technical concepts
+- **Add real-world examples** to help illustrate privacy concepts
+
+### 🔧 Technical Contributions
+
+- **Fix bugs** in the website or documentation
+- **Improve site performance** or accessibility
+- **Add new features** to the VitePress site
+- **Optimize images** and other assets
+- **Improve SEO** and discoverability
+
+## Getting Started
+
+### Reporting Issues
+
+Found a problem? [Open an issue](https://github.com/Turtlecute33/PrivacyActivistKit/issues) with:
+
+- A clear, descriptive title
+- A detailed description of the issue
+- Steps to reproduce (if applicable)
+- Expected vs. actual behavior
+- Screenshots (if relevant)
+
+### Making Changes
+
+1. **Fork the repository** to your own GitHub account
+2. **Clone your fork** locally:
+   ```bash
+   git clone https://github.com/YOUR-USERNAME/PrivacyActivistKit.git
+   cd PrivacyActivistKit
+   ```
+3. **Install dependencies**:
+   ```bash
+   npm install
+   ```
+4. **Create a branch** for your changes:
+   ```bash
+   git checkout -b your-branch-name
+   ```
+5. **Make your changes** and test them locally:
+   ```bash
+   npm run docs:dev
+   ```
+6. **Commit your changes** with a clear, descriptive message:
+   ```bash
+   git commit -m "Add brief description of your changes"
+   ```
+7. **Push to your fork**:
+   ```bash
+   git push origin your-branch-name
+   ```
+8. **Open a Pull Request** from your fork to the main repository
+
+## Content Guidelines
+
+When contributing content to the Privacy Activist Kit, please follow these principles:
+
+### Voice and Tone
+
+- **Clear and accessible**: Write for a general audience, not just technical experts
+- **Direct and practical**: Focus on actionable advice people can implement
+- **Empowering, not preachy**: Help people make informed choices without judgment
+- **Honest about trade-offs**: Privacy often involves balancing security, convenience, and usability
+
+### Technical Standards
+
+- **Accuracy first**: Verify information from reliable sources before adding it
+- **Keep it current**: Privacy tools and best practices change frequently—date-sensitive content when appropriate
+- **Cite sources**: Link to official documentation, research papers, or trusted organizations
+- **Test recommendations**: Only recommend tools you've researched or used yourself
+
+### Practical Considerations
+
+- **Consider diverse threat models**: What works for one person may not work for another
+- **Respect different risk levels**: Not everyone faces the same threats
+- **Avoid assumptions**: Don't assume technical knowledge, financial resources, or specific devices
+
+### What NOT to Include
+
+- **Affiliate links or sponsored content**: This project is independent and ad-free
+- **Untested or experimental tools**: Stick to well-established, trusted solutions
+- **Illegal activities**: Focus on defensive security, not offensive techniques
+- **Fear-mongering**: Be honest about risks without creating unnecessary panic
+- **Personal opinions as facts**: Clearly distinguish recommendations from personal preferences
+
+## Code of Conduct
+
+This project is committed to providing a welcoming environment for all contributors. Please read and follow our [Code of Conduct](CODE_OF_CONDUCT.md).
+
+## License
+
+By contributing to this project, you agree that your contributions will be licensed under the [Creative Commons Attribution-NonCommercial 4.0 International License](LICENSE).
+
+This means:
+- Your contributions can be freely shared and adapted
+- You will be credited for your work
+- The project will remain non-commercial
+
+## Questions?
+
+If you have questions about contributing, feel free to:
+- [Open an issue](https://github.com/Turtlecute33/PrivacyActivistKit/issues) for discussion
+- Reach out through the project's communication channels
+
+Thank you for helping make digital privacy accessible to everyone! ✨

LICENSE

@@ -0,0 +1,36 @@
+# Creative Commons Attribution-NonCommercial 4.0 International
+
+This work is licensed under the Creative Commons Attribution-NonCommercial 4.0 International License.
+
+## You are free to:
+
+- **Share** — copy and redistribute the material in any medium or format
+- **Adapt** — remix, transform, and build upon the material
+
+The licensor cannot revoke these freedoms as long as you follow the license terms.
+
+## Under the following terms:
+
+- **Attribution** — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
+
+- **NonCommercial** — You may not use the material for commercial purposes.
+
+- **No additional restrictions** — You may not apply legal terms or technological measures that legally restrict others from doing anything the license permits.
+
+## Notices:
+
+You do not have to comply with the license for elements of the material in the public domain or where your use is permitted by an applicable exception or limitation.
+
+No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as publicity, privacy, or moral rights may limit how you use the material.
+
+---
+
+**Full Legal Text:** https://creativecommons.org/licenses/by-nc/4.0/legalcode
+
+**Human-Readable Summary:** https://creativecommons.org/licenses/by-nc/4.0/
+
+**SPDX Identifier:** CC-BY-NC-4.0
+
+---
+
+Copyright © 2024-2025 Privacy Activist Kit Contributors

docs/.vitepress/config.mts

@@ -5,18 +5,21 @@ import checkbox from 'markdown-it-checkbox'
 export default defineConfig({
       head: [
     ['link', { rel: 'icon', href: '/favicon.ico' }],
-    ['link', { rel: 'preload', href: '/assets/inter-italic-latin-ext.CN1xVJS-.woff2', as: 'font', type: 'font/woff2', crossorigin: '' }],
-    ['link', { rel: 'preload', href: '/assets/inter-roman-latin-ext.4ZJIpNVo.woff2', as: 'font', type: 'font/woff2', crossorigin: '' }],
+    ['link', { rel: 'preload', href: '/assets/inter-italic-latin-ext.CN1xVJS-.woff2', as: 'font', type: 'font/woff2', crossorigin: 'anonymous' }],
+    ['link', { rel: 'preload', href: '/assets/inter-roman-latin-ext.4ZJIpNVo.woff2', as: 'font', type: 'font/woff2', crossorigin: 'anonymous' }],
+    // SEO
+    ['link', { rel: 'canonical', href: 'https://privacyactivistkit.org' }],
     // Open Graph
     ['meta', { property: 'og:title', content: 'Privacy Activist Kit' }],
     ['meta', { property: 'og:description', content: 'A complete guide to digital self-defense for activists, journalists, and everyone else.' }],
-    ['meta', { property: 'og:image', content: '/pak.jpg' }],
+    ['meta', { property: 'og:image', content: 'https://privacyactivistkit.org/pak.jpg' }],
     ['meta', { property: 'og:url', content: 'https://privacyactivistkit.org' }],
+    ['meta', { property: 'og:type', content: 'website' }],
     // Twitter Card
     ['meta', { name: 'twitter:card', content: 'summary_large_image' }],
     ['meta', { name: 'twitter:title', content: 'Privacy Activist Kit' }],
     ['meta', { name: 'twitter:description', content: 'A complete guide to digital self-defense for activists, journalists, and everyone else.' }],
-    ['meta', { name: 'twitter:image', content: '/pak.jpg' }]
+    ['meta', { name: 'twitter:image', content: 'https://privacyactivistkit.org/pak.jpg' }]
   ],
   title: "Privacy Activist Kit",
   description: "A complete guide to digital self-defense for activists, journalists, and everyone else.",