ararog · ararog · Jan 23, 2026 · Jan 23, 2026
diff --git a/README.md b/README.md
@@ -1,28 +1,29 @@
 # Sophia
 
-Full-stack web framework for Rust.
+🌟 **The elegant full-stack web framework that makes Rust web development effortless**
 
-## Description
+**Sophia** is a comprehensive, production-ready web framework for Rust that combines simplicity with power. Built on top of VeTiS, it provides everything you need to build modern web applications - from REST APIs to full-featured web services - with a clean, intuitive API that makes development a joy.
 
-**Sophia** is a full-stack web framework for Rust.
+## ✨ Why Sophia?
 
-## Install
+- **🎯 Developer Experience**: Ergonomic API design that feels natural and intuitive
+- **⚡ High Performance**: Powered by VeTiS for blazing-fast request handling
+- **🔧 Flexible Runtime**: Choose between Tokio or Smol async runtimes
+- **🛡️ Production Ready**: Built-in security, middleware, and monitoring capabilities
+- **📦 All-in-One**: Full-stack features from routing to authentication
+- **🚀 Modern Architecture**: Designed for today's web applications
+
+## 🛠️ Quick Start
+
+Add Sophia to your `Cargo.toml`:
 
 ```rust
 sophia = { version = "0.1.0", features = ["vetis"] }
 ```
 
