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
- GitHub - mawrkus/js-unit-testing-guide: 📙 A guide to unit testing in Javascriptgithub.com
- A successful Git branching model >> nvie.comnvie.com
- Tao of React - Software Design, Architecture & Best Practices | Alex Kondovalexkondov.com
- GitHub - nayafia/lemonade-stand: A handy guide to financial support for open sourcegithub.com
- How to Contribute to Open Source | Open Source Guidesopensource.guide
- Git from the Bottom Upjwiegley.github.io
- Useful git commands for SRE and DevOps engineersreliabilityengineering.substack.com
- GitHub - abhivaikar/howtheytest: A collection of public resources about how software companies test their softwaregithub.com
- How to write complex softwaregrantslatton.com
- GitHub - sindresorhus/awesome: 😎 Awesome lists about all kinds of interesting topics · GitHubgithub.com
- Bulletproof node.js project architecture 🛡️softwareontheroad.com