nachtigall.dev/nachtigall.dev
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
main
nachtigall.dev/README.md
vikingowl d30266248c chore: remove unused components, utilities, and dependencies 
- Removed unused components (`components.vue`, `Markup.vue`, `index.vue`, etc.) and related styles.
- Deleted obsolete utilities (`api.ts`, `componentCatalog.ts`).
- Cleared out dependencies in `package-lock.json` related to unused functionalities.
2025-09-27 01:03:01 +02:00

1.8 KiB
Raw Permalink Blame History

nachtigall.dev

A Vue 3 + Vuetify playground for prototyping component ideas and documenting reusable UI patterns.

Getting Started

  • Install dependencies with yarn install.
  • Start the development server with yarn dev (Vite).
  • Run the Vitest-powered unit suite with yarn test:unit.
  • Trigger the placeholder end-to-end command with yarn test:e2e until a real harness lands.
  • Lint the codebase with yarn lint.
  • Type-check and build the production bundle with yarn build.

Project Layout

  • src/main.ts bootstraps the Vue application and registers plugins.
  • src/layouts/ contains layout shells that wrap routed pages.
  • src/pages/ defines the routed views, including the new projects, experience, and contact flows generated automatically by unplugin-vue-router.
  • src/components/ holds global UI components as well as the portfolio building blocks in portfolio/.
  • src/composables/ exposes Composition API helpers, such as the portfolio data accessors.
  • src/services/ centralises domain logic and data sets, including portfolio.ts.
  • src/stores/ defines Pinia stores.
  • src/types/ contains ambient TypeScript declarations.

Portfolio Content

The home, projects, experience, and contact screens are populated from src/services/portfolio.ts via the usePortfolio composable. Update those data sets to surface new case studies, achievements, or contact options.

Styling Guidelines

  • Prefer Vuetify utility classes for spacing, colour, and typography.
  • Where custom rules are required, add them in the scoped <style> blocks of the relevant components.
  • Inline styles are intentionally avoided.

Tooling

  • ESLint + Prettier enforce code style via npm run lint.
  • TypeScript runs in strict mode. Fix type errors surfaced by npm run build before committing.