kriasoft/Folder-Structure-Conventions: Folder / directory structure options and naming conventions for software projects
github.com · 663 words · saved by 1 readers
Folder / directory structure options and naming conventions for software projects
Folder structure options and naming conventions for software projects A typical top-level directory layout . ├── build # Compiled files (alternatively `dist`) ├── docs # Documentation files (alternatively `doc`) ├── src # Source files (alternatively `lib` or `app`) ├── test # Automated tests (alternatively `spec` or `tests`) ├── tools # Tools and utilities ├── LICENSE └── README.md Use short lowercase names at least for the top-level files and folders except LICENSE, README.md Source files The actual source files of a software project are usually stored inside the src folder.…
saved by
related reading
- GitHub - golang-standards/project-layout: Standard Go Project Layoutgithub.com
- Agentationagentation.dev
- Impeccable: The missing upgrade to Anthropic's impeccable skillimpeccable.style
- GitHub · Change is constant. GitHub keeps you ahead.github.com
- Tao of React - Software Design, Architecture & Best Practices | Alex Kondovalexkondov.com
- Agentationagentation.com
- v0 by Vercel - Build Full-Stack Web Apps with AIv0.dev
- Bolt AI builder: Websites, apps & prototypesbolt.new
- Subframe – The AI design tool built for codesubframe.com
- GitHub - abhivaikar/howtheytest: A collection of public resources about how software companies test their softwaregithub.com
- GitHub - jackyzha0/quartz: 🌱 a fast, batteries-included static-site generator that transforms Markdown content into fully functional websitesgithub.com
- next.js/examples at canary · vercel/next.jsgithub.com