diff --git a/README-template.md b/README-template.md new file mode 100644 index 0000000..49e6b70 --- /dev/null +++ b/README-template.md @@ -0,0 +1,91 @@ +# challenge-landing-page + + + +## Getting started + +To make it easy for you to get started with GitLab, here's a list of recommended next steps. + +Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! + +## Add your files + +- [ ] [Create](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files +- [ ] [Add files using the command line](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: + +``` +cd existing_repo +git remote add origin https://gitlab.com/m3-academy/fase-01/challenge-landing-page.git +git branch -M main +git push -uf origin main +``` + +## Integrate with your tools + +- [ ] [Set up project integrations](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/user/project/integrations/) + +## Collaborate with your team + +- [ ] [Invite team members and collaborators](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/user/project/members/) +- [ ] [Create a new merge request](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) +- [ ] [Automatically close issues from merge requests](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) +- [ ] [Automatically merge when pipeline succeeds](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) + +## Test and Deploy + +Use the built-in continuous integration in GitLab. + +- [ ] [Get started with GitLab CI/CD](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/ci/quick_start/index.html) +- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/user/application_security/sast/) +- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/topics/autodevops/requirements.html) +- [ ] [Use pull-based deployments for improved Kubernetes management](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/user/clusters/agent/) + +*** + +# Editing this README + +When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://www.makeareadme.com/) for this template. + +## Suggestions for a good README +Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. + +## Name +Choose a self-explaining name for your project. + +## Description +Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. + +## Badges +On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. + +## Visuals +Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. + +## Installation +Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. + +## Usage +Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. + +## Support +Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. + +## Roadmap +If you have ideas for releases in the future, it is a good idea to list them in the README. + +## Contributing +State if you are open to contributions and what your requirements are for accepting them. + +For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. + +You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. + +## Authors and acknowledgment +Show your appreciation to those who have contributed to the project. + +## License +For open source projects, say how it is licensed. + +## Project status +If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers. + diff --git a/README.md b/README.md index 49e6b70..262c108 100644 --- a/README.md +++ b/README.md @@ -1,91 +1,179 @@ -# challenge-landing-page +# M3 Amazing Landing page | Challenge 1 - M3Academy + +Projeto criado e planejado pela M3Academy, com o intuito de mostrar nossas capacidades, e fazer a gente conhecer o seu ambiente de desenvolvimento, para trabalho em equipe, tendo versionamento de código, responsabilidade, prazo de entrega, boas práticas, demostranto o seu ambiente de trabalho em equipe e desenvolvimento em grupo. + +## Contents + +|Contents |Available | +|------------------------------------------------------------------------|----------| +|[👀 Overview 👀](#overview) |Yes | +|[🎯 The challenge 🎯](#the-challenge) |Yes | +|[📽️ Visuals 📽️](#visuals) |Yes | +|[🧪 Links para Demos 🧪](#links) |Yes | +|[👟 My process 👟](#my-process) |Yes | +|[📖 What I Learned 📖](#what-i-learned) |Yes | +|[🏗️ Technologies 🏗️](#technologies) |Yes | +|[🏭 Continuous Development 🏭](#continuous-development) |Yes | +|📦 Resources 📦 |Not | +|[📥 Installation 📥](#installation) |Yes | +|🕹️ Usage 🕹️ |Yes | +|[💙 Support 💙](#support) |Yes | +|[💙 Contributing 💙](#contributing) |Yes | +|[✍️ Author ✍️](#author) |Yes | +|[📞 Contact 📞](#contact) |Yes | +|[🎊 Acknowledgment 🎊](#acknowledgment) |Yes | +| | | +## 👀 Overview + +### 🎯 The Challenge + +**DATA ENTREGA**: 13/10/2022 - Antecipado + +A branch que será corrigida será a branch principal (main ou master), então, após terminar o desenvolvimento do desafio, faça o pull request das branchs para a branch principal (main ou master). Se não estiver tudo na branch correta, não será considerado. + +Os Requisitos cobrados serão: + +- [x] Repositório PRIVADO no gitTea; +- [x] NÃO DEVE ser usado javaScript no desenvolvimento; +- [x] Quantidade de commits feitos deve ser maior que 10; +- [x] HTML e CSS devem considerar a performance da pagina (código limpo, sem repetições desnecessárias) +- [x] Entrega deve ser feita conforme é informado no vídeo - no local de entrega DESTE desafio, você irá colocar a URL do SEU repositório com TODA a Landingpage desenvolvida (o professor que for corrigir irá fazer o clone do seu repositório para corrigir) e irá aguardar a nota e o link da tabela de correção com os erros cometidos e dicas de como ajustar. TRABALHOS ENTREGUES POR EMAIL NÃO SERÃO ACEITOS. CONFIRA O SEU REPOSITÓRIO ANTES DE ENTREGAR, faça o clone novamente e confira se tudo está correto. + +Avisos: + +- Repositórios VAZIOS terão nota ZERO e o aluno poderá ser eliminado imediatamente do treinamento (no dia seguinte a data de entrega será conferido cada repositório). +#### Developer Challenge + +- [x] Semântica do HTML; +- [x] Uso de Conventional Commits e GitFlow para fazer as branchs e os commits; +- [x] Layout deve ser igual ao do figma fornecido acima e deve ser feito por completo; +- [x] CSS com uso de media query (pode fazer uso de SASS se tiver familiaridade); +- [x] A pagina deve se adaptar a TODOS os tamanhos de tela (telas maiores que 2500px, desktop (entre 2500 e 1025px), tablet e mobile (1024px até 280px - Galaxy Fold - Chrome) - DICA: usem medidas em porcentagem quando necessário. + +[<<< TOP](#contents) + +## 📽 Visuals + +### 📽 Screenshot + +![Image](./docs/images/screenshot.png) + +[<<< TOP](#contents) + +### 🧪 Links + +- URL da solução: [LINK](sss) +- Demostrativo da solução: [LINK](sss) + +[<<< TOP](#contents) + +## 👟 My process + +### 🏗 Technologies + +- HTML +- CSS + +[<<< TOP](#contents) + +### 📖 What I Learned + +Eu aprendi, a ajudar pessoas com problemas de progamação, gostei bastante do meu desenvolvimento, ajudar quem precisa e gratificante, meu desenvolvimento foi tranquilo acredito que esse é somente o aquecimento, creio que ainda tenho muito a aprender, todos contéudos da M3 Academy são um dos melhores que eu já conheci, acredito que aprenderei muitos conhecimentos novos. Estou ansioso para mais contéudos. + +[<<< TOP](#contents) + +### 🏭 Continuous development + +Quero revisar o que aprendi ao longo do tempo, conhecer como uma empresa realmente funciona, sempre criei projetos sozinhos digo que a melhor experiencia em auxiliar pessoas e ajuda-las é algo muito bonito visto que sempre fui sozinho somente eu e minhas músicas, apesar de estar a um tempo na área de programação acredito que ainda terei muito o que aprender. + +[<<< TOP](#contents) +## 📥 Installation +Requisitos: -## Getting started +- Baixar o VSCode (Visual Studio Code). (Recomendado) +- Git (Versionamento de código). (Obrigatorio) -To make it easy for you to get started with GitLab, here's a list of recommended next steps. +### 📥 VSCODE -Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! +O VSCode(Visual Studio Code) é um IDE (Integrated Development Environment) Ambiente de Desenvolvimento Integrado, +Este ambiente proposto pelo software VSCode, E muito importante para desenvolvedores das mais diferenciadas áres, como Desenvolvimento Web, Desenvolvimento de software, etc. -## Add your files +Baixe de Acordo com seu SO (Sistema Operacional). -- [ ] [Create](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files -- [ ] [Add files using the command line](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: +Como Instalar o VSCode. +- [Site Oficial](https://code.visualstudio.com/) -``` -cd existing_repo -git remote add origin https://gitlab.com/m3-academy/fase-01/challenge-landing-page.git -git branch -M main -git push -uf origin main +![VSCODE Screenshot Site Oficial](./docs/images/vscode-official-home.png) + +AVISO: Não baixe o software de sites estrangeiros, baixe direto do site oficial. +### 📥 Git + +O Git é um sistema de versionamento de código que deve ser utilizado para clonagem de repositorios, sendo assim o Git tem que estar instalado no computador de clonagem no repositorio. + +Baixe de Acordo com seu SO (Sistema Operacional). + +Como Instalar o Git. + +- [Site Oficial](https://git-scm.com/) + +![GIT Screenshot Site Oficial](./docs/images/git-official-home.png) + +AVISO: Não baixe o software de sites estrangeiros, baixe direto do site oficial + +### 📥 Extensions + +No VSCode temos varias extenções para ajudar em nosso desenvolvimento do dia a dia, No caso citaremos algumas. + +- [Live Server](https://marketplace.visualstudio.com/items?itemName=ritwickdey.LiveServer) + - Extenção para desenvolvimento Web, que permite a criação de um "servidor" para ambiente de desenvolvimento permitindo a manutenção dos elementos da páginas e testes de classes, cores, tamanhos, etc. Ela também comtribui com agilidade para o desenvolvimeto web pertimitindo uma economia de tempo. (Uso Opcional) + +- [Material Icon](https://marketplace.visualstudio.com/items?itemName=PKief.material-icon-theme) + - Essa extenção ajuda a torna mais legiveis os arquivos e pastas do projeto (Uso Opcional) + +## 🕹️ Usage + +`Windows` / `Mac` / `Linux` + +Abra seu `cmd`/`bash`/`shell` copie e cole o código abaixo no seu `cmd`/`bash`/`shell`. + +```shell + git clone https://gitea.ecommercetools.com.br/HenriqueSantosSantana/m3-amazing-landing-page.git + cd challenge-landing-page-henrique-santos-santana/ + code . ``` -## Integrate with your tools +AVISO: Git deve estar instalado na máquina junto com o VSCODE, caso sua IDE não for o VSCODE vá diretamente por meio de seu `cmd`/`bash`/`shell` manualmente, ou utilize a interface para chegar a pasta que foi clonado o repositorio, e entre dentro do projeto. -- [ ] [Set up project integrations](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/user/project/integrations/) +Caso tenha baixado as extenções no VSCODE, somente clique no arquivo index.html, ira abrir um menu abaixo do seu mouse, clique na opção `Open with Live Server`. Após clicar você será redirecionado para o seu navegador padrão com o projeto aberto. -## Collaborate with your team +![Open with Live Server](./docs/images/vscode-open-menu-liveserver.png) -- [ ] [Invite team members and collaborators](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/user/project/members/) -- [ ] [Create a new merge request](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) -- [ ] [Automatically close issues from merge requests](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) -- [ ] [Automatically merge when pipeline succeeds](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) +## 💙 Support -## Test and Deploy +Estou a qualquer momento disponivel, para tirar suas duvidas sobre o desafio somente me chame no discord :3 -Use the built-in continuous integration in GitLab. +## 💙 Contributing -- [ ] [Get started with GitLab CI/CD](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/ci/quick_start/index.html) -- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/user/application_security/sast/) -- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/topics/autodevops/requirements.html) -- [ ] [Use pull-based deployments for improved Kubernetes management](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://docs.gitlab.com/ee/user/clusters/agent/) +Está disponivel para contribuições -*** +## ✍ Author -# Editing this README +- GitHub : [Henrique Santos Santana](https://github.com/HenriqueSSan/) +- Linkedin : [Henrique Santos Santana](https://linkedin.com/in/henrique-santos-santana) -When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://gitlab.com/-/experiment/new_project_readme_content:a980a0e1508cd91a06bf888abbfadab2?https://www.makeareadme.com/) for this template. +[<<< TOP](#contents) -## Suggestions for a good README -Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. +## 📞 Contact -## Name -Choose a self-explaining name for your project. +- Email: [hsstudentwork@gmail.com](https://mail.to:hsstudentwork@gmail.com) -## Description -Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. +[<<< TOP](#contents) -## Badges -On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. +## 🎊 Acknowledgment -## Visuals -Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. +Agradecimentos a Minha familia por me apoiarem, Obrigado a M3Academy, Caroline .V Moran e Marcia Leal por me selecionarem para algo tão grande 💙. -## Installation -Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. - -## Usage -Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. - -## Support -Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. - -## Roadmap -If you have ideas for releases in the future, it is a good idea to list them in the README. - -## Contributing -State if you are open to contributions and what your requirements are for accepting them. - -For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. - -You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. - -## Authors and acknowledgment -Show your appreciation to those who have contributed to the project. - -## License -For open source projects, say how it is licensed. - -## Project status -If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers. +[<<< TOP](#contents) diff --git a/assets/css/main.css b/assets/css/main.css new file mode 100644 index 0000000..6200395 --- /dev/null +++ b/assets/css/main.css @@ -0,0 +1,421 @@ +/* Mas legível quais tags eu declarei com propriedades padrão */ + +/* reset all tags */ +* { + margin: 0; + padding: 0; + box-sizing: border-box; +} + +img { + display: block; + max-width: 100%; + height: auto; +} + +/* Mas organização de cores, estilos, fonts, espaçamentos,etc. isso é um arquivo de configuração*/ +:root { + --clr-black: #000; + --clr-gray-100: #BDBDBD; + + --bg-clr-black: #000; + --bg-clr-gray: #E0E0E0; + --bg-clr-white: #fff; + + --body-family: "Inter", Arial, Helvetica, sans-serif; + --title-family: "Inter", Arial, Helvetica, sans-serif; + + /*----------------------*\ + = Volatile Variables = + \*----------------------*/ + --hs-flow-space: 1rem; + --hs-grid-space: 1rem; + --hs-flex-space: 1rem; +} + +/* font styles for all body tags */ + +body * { + font-family: var(--body-family); +} + + +/* font styles for page titles */ +h1, +h2, +h3, +h4, +h5, +h6, +.title { + font-family: var(--title-family); +} + +/* a metodologia que vou usar será CUBE CSS <3*/ + +/* started styles */ + +/*--------*\ += HEADER = +\*--------*/ +.l-header { + display: flex; + align-items: center; + justify-content: center; + width: 100%; + padding: 1.875rem 1rem; +} + +.header-logo { + display: flex; +} + +/*-------------*\ += MAIN BANNER = +\*-------------*/ +.main-banner-image { + width: 100%; + height: auto; +} + +/*-------------*\ += INFORMATION = +\*-------------*/ +.information { + display: flex; + align-items: center; + justify-content: center; + flex-direction: column; + gap: 4rem; + padding: 4.625rem 1.875rem 90px; +} + +.information-texts { + text-align: center; +} + +.information-subtitle, +.information-description { + line-height: 1.5rem; +} + +.information-subtitle { + font-weight: 400; +} + +.information-title { + font-weight: 500; + line-height: 3rem; +} + +/*----------*\ += SERVICES = +\*----------*/ +.services { + padding-bottom: 5.625rem; +} + +.services-container { + --hs-flex-space: 1.25rem; + --hs-flow-space: 1.75rem; + + padding: 0 1.625rem; +} + +.services-container, +.card { + display: flex; + align-items: center; + justify-content: center; +} + +.card { + flex-direction: column; + width: 100%; + min-height: 288px; + padding: 2.25rem 1.625rem 1.75rem; +} + +.card-image { + width: 34.5%; + height: auto; + min-width: 103px; +} + +/*---------*\ += GALLERY = +\*---------*/ +.gallery { + --hs-grid-space: 1.5rem 0.875rem; + + padding: 0 1.5rem; + margin-bottom: 7rem; +} + +.gallery-container { + position: relative; + grid-template-columns: repeat(2, 1fr); + justify-content: center; + transform: translateY(2rem); +} + +.gallery-image, +.gallery-image img { + width: 100%; +} + + +.gallery-image-3 { + grid-column: 1/2 span; +} + +/*----------*\ += FEATURES = +\*----------*/ +.features { + padding: 0 1.5rem; +} + +.features-container { + --hs-flex-space: 1rem; + + flex-direction: column; + width: 100%; + padding-bottom: 6rem; + margin: 0; +} + +.features .card { + width: 100%; + min-height: 332px; +} + +/*------*\ += BLOG = +\*------*/ +.blog { + --hs-flex-space: 3.125rem; + + width: 100%; + padding-bottom: 5.5rem; +} + +.blog-images-image { + width: 100%; +} + +.blog-article { + padding: 0 1.5rem; +} + +.blog-title { + font-weight: 500; + font-size: 1.5rem; +} + +/*--------*\ += FOOTER = +\*--------*/ +.footer { + flex-direction: column; + padding: 2.375rem 0; +} + +/*CUBE CSS styles*/ + +/*-------------*\ += COMPOSITION = +\*-------------*/ +.flow *+* { + margin-top: var(--hs-flow-space); +} + +.grid-box { + display: grid; + gap: var(--hs-grid-space); +} + +.flex-box { + display: flex; + gap: var(--hs-flex-space); +} + +.flex-box[data-type="reversed"] { + flex-direction: column-reverse; +} + +/*-------*\ += UTILS = +\*-------*/ +.center { + align-items: center; + justify-content: center; +} + +.text-upper { + text-transform: uppercase; +} + +.text-center { + text-align: center; +} + +.box-shadow { + box-shadow: 0px 4px 20px rgba(0, 0, 0, 0.23); +} + +.clr-gray-100 { + color: var(--clr-gray-100); +} + +.bg-clr-black { + background-color: var(--bg-clr-black); +} + +.bg-clr-gray { + background-color: var(--bg-clr-gray); +} + +/*---------------*\ += MEDIA QUERIES = +\*---------------*/ +@media only screen and (max-width: 1024px) { + .services-container { + flex-direction: column; + } + + .image-mobile { + display: flex; + } + + .image-desktop { + display: none; + } +} + +/*--------------------------------------*\ += MEDIA QUERIES LARGE DEVICES 1025px > = +\*--------------------------------------*/ +@media screen and (min-width:1025px) { + + .features, + .gallery { + padding: 0 4.5rem; + } + + .information-texts, + .services, + .blog-article, + .blog-images { + margin: 0 auto; + } + + .information { + padding: 4.675rem 0 9.875rem; + gap: 4.675rem; + } + + .information-texts { + width: 40.5%; + text-align: initial; + } + + .information-title, + .information-subtitle { + text-align: center; + } + + .information-title { + font-size: 200%; + margin-bottom: 1.75rem; + } + + .information-subtitle { + line-height: 2rem; + } + + .information-image { + width: 17%; + height: auto; + } + + .information-image img { + width: 100%; + } + + .services { + width: 57%; + } + + .services-container { + padding: 0; + } + + .services .card { + width: 34%; + } + + .gallery { + --hs-grid-space: 2.5rem; + } + + .gallery-container { + grid-template-columns: repeat(3, 1fr); + transform: translateY(4rem); + } + + .gallery-image { + min-height: 530px; + } + + .gallery-image-3 { + grid-column: auto; + } + + .features-container { + flex-direction: row; + padding-bottom: 6.75rem; + } + + .card-image { + width: 29%; + height: auto; + } + + .blog { + padding-bottom: 7.25rem; + } + + .blog-title { + font-size: 2rem; + } + + .blog-images-image { + margin: 0; + } + + .blog .flex-box[data-type="reversed"] { + flex-direction: column; + } + + .blog-article { + width: 30.5%; + } + + .blog-description { + line-height: 1.5rem; + } + + .blog-images { + width: 71%; + height: auto; + } + + .image-mobile { + display: none; + } + + .image-desktop { + display: flex; + } +} \ No newline at end of file diff --git a/assets/images/blog-desktop.jpg b/assets/images/blog-desktop.jpg new file mode 100644 index 0000000..bc55059 Binary files /dev/null and b/assets/images/blog-desktop.jpg differ diff --git a/assets/images/blog-mobile.jpg b/assets/images/blog-mobile.jpg new file mode 100644 index 0000000..cf8d7ae Binary files /dev/null and b/assets/images/blog-mobile.jpg differ diff --git a/assets/images/facebook-logo.svg b/assets/images/facebook-logo.svg new file mode 100644 index 0000000..061ff85 --- /dev/null +++ b/assets/images/facebook-logo.svg @@ -0,0 +1,3 @@ + + + diff --git a/assets/images/full-logo.svg b/assets/images/full-logo.svg new file mode 100644 index 0000000..698965a --- /dev/null +++ b/assets/images/full-logo.svg @@ -0,0 +1,9 @@ + + + + + + + + + diff --git a/assets/images/gallery-1.jpg b/assets/images/gallery-1.jpg new file mode 100644 index 0000000..b715a4d Binary files /dev/null and b/assets/images/gallery-1.jpg differ diff --git a/assets/images/gallery-2.jpg b/assets/images/gallery-2.jpg new file mode 100644 index 0000000..5570225 Binary files /dev/null and b/assets/images/gallery-2.jpg differ diff --git a/assets/images/gallery-3.jpg b/assets/images/gallery-3.jpg new file mode 100644 index 0000000..1ced302 Binary files /dev/null and b/assets/images/gallery-3.jpg differ diff --git a/assets/images/handle-coin.svg b/assets/images/handle-coin.svg new file mode 100644 index 0000000..ea11a3d --- /dev/null +++ b/assets/images/handle-coin.svg @@ -0,0 +1,6 @@ + + + + + + diff --git a/assets/images/information-image.png b/assets/images/information-image.png new file mode 100644 index 0000000..e3a04a9 Binary files /dev/null and b/assets/images/information-image.png differ diff --git a/assets/images/instagram-logo.svg b/assets/images/instagram-logo.svg new file mode 100644 index 0000000..9221bab --- /dev/null +++ b/assets/images/instagram-logo.svg @@ -0,0 +1,5 @@ + + + + + diff --git a/assets/images/laptop.svg b/assets/images/laptop.svg new file mode 100644 index 0000000..7d13645 --- /dev/null +++ b/assets/images/laptop.svg @@ -0,0 +1,14 @@ + + + + + + + + + + + + + + diff --git a/assets/images/main-banner-desktop.jpg b/assets/images/main-banner-desktop.jpg new file mode 100644 index 0000000..2d7cc22 Binary files /dev/null and b/assets/images/main-banner-desktop.jpg differ diff --git a/assets/images/main-banner-mobile.jpg b/assets/images/main-banner-mobile.jpg new file mode 100644 index 0000000..553ceec Binary files /dev/null and b/assets/images/main-banner-mobile.jpg differ diff --git a/assets/images/money.svg b/assets/images/money.svg new file mode 100644 index 0000000..1090b7b --- /dev/null +++ b/assets/images/money.svg @@ -0,0 +1,14 @@ + + + + + + + + + + + + + + diff --git a/assets/images/phone-notificated.svg b/assets/images/phone-notificated.svg new file mode 100644 index 0000000..09c2c25 --- /dev/null +++ b/assets/images/phone-notificated.svg @@ -0,0 +1,6 @@ + + + + + + diff --git a/assets/images/shop.svg b/assets/images/shop.svg new file mode 100644 index 0000000..be82592 --- /dev/null +++ b/assets/images/shop.svg @@ -0,0 +1,13 @@ + + + + + + + + + + + + + diff --git a/assets/images/shopping-bag.svg b/assets/images/shopping-bag.svg new file mode 100644 index 0000000..d330029 --- /dev/null +++ b/assets/images/shopping-bag.svg @@ -0,0 +1,12 @@ + + + + + + + + + + + + diff --git a/assets/images/simple-logo.svg b/assets/images/simple-logo.svg new file mode 100644 index 0000000..d0656f5 --- /dev/null +++ b/assets/images/simple-logo.svg @@ -0,0 +1,9 @@ + + + + + + + + + diff --git a/assets/images/youtube-logo.svg b/assets/images/youtube-logo.svg new file mode 100644 index 0000000..de6f9a7 --- /dev/null +++ b/assets/images/youtube-logo.svg @@ -0,0 +1,3 @@ + + + diff --git a/docs/images/git-official-home.png b/docs/images/git-official-home.png new file mode 100644 index 0000000..5736b97 Binary files /dev/null and b/docs/images/git-official-home.png differ diff --git a/docs/images/screenshot.png b/docs/images/screenshot.png new file mode 100644 index 0000000..94d3e04 Binary files /dev/null and b/docs/images/screenshot.png differ diff --git a/docs/images/vscode-official-home.png b/docs/images/vscode-official-home.png new file mode 100644 index 0000000..b2d43a7 Binary files /dev/null and b/docs/images/vscode-official-home.png differ diff --git a/docs/images/vscode-open-menu-liveserver.png b/docs/images/vscode-open-menu-liveserver.png new file mode 100644 index 0000000..6424da6 Binary files /dev/null and b/docs/images/vscode-open-menu-liveserver.png differ diff --git a/index.html b/index.html new file mode 100644 index 0000000..e96e153 --- /dev/null +++ b/index.html @@ -0,0 +1,232 @@ + + + + + + + + + + + + + + + + + + + + + + M3 Amazing Landing page | Challenge 1 + + + +
+ +
+ + +
+ Um desktop aberto em um software de ambiente de desenvolvimento + Um desktop aberto em um software de ambiente de desenvolvimento +
+ + +
+
+

