Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .env.example
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# Example env file for local development. DO NOT commit real secrets.
NEXT_PUBLIC_FIREBASE_API_KEY=your_api_key_here
NEXT_PUBLIC_FIREBASE_AUTH_DOMAIN=your_project.firebaseapp.com
NEXT_PUBLIC_FIREBASE_PROJECT_ID=your_project_id
NEXT_PUBLIC_FIREBASE_STORAGE_BUCKET=your_project.appspot.com
NEXT_PUBLIC_FIREBASE_MESSAGING_SENDER_ID=your_messaging_sender_id
NEXT_PUBLIC_FIREBASE_APP_ID=your_app_id
31 changes: 6 additions & 25 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,25 +1,6 @@
.DS_Store
.cache
npm-debug.log
Thumbs.db
node_modules/
.build/
.vscode/extensions/**/out/
extensions/**/dist/
/out*/
/extensions/**/out/
build/node_modules
coverage/
test_data/
test-results/
test-results.xml
vscode.lsif
vscode.db
/.profile-oss
/cli/target
/cli/openssl
product.overrides.json
*.snap.actual
*.tsbuildinfo
.vscode-test
vscode-telemetry-docs/
node_modules/
.env.local
.env
/.next
npm-debug.log
package-lock.json
34 changes: 34 additions & 0 deletions DNS_ZONE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
# DNS zone records for fitvestmoda.com

The following are the DNS entries intended for the `fitvestmoda.com` zone. Apply changes only through the domain registrar or DNS provider UI (Locaweb) and follow your team's deploy checklist (see `README.md`).

Zone entries (TTL default if not set):

Root (A record)
. A 179.188.12.92

www (CNAME)
www CNAME fitvestmoda.com

_domainconnect (CNAME)
_domainconnect CNAME domainconnect.locaweb.com.br

ftp (CNAME)
ftp CNAME fitvestmoda.com

Nameservers (set at registrar)
. NS ns1.locaweb.com.br
. NS ns2.locaweb.com.br
. NS ns3.locaweb.com.br

SOA (example provided by registrar)
. SOA ns1.locaweb.com.br. postmaster.locaweb.com.br. 2025101003 3600 600 1209600 3600

Notes
- The SOA serial (2025101003) follows the YYYYMMDDnn convention — update it when changing zone records.
- The root A record points the apex domain to `179.188.12.92`.
- `www` is a CNAME to the apex; ensure your hosting supports serving traffic for the apex and the `www` alias.
- `_domainconnect` is used by domain-connect integrations (Locaweb) for automatic DNS provisioning.
- Use the checklist in `README.md` before making DNS changes (reduce TTL, test propagation, validate SSL).

