How devtecnologirl/portifolio-pessoal works
Project type and purpose
• This is a single‐page application (SPA) built with Vue.js (via Vue CLI) and Quasar variables, intended as a personal portfolio website.
• Its role is purely front-end: presenting your resume (PDF), projects, experience, contact form, etc., all statically hosted.
File structure
• Top-level “3.0/meu-portifolio” contains the Vue project created by vue create.
• “public/” holds static assets (index.html, cvcamilly.pdf).
• “src/” contains:
• App.vue – root component
• main.js – application entry point
• assets/ – global CSS files (base.css, main.css)
• components/ – Vue UI components (MainHeader, MyAbout, MyProjects, etc.)
• stores/ – state management modules (navigation.js, splash.js)
• Configuration files: package.json (dependencies), vite.config.js (build config), jsconfig.json (editor paths), .gitignore, .vscode settings.
Review the README
• Instructs installing Vue CLI, creating the project, and running npm run serve.
• No backend or API calls are defined here; it’s a static SPA.
Main components and their relationships
a. Developer workstation – uses Git + Node/npm + Vue CLI →
b. Source code (src/, public/) →
c. Vite build process (vite.config.js) bundles JS/CSS/assets →
d. Production output (dist/) →
e. Static web server/CDN (e.g., GitHub Pages, Netlify) →
f. Client browser loads index.html →
g. main.js bootstraps Vue app →
h. App.vue + child components render UI →
i. Components read/write state via stores (navigation, splash) →
j. User interacts, navigates to sections (MyAbout, MyProjects, MyContact).
Architectural patterns and design principles
• Component-based UI (Vue single-file components).
• Unidirectional data flow via centralized stores.
• Separation of concerns:
• Presentation layer (Vue components + CSS)
• State layer (stores)
• Build layer (Vite)
• Deployment layer (static hosting).
• Convention-based routing (via component names and conditional rendering, not a full router).
Technologies, frameworks, and libraries
• Vue.js 3 (CLI, single-file components)
• Vite (fast bundler/dev server)
• Quasar variables (SASS/CSS theming)
• npm (package management)
• Git (version control)
Essential elements
• Clear, descriptive labels on every component and pipeline stage.
• Optional: note version control (.git) and local dev server (npm run serve).