rebase project

.github/workflows/node.js.yml

@@ -0,0 +1,36 @@
+name: Node.js CI
+
+on:
+ push:
+ branches: [ "main" , "dev" ]
+ pull_request:
+ branches: [ "main" , "dev"]
+
+jobs:
+ build:
+
+ runs-on: ubuntu-latest
+
+ strategy:
+ matrix:
+ node-version: [ 16.x ]
+ pnpm-version: [ 8.0.0 ]
+ name: Use Node.js ${{ matrix.node-version }}
+ steps:
+
+ - name: Checkout code
+ uses: actions/checkout@v4
+
+ - name: Setup Node enviroment
+ uses: actions/setup-node@v4
+ with:
+ node-version: ${{ matrix.node-version }}
+
+ - name: Setup Pnpm
+ uses: pnpm/action-setup@v2
+ with:
+ version: ${{matrix.pnpm-version}}
+
+ - name: Install Pnpm
+ run: pnpm install
+

.gitignore

@@ -0,0 +1,27 @@
+# build output
+dist/
+# generated types
+.astro/
+
+# dependencies
+node_modules/
+
+# logs
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+
+
+# environment variables
+.env
+.env.production
+
+# macOS-specific files
+.DS_Store
+
+# Language directories to ignore
+astro_tmp_pages_*
+
+# Local Netlify folder
+.netlify

.npmignore

@@ -0,0 +1,29 @@
+# build output
+dist/
+# generated types
+.astro/
+
+# dependencies
+node_modules/
+
+# logs
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+
+# environment variables
+.env
+.env.production
+
+# macOS-specific files
+.DS_Store
+
+# Language directories to ignore
+astro_tmp_pages_*
+
+# Include npmrc
+!.npmrc
+
+# Github Actions
+.github/workflows/publish.yml

.npmrc

@@ -0,0 +1 @@
+shamefully-hoist=true

.prettierignore

@@ -0,0 +1 @@
+node_modules/**

.prettierrc

@@ -0,0 +1,8 @@
+{
+ "tabWidth": 4,
+ "useTabs": true,
+ "bracketSameLine": true,
+ "printWidth": 150,
+ "htmlWhitespaceSensitivity": "ignore",
+ "plugins": ["prettier-plugin-astro", "prettier-plugin-tailwindcss"]
+}

.vscode/extensions.json

@@ -0,0 +1,9 @@
+{
+ "recommendations": [
+ "astro-build.astro-vscode",
+ "bradlc.vscode-tailwindcss",
+ "christian-kohler.path-intellisense",
+ "adrianwilczynski.alpine-js-intellisense"
+ ],
+ "unwantedRecommendations": []
+}

.vscode/launch.json

@@ -0,0 +1,11 @@
+{
+ "version": "0.2.0",
+ "configurations": [
+ {
+ "command": "call ./node_modules/.bin/astro dev",
+ "name": "Development server",
+ "request": "launch",
+ "type": "node-terminal"
+ }
+ ]
+}

.vscode/settings.json

@@ -0,0 +1,3 @@
+{
+ "css.customData": [".vscode/tailwind.json"]
+}

.vscode/tailwind.json

@@ -0,0 +1,55 @@
+{
+ "version": 1.1,
+ "atDirectives": [
+ {
+ "name": "@tailwind",
+ "description": "Use the `@tailwind` directive to insert Tailwind's `base`, `components`, `utilities` and `screens` styles into your CSS.",
+ "references": [
+ {
+ "name": "Tailwind Documentation",
+ "url": "https://tailwindcss.com/docs/functions-and-directives#tailwind"
+ }
+ ]
+ },
+ {
+ "name": "@apply",
+ "description": "Use the `@apply` directive to inline any existing utility classes into your own custom CSS. This is useful when you find a common utility pattern in your HTML that you’d like to extract to a new component.",
+ "references": [
+ {
+ "name": "Tailwind Documentation",
+ "url": "https://tailwindcss.com/docs/functions-and-directives#apply"
+ }
+ ]
+ },
+ {
+ "name": "@responsive",
+ "description": "You can generate responsive variants of your own classes by wrapping their definitions in the `@responsive` directive:\n```css\n@responsive {\n .alert {\n background-color: #E53E3E;\n }\n}\n```\n",
+ "references": [
+ {
+ "name": "Tailwind Documentation",
+ "url": "https://tailwindcss.com/docs/functions-and-directives#responsive"
+ }
+ ]
+ },
+ {
+ "name": "@screen",
+ "description": "The `@screen` directive allows you to create media queries that reference your breakpoints by **name** instead of duplicating their values in your own CSS:\n```css\n@screen sm {\n /* ... */\n}\n```\n…gets transformed into this:\n```css\n@media (min-width: 640px) {\n /* ... */\n}\n```\n",
+ "references": [
+ {
+ "name": "Tailwind Documentation",
+ "url": "https://tailwindcss.com/docs/functions-and-directives#screen"
+ }
+ ]
+ },
+ {
+ "name": "@variants",
+ "description": "Generate `hover`, `focus`, `active` and other **variants** of your own utilities by wrapping their definitions in the `@variants` directive:\n```css\n@variants hover, focus {\n .btn-brand {\n background-color: #3182CE;\n }\n}\n```\n",
+ "references": [
+ {
+ "name": "Tailwind Documentation",
+ "url": "https://tailwindcss.com/docs/functions-and-directives#variants"
+ }
+ ]
+ }
+ ]
+}

