How evavic44/portfolio-ideas works
• Repository & Version Control: The source code is hosted on GitHub. Include elements such as the repository itself, the “.all-contributorsrc”, “.gitattributes”, “.gitignore”, and contribution documents (CODE_OF_CONDUCT, CONTRIBUTING, LICENSE).
• Documentation/Content Module: The “docs” directory holds the markdown content and the VitePress configuration (within docs/.vitepress). This is the “frontend” content component that renders the static site.
• Build Process & Static Site Generation: Indicate that VitePress is used to process the markdown into a static site. Show the “package.json”, “package-lock.json”, and an “extract.sh” script (which may be used to update or extract portfolio data) as parts of the build tools.
• CI/CD Pipeline: Represent GitHub Actions workflows (found under .github/workflows, for example, “autodeploy.yml”) that automatically build, test (using husky pre-commit hooks in the “.husky” folder), and deploy the site.
Relationships and data flow
• Commits and pull requests flowing from contributors into the GitHub repository.
Design principles and external integrations
• That a static site generation pattern is used, which separates content (markdown files and docs) from build and deployment.
• That the repository adopts community-driven contributions; label elements for issue/templates and all-contributors.
• If desired, include annotations for design patterns (e.g., “Documentation-as-Code”, “CI/CD Pipeline”, “Pull Request-Based Contributions”).