If you want, I can also generate a BIND-style zone file or `dig`/`nslookup` commands to validate these records from multiple resolvers.
214 changes: 136 additions & 78 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,78 +1,136 @@
# Visual Studio Code - Open Source ("Code - OSS")
[![Feature Requests](https://img.shields.io/github/issues/microsoft/vscode/feature-request.svg)](https://github.com/microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Afeature-request+sort%3Areactions-%2B1-desc)
[![Bugs](https://img.shields.io/github/issues/microsoft/vscode/bug.svg)](https://github.com/microsoft/vscode/issues?utf8=✓&q=is%3Aissue+is%3Aopen+label%3Abug)
[![Gitter](https://img.shields.io/badge/chat-on%20gitter-yellow.svg)](https://gitter.im/Microsoft/vscode)

## The Repository

This repository ("`Code - OSS`") is where we (Microsoft) develop the [Visual Studio Code](https://code.visualstudio.com) product together with the community. Not only do we work on code and issues here, we also publish our [roadmap](https://github.com/microsoft/vscode/wiki/Roadmap), [monthly iteration plans](https://github.com/microsoft/vscode/wiki/Iteration-Plans), and our [endgame plans](https://github.com/microsoft/vscode/wiki/Running-the-Endgame). This source code is available to everyone under the standard [MIT license](https://github.com/microsoft/vscode/blob/main/LICENSE.txt).

## Visual Studio Code

<p align="center">
<img alt="VS Code in action" src="https://user-images.githubusercontent.com/35271042/118224532-3842c400-b438-11eb-923d-a5f66fa6785a.png">
</p>

[Visual Studio Code](https://code.visualstudio.com) is a distribution of the `Code - OSS` repository with Microsoft-specific customizations released under a traditional [Microsoft product license](https://code.visualstudio.com/License/).

[Visual Studio Code](https://code.visualstudio.com) combines the simplicity of a code editor with what developers need for their core edit-build-debug cycle. It provides comprehensive code editing, navigation, and understanding support along with lightweight debugging, a rich extensibility model, and lightweight integration with existing tools.

Visual Studio Code is updated monthly with new features and bug fixes. You can download it for Windows, macOS, and Linux on [Visual Studio Code's website](https://code.visualstudio.com/Download). To get the latest releases every day, install the [Insiders build](https://code.visualstudio.com/insiders).

## Contributing

There are many ways in which you can participate in this project, for example:

* [Submit bugs and feature requests](https://github.com/microsoft/vscode/issues), and help us verify as they are checked in
* Review [source code changes](https://github.com/microsoft/vscode/pulls)
* Review the [documentation](https://github.com/microsoft/vscode-docs) and make pull requests for anything from typos to additional and new content

If you are interested in fixing issues and contributing directly to the code base,
please see the document [How to Contribute](https://github.com/microsoft/vscode/wiki/How-to-Contribute), which covers the following:

* [How to build and run from source](https://github.com/microsoft/vscode/wiki/How-to-Contribute)
* [The development workflow, including debugging and running tests](https://github.com/microsoft/vscode/wiki/How-to-Contribute#debugging)
* [Coding guidelines](https://github.com/microsoft/vscode/wiki/Coding-Guidelines)
* [Submitting pull requests](https://github.com/microsoft/vscode/wiki/How-to-Contribute#pull-requests)
* [Finding an issue to work on](https://github.com/microsoft/vscode/wiki/How-to-Contribute#where-to-contribute)
* [Contributing to translations](https://aka.ms/vscodeloc)

## Feedback

* Ask a question on [Stack Overflow](https://stackoverflow.com/questions/tagged/vscode)
* [Request a new feature](CONTRIBUTING.md)
* Upvote [popular feature requests](https://github.com/microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Afeature-request+sort%3Areactions-%2B1-desc)
* [File an issue](https://github.com/microsoft/vscode/issues)
* Connect with the extension author community on [GitHub Discussions](https://github.com/microsoft/vscode-discussions/discussions) or [Slack](https://aka.ms/vscode-dev-community)
* Follow [@code](https://twitter.com/code) and let us know what you think!

See our [wiki](https://github.com/microsoft/vscode/wiki/Feedback-Channels) for a description of each of these channels and information on some other available community-driven channels.

## Related Projects

Many of the core components and extensions to VS Code live in their own repositories on GitHub. For example, the [node debug adapter](https://github.com/microsoft/vscode-node-debug) and the [mono debug adapter](https://github.com/microsoft/vscode-mono-debug) repositories are separate from each other. For a complete list, please visit the [Related Projects](https://github.com/microsoft/vscode/wiki/Related-Projects) page on our [wiki](https://github.com/microsoft/vscode/wiki).

## Bundled Extensions

VS Code includes a set of built-in extensions located in the [extensions](extensions) folder, including grammars and snippets for many languages. Extensions that provide rich language support (code completion, Go to Definition) for a language have the suffix `language-features`. For example, the `json` extension provides coloring for `JSON` and the `json-language-features` extension provides rich language support for `JSON`.

## Development Container

This repository includes a Visual Studio Code Dev Containers / GitHub Codespaces development container.

* For [Dev Containers](https://aka.ms/vscode-remote/download/containers), use the **Dev Containers: Clone Repository in Container Volume...** command which creates a Docker volume for better disk I/O on macOS and Windows.
* If you already have VS Code and Docker installed, you can also click [here](https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/microsoft/vscode) to get started. This will cause VS Code to automatically install the Dev Containers extension if needed, clone the source code into a container volume, and spin up a dev container for use.

* For Codespaces, install the [GitHub Codespaces](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces) extension in VS Code, and use the **Codespaces: Create New Codespace** command.

Docker / the Codespace should have at least **4 Cores and 6 GB of RAM (8 GB recommended)** to run a full build. See the [development container README](.devcontainer/README.md) for more information.

## Code of Conduct

This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.

## License

Copyright (c) Microsoft Corporation. All rights reserved.

Licensed under the [MIT](LICENSE.txt) license.
# FITVEST — Preview local (rápido)

Este repositório é uma prévia estática de uma única página: `index.html` (pt-BR).
Use este projeto para visualizar rapidamente o site localmente ou preparar pequenas edições.

## Como visualizar localmente

1) Abrir diretamente no navegador (Windows PowerShell):

```powershell
Set-Location -Path 'C:\Users\Usuario\OneDrive\Desktop\FITVEST'
Copy link

Copilot AI Oct 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hardcoded absolute paths like 'C:\Users\Usuario\OneDrive\Desktop\FITVEST' make the documentation non-portable. Replace with relative path instructions or use $PSScriptRoot in the PowerShell examples.

Copilot uses AI. Check for mistakes.
Start-Process 'index.html'
```

2) Usando Python (se estiver disponível):

```powershell
Set-Location -Path 'C:\Users\Usuario\OneDrive\Desktop\FITVEST'
python -m http.server 8000
# então abra http://localhost:8000/
```

3) Alternativa PowerShell (sem Python) — script incluído `serve.ps1`:

```powershell
Set-Location -Path 'C:\Users\Usuario\OneDrive\Desktop\FITVEST'
.\serve.ps1 # porta padrão 8000
.\serve.ps1 -Port 8080
# abra http://localhost:8000/ ou a porta escolhida
```

Dica: a extensão "Live Server" do VS Code também funciona bem para edição/preview rápidos.

## Convenções rápidas

- Idioma: conteúdo em Português do Brasil (`pt-BR`). Mantenha consistência nas traduções.
- Acessibilidade: preserve ou melhore atributos ARIA já existentes (ex.: `aria-label` no link principal).
- Estilo: atualmente o CSS está embutido em `index.html`. Se extrair, prefira `assets/css/style.css` e mantenha a aparência.
- Não altere o link de produção: `https://www.fitvestmoda.com.br` — não substitua ou redirecione sem uma issue/PR explícita.

## Commits e PRs

- Mantenha commits pequenos e focados. Exemplo de mensagem:

```
fix(html): ajustar texto de link e aria-label
```

- Em PRs, inclua uma captura de tela ou uma breve nota explicando as mudanças visuais no `index.html`.

## Quando expandir o projeto

Antes de introduzir frameworks (React, Vite, etc.) abra uma issue propondo a mudança e aguarde aprovação de um revisor humano — este repositório é intencionalmente minimalista.

## Mais documentação

Veja também: `.github/copilot-instructions.md` — instruções para agentes/colaboradores (bilíngue).


Se quiser, posso também criar pequenos exemplos: extrair o CSS para `assets/css/style.css` e atualizar `index.html`, ou adicionar um `serve` npm/script se preferir Node.js. Escolha o próximo passo.

## Rodando o projeto Next.js localmente (opcional)

Se você quiser experimentar a versão mínima do Next.js incluída aqui:

```powershell
# instalar dependências (uma vez)
npm install

# rodar em desenvolvimento
npm run dev
```

Isto cria um app Next minimal que inclui o `src/app/page.tsx` e stubs de componentes. Use esta versão só se você pretende transformar o repositório em um app React/Next.

## Firebase (inicialização cliente)

O repositório inclui um inicializador cliente mínimo em `src/firebase/index.tsx` que usa variáveis de ambiente públicas do Next (`NEXT_PUBLIC_FIREBASE_*`).

Variáveis esperadas (exemplo):

- NEXT_PUBLIC_FIREBASE_API_KEY
- NEXT_PUBLIC_FIREBASE_AUTH_DOMAIN
- NEXT_PUBLIC_FIREBASE_PROJECT_ID
- NEXT_PUBLIC_FIREBASE_STORAGE_BUCKET
- NEXT_PUBLIC_FIREBASE_MESSAGING_SENDER_ID
- NEXT_PUBLIC_FIREBASE_APP_ID

NUNCA comite chaves privadas ou credenciais sensíveis no repositório. Use o sistema de variáveis do seu provedor/CI para armazenar segredos.


## DNS (informações de deploy)

Servidores de nome usados pelo deploy/registro do domínio:

- Servidor DNS Primário: `ns1.locaweb.com.br`
- Servidor DNS Secundário: `ns2.locaweb.com.br`
- Servidor DNS Terciário: `ns3.locaweb.com.br`

Inclua estas entradas apenas em alterações aprovadas pelo time de infraestrutura ou pelo responsável do domínio.

## Privacidade e Telemetria

Este repositório inclui integração opcional com Google Analytics (gtag) e Google Tag Manager (GTM).
- Por padrão os snippets estão desativados em `assets/js/analytics.js` (variável `ENABLE_ANALYTICS = false`).
- Só habilite o rastreamento em deploys de produção com aprovação explícita da equipe responsável e garantindo conformidade com LGPD/GDPR.
- Se ativar, atualize a documentação do deploy e garanta aviso/consentimento aos usuários conforme as políticas aplicáveis.

### Como ativar/desativar (procedimento controlado)

Há um utilitário PowerShell para alternar a flag de telemetria em `assets/js/analytics.js`.

```powershell
# Ativar analytics (APENAS em deploy de produção e com aprovação)
.\scripts\enable_analytics.ps1 -Enable $true

# Desativar analytics
.\scripts\enable_analytics.ps1 -Enable $false
```

O script cria um backup do arquivo `analytics.js` antes da alteração. Use este utilitário somente em pipelines de release aprovados.

## Checklist de deploy (rápido)

Antes de publicar alterações na zona DNS ou apontar o domínio, siga estes passos mínimos:

- Verifique os registros atuais: A/AAAA/CNAME/MX/TXT usando `dig` ou `nslookup`.
- Reduza temporariamente o TTL (ex.: 300s) algumas horas antes da mudança para acelerar rollback.
- Atualize apenas os registros aprovados (A/AAAA para o host, CNAMEs conforme necessário).
- Confirme que os nameservers (`ns1/2/3.locaweb.com.br`) estão corretos na interface do registrador.
- Verifique certificação TLS/SSL: gere/renove certificados (Let's Encrypt/ACME ou provedor) e valide o HTTPS.
- Após aplicar, monitore a propagação (dig/nslookup apontando para diferentes resolvers, e ferramentas online de propagação).
- Teste o site em HTTP/HTTPS, em múltiplos dispositivos/rede, e verifique cabeçalhos e redirecionamentos.
- Se algo der errado, use o TTL reduzido para reverter rapidamente aos valores anteriores e notifique o time.

Notas: Este é um checklist mínimo. Para alterações maiores (subdomínios, uso de CDN, failover), siga o runbook de infraestrutura do time.
25 changes: 25 additions & 0 deletions index.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
<!DOCTYPE html>
<html lang="pt-BR">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Visualizando o Site</title>
<link rel="stylesheet" href="assets/css/style.css">
<!-- Analytics are centralized in assets/js/analytics.js and disabled by default -->
<script defer src="assets/js/analytics.js"></script>
</head>
<body>
<!-- Google Tag Manager (noscript) -->
<!-- Keep this noscript iframe if you enable GTM in production; it can be removed if analytics remain disabled -->
<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-PVXBBP6P" height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
<!-- End Google Tag Manager (noscript) -->
<h1>Link para o Site:</h1>
<p>Clique no botão abaixo para abrir o site:</p>
<a href="https://www.fitvestmoda.com.br" target="_blank" aria-label="Abrir site no navegador">
Abrir no Navegador
</a>
<footer>
© 2025 - Desenvolvido por DeividCurcio
</footer>
</body>
</html>
5 changes: 5 additions & 0 deletions next-env.d.ts
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
/// <reference types="next" />
/// <reference types="next/types/global" />
/// <reference types="next/image-types/global" />

// NOTE: This file should not be edited
Loading