-## Runtimes
-
-- [tokio](https://github.com/tokio-rs/tokio)
-- [smol](https://github.com/smol-rs/smol)
+## 💡 Usage Example
 
-## Crate features
-
-- tokio-rt (default)
-- smol-rt
-
-## Examples
+Here's how simple it is to create a web application with Sophia:
 
 ```rust
 use sophia::Sophia;
@@ -45,10 +46,30 @@ async fn main() -> Result<(), Box<dyn std::error::Error>> {
 
 ```
 
-## License
+## 🎯 Perfect For
+
+- **🚀 REST APIs**: Build robust, scalable API services
+- **🌐 Web Applications**: Create full-featured web applications
+- **📱 Microservices**: Develop lightweight, focused services
+- **🔧 Backend Services**: Power modern frontend applications
+- **📊 Real-time Apps**: WebSocket and streaming applications
+- **🤖 AI Integration**: Build AI-powered web services
+
+## ⚙️ Supported Runtimes
+
+- [tokio](https://github.com/tokio-rs/tokio) - High-performance async runtime
+- [smol](https://github.com/smol-rs/smol) - Lightweight async runtime
+
+## 🔧 Crate Features
+
+- **tokio-rt** (default) - Tokio runtime support
+- **smol-rt** - Smol runtime support
+- **vetis** - VeTiS server integration
+
+## 📄 License
 
 MIT
 
-## Author
+## 👤 Author
 
 Rogerio Pereira Araujo <rogerio.araujo@gmail.com>
diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md
@@ -0,0 +1,177 @@
+---
+layout: default
+title: Contributing
+nav_order: 1
+permalink: /contributing
+---
+
+# Contributing to deboa
+
+First off, thanks for taking the time to contribute! ❤️
+
+All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉
+
+> And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
+> - Star the project
+> - Tweet about it
+> - Refer this project in your project's readme
+> - Mention the project at local meetups and tell your friends/colleagues
+
+## Table of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [I Have a Question](#i-have-a-question)
+  - [I Want To Contribute](#i-want-to-contribute)
+  - [Reporting Bugs](#reporting-bugs)
+  - [Suggesting Enhancements](#suggesting-enhancements)
+  - [Your First Code Contribution](#your-first-code-contribution)
+  - [Improving The Documentation](#improving-the-documentation)
+- [Styleguides](#styleguides)
+  - [Commit Messages](#commit-messages)
+- [Join The Project Team](#join-the-project-team)
+
+
+## Code of Conduct
+
+This project and everyone participating in it is governed by the
+[deboa Code of Conduct](https://github.com/ararog/deboa/blob/master/CODE_OF_CONDUCT.md).
+By participating, you are expected to uphold this code. Please report unacceptable behavior
+to <>.
+
+
+## I Have a Question
+
+> If you want to ask a question, we assume that you have read the available [Documentation]().
+
+Before you ask a question, it is best to search for existing [Issues](https://github.com/ararog/deboa/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
+
+If you then still feel the need to ask a question and need clarification, we recommend the following:
+
+- Open an [Issue](https://github.com/ararog/deboa/issues/new).
+- Provide as much context as you can about what you're running into.
+- Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
+
+We will then take care of the issue as soon as possible.
+
+<!--
+You might want to create a separate issue tag for questions and include it in this description. People should then tag their issues accordingly.
+
+Depending on how large the project is, you may want to outsource the questioning, e.g. to Stack Overflow or Gitter. You may add additional contact and information possibilities:
+- IRC
+- Slack
+- Gitter
+- Stack Overflow tag
+- Blog
+- FAQ
+- Roadmap
+- E-Mail List
+- Forum
+-->
+
+## I Want To Contribute
+
+> ### Legal Notice
+> When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project licence.
+
+### Reporting Bugs
+
+#### Before Submitting a Bug Report
+
+A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
+
+- Make sure that you are using the latest version.
+- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](). If you are looking for support, you might want to check [this section](#i-have-a-question)).
+- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/ararog/deboa/issues?q=label%3Abug).
+- Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
+- Collect information about the bug:
+  - Stack trace (Traceback)
+  - OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
+  - Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant.
+  - Possibly your input and the output
+  - Can you reliably reproduce the issue? And can you also reproduce it with older versions?
+
+#### How Do I Submit a Good Bug Report?
+
+> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to <>.
+<!-- You may add a PGP key to allow the messages to be sent encrypted as well. -->
+
+We use GitHub issues to track bugs and errors. If you run into an issue with the project:
+
+- Open an [Issue](https://github.com/ararog/deboa/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
+- Explain the behavior you would expect and the actual behavior.
+- Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
+- Provide the information you collected in the previous section.
+
+Once it's filed:
+
+- The project team will label the issue accordingly.
+- A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as `needs-repro`. Bugs with the `needs-repro` tag will not be addressed until they are reproduced.
+- If the team is able to reproduce the issue, it will be marked `needs-fix`, as well as possibly other tags (such as `critical`), and the issue will be left to be [implemented by someone](#your-first-code-contribution).
+
+<!-- You might want to create an issue template for bugs and errors that can be used as a guide and that defines the structure of the information to be included. If you do so, reference it here in the description. -->
+
+
+### Suggesting Enhancements
+
+This section guides you through submitting an enhancement suggestion for deboa, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
+
+#### Before Submitting an Enhancement
+
+- Make sure that you are using the latest version.
+- Read the [documentation]() carefully and find out if the functionality is already covered, maybe by an individual configuration.
+- Perform a [search](https://github.com/ararog/deboa/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
+- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
+
+#### How Do I Submit a Good Enhancement Suggestion?
+
+Enhancement suggestions are tracked as [GitHub issues](https://github.com/ararog/deboa/issues).
+
+- Use a **clear and descriptive title** for the issue to identify the suggestion.
+- Provide a **step-by-step description of the suggested enhancement** in as many details as possible.
+- **Describe the current behavior** and **explain which behavior you expected to see instead** and why. At this point you can also tell which alternatives do not work for you.
+- You may want to **include screenshots or screen recordings** which help you demonstrate the steps or point out the part which the suggestion is related to. You can use [LICEcap](https://www.cockos.com/licecap/) to record GIFs on macOS and Windows, and the built-in [screen recorder in GNOME](https://help.gnome.org/users/gnome-help/stable/screen-shot-record.html.en) or [SimpleScreenRecorder](https://github.com/MaartenBaert/ssr) on Linux. <!-- this should only be included if the project has a GUI -->
+- **Explain why this enhancement would be useful** to most deboa users. You may also want to point out the other projects that solved it better and which could serve as inspiration.
+
+<!-- You might want to create an issue template for enhancement suggestions that can be used as a guide and that defines the structure of the information to be included. If you do so, reference it here in the description. -->
+
+### Your First Code Contribution
+
+Always set up your environment and IDE before contributing to the project. When you are ready to start contributing, please follow the steps below:
+
+- Fork repository
+- Clone forked repository
+- Create a new branch
+- Make your changes
+- Commit your changes
+- Push your changes
+- Open a pull request
+
+Please set project maintainer as the reviewer of your pull request.
+
+### Improving The Documentation
+
+For every change in the code, please update the documentation. Please add examples and explainations to the documentation.
+If you are adding a new feature, please add a new section to the documentation. Also create a small example inside examples folder.
+
+
+## Styleguides
+
+### Commit Messages
+
+In project we use [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). Please use it when committing your changes.
+Limit title to 72 characters.
+
+### Rust
+
+In project we use [rustfmt](https://github.com/rust-lang/rustfmt) to format the code.
+We also use [clippy](https://github.com/rust-lang/rust-clippy) to lint the code.
+And we use [samoyed](https://github.com/nutthead/samoyed) manage git hooks.
+
+## Join The Project Team
+
+In order to join the project team, please make your first contribution.
+
+Once your first contribution is merged, please send a mail to <rogerio.araujo@gmail.com> to join the project team.
+
+## Attribution
+This guide is based on the [contributing.md](https://contributing.md/generator)!
diff --git a/docs/LICENSE.md b/docs/LICENSE.md
@@ -0,0 +1,29 @@
+---
+layout: default
+title: License
+nav_order: 1
+permalink: /license
+---
+
+# MIT License
+
+Copyright (c) 2025 Rogerio Pereira Araújo <rogerio.pereira@gmail.com>
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
diff --git a/docs/_config.yml b/docs/_config.yml
@@ -0,0 +1,23 @@
+title: Sophia
+baseurl: "/sophia" # the subpath of your site, e.g. /blog
+url: "https://ararog.github.io" # the base hostname & protocol for your site
+
+theme: jekyll-theme-cayman
+
+markdown: kramdown
+
+plugins:
+  - jekyll-seo-tag
+  - jekyll-sitemap
+  - jekyll-feed
+
+defaults:
+  - scope:
+      path: ""
+    values:
+      layout: "default"
+      toc: true
+      toc_sticky: true
+      sidebar:
+        nav: "navigation"
+