Lorem ipusm

+

Dolor sit amet

+

+ Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras euismod enim non dui + fringilla interdum. Curabitur ut tortor sed lacus egestas vulputate vel sit amet velit. + Nulla suscipit magna dui. +

+
+
+ três computadores juntos conectados por setas +
+
+ + +
+
+
+ shop +
+ Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras euismod enim non dui + fringilla interdum. +
+
+ +
+ shopping bag +
+ Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras euismod enim non dui + fringilla interdum. +
+
+ +
+ handle coin +
+ Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras euismod enim non dui + fringilla interdum. +
+
+
+
+ + +
+
+
+ notebook em mistura de cores vermelho,roxo,ciano, com fundo preto, visto de frente +
+ +
+ notebook em mistura de cores em vermelho,roxo,branco, com reflexo de cores, visto de cima +
+ +
+ notebook em cores vibrantes de tonalidades vermelhas laranja, vermelho, amarelo, visto de lateral +
+
+
+ + +
+
+
+ Dinheiro +
+ Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras euismod enim non dui + fringilla interdum. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras + euismod enim non dui fringilla interdum. +
+
+
+ Mão estendida com uma moeda +
+ Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras euismod enim non dui + fringilla interdum. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras + euismod enim non dui fringilla interdum. +
+
+
+ Um laptop aberto em umas de suas páginas do seu ecommerce +
+ Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras euismod enim non dui + fringilla interdum. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras + euismod enim non dui fringilla interdum. +
+
+
+ Um celular que contém suas notificações +
+ Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras euismod enim non dui + fringilla interdum. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras + euismod enim non dui fringilla interdum. +
+
+
+
+ + + +
+
+
+

Lorem ipsum dolor sit amet

+

+ Lorem ipsum dolor sit amet, consectetur adipiscing elit. Cras vulputate sapien non + libero faucibus interdum. In eget tincidunt ipsum. Quisque a tellus at lectus blandit + tempor. Ut tristique auctor mi eget hendrerit. Curabitur venenatis felis vitae sagittis + venenatis. Donec finibus turpis vitae lectus interdum rutrum vitae sed augue. +

+
+ +
+ fundo borado com um oculos em destaque refletindo uma tela de programação + fundo borado com um oculos em destaque refletindo uma tela de programação +
+
+
+ + + + +