diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000..56fa97e
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,125 @@
+##
+
+
+
+
+```
+
+The `header` is mandatory and must conform to the [Commit Message Header](#commit-header) format.
+
+The `body` is mandatory for all commits except for those of type "docs".
+When the body is present it must be at least 20 characters long and must conform to the [Commit Message Body](#commit-body) format.
+
+The `footer` is optional. The [Commit Message Footer](#commit-footer) format describes what the footer is used for and the structure it must have.
+
+#### ():
+ │ │ │
+ │ │ └─⫸ Summary in present tense. Not capitalized. No period at the end.
+ │ │
+ │ └─⫸ Commit Scope: layouts|components|components-widgets|components-atoms|pages
+ │ pages-blog|pages-docs|scripts|assets
+ │ platform-browser-dynamic|platform-server|router|service-worker|
+ │
+ └─⫸ Commit Type: build|ci|docs|feat|fix|perf|refactor|test
+```
+
+The `` and `` fields are mandatory, the `()` field is optional.
+
+##### Type
+
+Must be one of the following:
+
+- **build**: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
+- **ci**: Changes to our CI configuration files and scripts (examples: CircleCi, SauceLabs)
+- **docs**: Documentation only changes
+- **feat**: A new feature
+- **fix**: A bug fix
+- **perf**: A code change that improves performance
+- **refactor**: A code change that neither fixes a bug nor adds a feature
+- **test**: Adding missing tests or correcting existing tests
+
+##### Scope
+
+The scope should be the name of the npm package affected (as perceived by the person reading the changelog generated from commit messages).
+
+The following is the list of supported scopes:
+
+- `layouts`
+- `components`
+- `components-widgets`
+- `components-atoms`
+- `pages`
+- `pages-blog`
+- `pages-docs`
+- `scripts`
+- `assets`
+
+There are currently a few exceptions to the "use package name" rule:
+
+- none/empty string: useful for `test` and `refactor` changes that are done across all packages (e.g. `test: add missing unit tests`) and for docs changes that are not related to a specific package (e.g. `docs: fix typo in tutorial`).
+
+##### Summary
+
+Use the summary field to provide a succinct description of the change:
+
+- use the imperative, present tense: "change" not "changed" nor "changes"
+- don't capitalize the first letter
+- no dot (.) at the end
+
+####
+
+
+
+
+Fixes #
+```
+
+or
+
+```
+DEPRECATED:
+
+
+
+
+Closes #
+```
+
+Breaking Change section should start with the phrase "BREAKING CHANGE: " followed by a summary of the breaking change, a blank line, and a detailed description of the breaking change that also includes migration instructions.
+
+Similarly, a Deprecation section should start with "DEPRECATED: " followed by a short description of what is deprecated, a blank line, and a detailed description of the deprecation that also mentions the recommended update path.
+
+### Revert commits
+
+If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit.
+
+The content of the commit message body should contain:
+
+- information about the SHA of the commit being reverted in the following format: `This reverts commit `,
+- a clear description of the reason for reverting the commit message.
diff --git a/LICENSE b/LICENSE
new file mode 100644
index 0000000..f6cbe27
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2022 Jozef Steinhübl
+
+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/README.md b/README.md
new file mode 100644
index 0000000..b321361
--- /dev/null
+++ b/README.md
@@ -0,0 +1,39 @@
+
+
+
+Source code for hyro's website, simple and modern page.
+
+
+
+
+
+
+## Setup
+
+1. Clone this repository: `git clone https://github.com/[your_username]/astro-project.git`
+2. Navigate to the project directory: `cd astro-project`
+3. Install the dependencies: `npm install`
+
+## Usage
+
+- To run the development server: `npm run dev`
+- To build the project for production: `npm run build`
+- To preview the production build: `npm run preview`
+
+## Contributing
+
+To contribute to this project, please follow the [standard Git workflow](https://git-scm.com/book/en/v2/Git-Basics-Getting-a-Git-Repository#The-Standard-Git-Workflow) and [CONTRIBUTING](./CONTRIBUTING.md).
+
+1. Fork this repository
+2. Create a new branch for your changes: `git checkout -b my-feature`
+3. Commit your changes: `git commit -am "Add my feature"`
+4. Push the branch: `git push origin my-feature`
+5. Open a pull request
+
+## License
+
+This project is licensed under the [MIT License](LICENSE).