CONTRIBUTING.md

@@ -0,0 +1,81 @@
+# Contributing
+
+When contributing to this repository, please first discuss the change you wish to make via issue,
+email, or any other method with the owners of this repository before making a change. 
+
+Please note we have a code of conduct, please follow it in all your interactions with the project.
+
+## Pull Request Process
+
+
+1. fork the repo.
+2. Ensure any install or build dependencies are removed before the end of the layer when doing a 
+ build.
+3. Create a new branch for pull request.
+
+## Code of Conduct
+
+### Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+### Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+### Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+### Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+### Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.

LICENSE

@@ -0,0 +1,20 @@
+Copyright (c) 2024 Matheus Alves.
+
+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.

README.md

@@ -0,0 +1,70 @@
+<h1 align="center"> Anoto Website</h1>
+
+### Preview
+![Captura de tela 2023-12-30 182503](https://github.com/MatheusAlvesPereira/Anoto-Website/assets/99885299/c376ae19-076a-49cf-9591-48f309d66ada)
+![Captura de tela 2023-12-30 182520](https://github.com/MatheusAlvesPereira/Anoto-Website/assets/99885299/e5d3fa5a-02bd-480a-9867-29a9140261af)
+![Captura de tela 2023-12-30 182609](https://github.com/MatheusAlvesPereira/Anoto-Website/assets/99885299/a6914fb9-29e7-4033-803b-7d77cfdb9519)
+![Captura de tela 2023-12-30 183214](https://github.com/MatheusAlvesPereira/Anoto-Website/assets/99885299/b320e813-9f36-4de5-b024-696bb56637fe)
+
+## Installation
+
+1. Clone the repository:
+
+```bash
+$ git clone https://github.com/MatheusAlvesPereira/Anoto-Website.git
+```
+
+2. run `pnpm install`
+3. If you want to switch to npm make sure to remove pnpm-lock.yaml and node_modules folder and then run `npm install`
+
+All commands are run from the root of the project, from a terminal:
+
+| Command | Action |
+| :--------------------- | :----------------------------------------------- |
+| `pnpm install` | Installs dependencies |
+| `pnpm dev` | Starts local dev server at `localhost:4321` |
+| `pnpm build` | Build your production site to `./dist/` |
+| `pnpm preview` | Preview your build locally, before deploying |
+| `pnpm astro ...` | Run CLI commands like `astro add`, `astro check` |
+| `pnpm astro -- --help` | Get help using the Astro CLI |
+
+### Project Structure
+
+Inside of your Astro project, you'll see the following folders and files:
+
+```
+├── public/
+├── src/
+│   ├── components/
+│   ├── content/
+│   ├── layouts/
+│   ├── locales/
+│   ├── middleware/
+│   ├── pages/
+│   ├── styles/
+│   ├── utils/
+│   └── consts.ts/
+│   └── env.d.ts/
+├── .prettierrc
+├── astro.config.mjs
+├── CONTRIBUTING.md
+├── LICENSE
+├── package.json
+├── pnpm-lock.yaml
+├── README.md
+├── tailwind.config.cjs
+└── tsconfig.json
+```
+
+This project use the template [Astro-starter](https://github.com/zankhq/astro-starter)
+
+### About Astro.js...
+
+Check out [Astro documentation](https://docs.astro.build) 
+
+### Check the AnotoApp...
+
+[AnotoApp](https://github.com/MatheusAlvesPereira/Anoto-App)
+
+
+