docs: improve documentation and developer onboarding

Author: GaspardKirira

CHANGELOG.md

@@ -8,7 +8,27 @@ This project follows a simple versioning strategy:
 - fixes → patch
 
 ---
-## v0.2.0
+## [v0.2.1]
+
+### Added
+- Add full documentation for template engine:
+  - architecture
+  - AST
+  - rendering
+  - syntax
+  - roadmap
+- Add CONTRIBUTING.md with contribution guidelines
+- Add SECURITY.md with vulnerability reporting policy
+- Add CODE_OF_CONDUCT.md
+
+### Changed
+- Improve README with clear usage examples and positioning
+- Refine documentation structure for better developer experience
+
+### Notes
+This release focuses on documentation, clarity, and onboarding experience.
+
+## [v0.2.0]
 
 ### Added
 - Add CMakePresets.json for unified configure/build/test workflows (Ninja + MSVC)

CODE_OF_CONDUCT.md

@@ -0,0 +1,119 @@
+# Vix.cpp Code of Conduct
+
+## Our Commitment
+
+We are committed to fostering a welcoming, inclusive, and professional community around **Vix.cpp**.
+
+We want this project to be a place where developers from all backgrounds can collaborate, learn, and build high-quality software together, free from harassment or discrimination.
+
+We pledge to make participation in this project a harassment-free experience for everyone, regardless of:
+
+- age, body size, disability, ethnicity, nationality
+- gender identity or expression
+- level of experience or education
+- personal appearance
+- race, religion, sexual identity, or orientation
+
+---
+
+## Our Standards
+
+### Expected Behavior
+
+Contributors are expected to:
+
+- Be respectful, professional, and constructive in all interactions
+- Provide feedback focused on ideas and code, not individuals
+- Welcome newcomers and support less experienced contributors
+- Respect differing viewpoints and experiences
+- Give proper credit for others’ work and ideas
+- Act in the best interest of the project and its community
+
+### Unacceptable Behavior
+
+The following behaviors are not tolerated:
+
+- Sexualized language, imagery, or unwelcome advances
+- Trolling, insulting, or derogatory comments
+- Harassment, intimidation, or threats (public or private)
+- Publishing private information about others without explicit permission
+- Any conduct that would reasonably be considered inappropriate in a professional environment
+
+---
+
+## Enforcement Responsibilities
+
+Project maintainers are responsible for clarifying and enforcing this Code of Conduct.
+
+They may remove, edit, or reject comments, commits, issues, pull requests, or other contributions that violate these standards.
+
+Maintainers may also temporarily or permanently ban contributors whose behavior they deem harmful, abusive, or disruptive.
+
+---
+
+## Scope
+
+This Code of Conduct applies within all project spaces, including but not limited to:
+
+- GitHub issues, pull requests, discussions, and code reviews
+- Official communication channels related to Vix.cpp
+
+It also applies when an individual is representing the project in public spaces, such as:
+
+- Using official project communication channels
+- Representing Vix.cpp at events, conferences, or online discussions
+
+---
+
+## Enforcement
+
+If you experience or witness behavior that violates this Code of Conduct, please report it by contacting:
+
+**Email:** gaspardkirira@outlook.com
+
+All reports will be reviewed promptly and handled with discretion.  
+Project maintainers are committed to respecting the privacy and safety of everyone involved.
+
+---
+
+## Enforcement Guidelines
+
+When determining appropriate consequences, maintainers will consider the context, severity, and history of the behavior.
+
+### 1. Correction
+
+**Impact:** Minor unprofessional or inappropriate behavior.  
+**Consequence:** Private clarification and guidance on expected conduct.
+
+### 2. Warning
+
+**Impact:** Repeated minor violations or a single significant incident.  
+**Consequence:** Formal warning and possible temporary limitations on participation.
+
+### 3. Temporary Ban
+
+**Impact:** Serious or repeated violations of community standards.  
+**Consequence:** Temporary suspension from participation in project spaces.
+
+### 4. Permanent Ban
+
+**Impact:** Sustained pattern of abusive, hostile, or harmful behavior.  
+**Consequence:** Permanent removal from all project-related spaces.
+
+---
+
+## Attribution
+
+This Code of Conduct is adapted from the  
+[Contributor Covenant, version 2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).
+
+For additional information, see:  
+https://www.contributor-covenant.org/faq
+
+---
+
+## Summary
+
+All contributors are expected to act with professionalism, respect, and integrity.
+
+By participating in **Vix.cpp**, you help build not only high-performance software, but also a healthy and collaborative community.

CONTRIBUTING.md

@@ -0,0 +1,159 @@
+# Contributing to Vix Template Engine
+
+Thank you for your interest in contributing.
+
+This project focuses on performance, clarity, and deterministic behavior. Contributions should follow these principles.
+
+---
+
+## Philosophy
+
+Before contributing, understand the core goals:
+
+- deterministic behavior
+- minimal design
+- no hidden state
+- performance-first mindset
+
+If your change adds complexity, it must bring clear value.
+
+---
+
+## Getting Started
+
+### 1. Fork the repository
+
+```bash
+git clone https://github.com/vixcpp/template.git
+cd template
+```
+
+### 2. Create a branch
+
+```bash
+git checkout -b feature/my-feature
+```
+
+### 3. Build the project
+
+```bash
+cmake --preset dev-ninja
+cmake --build --preset build-ninja
+```
+
+### 4. Run tests
+
+```bash
+ctest --preset test-ninja
+```
+
+---
+
+## Code Guidelines
+
+### C++ Standards
+
+- Use modern C++ (C++20)
+- Prefer RAII
+- Avoid raw pointers unless necessary
+- Use `std::unique_ptr` for ownership
+- Avoid unnecessary allocations
+
+### Style
+
+- Clear and explicit code
+- Small, focused functions
+- No hidden behavior
+- Avoid magic
+
+### Naming
+
+- Use English names
+- Be descriptive and consistent
+
+---
+
+## Architecture Rules
+
+Do not break core guarantees:
+
+- AST must remain deterministic
+- Renderer must remain stateless
+- No I/O inside rendering
+- No global mutable state
+
+---
+
+## Tests
+
+All changes must include tests when relevant.
+
+- Add tests in `tests/`
+- Keep tests deterministic
+- Avoid external dependencies
+
+---
+
+## Benchmarks
+
+If your change impacts performance:
+
+- update benchmarks in `benchmarks/`
+- explain performance impact in PR
+
+---
+
+## Commit Messages
+
+Use clear messages:
+
+```bash
+feat(parser): add filter node support
+fix(renderer): avoid unnecessary allocations
+refactor(cache): use shared template handles
+```
+
+---
+
+## Pull Requests
+
+Before opening a PR:
+
+- ensure project builds
+- ensure tests pass
+- keep PR focused (one change = one PR)
+- describe clearly what you changed and why
+
+---
+
+## What Not to Do
+
+- do not introduce heavy dependencies
+- do not add magic behavior
+- do not break deterministic design
+- do not add features without discussion (for large changes)
+
+---
+
+## Discussions
+
+For large features:
+
+- open an issue first
+- discuss design before implementation
+
+---
+
+## Summary
+
+Good contributions are:
+
+- simple
+- explicit
+- fast
+- aligned with architecture
+
+---
+
+Thanks for contributing to Vix Template Engine 🚀
+