Standardize naming convention for this project and branches and directory structure

[AlexVanK]

This project is a Drupal theme.

Upon downloading the repository, github automatically renames the folder within the .zip file with the name of the repository.

This creates problems upon first installation of the project.

Proposed solution. Re-imagine the file system structure from:

/THEMES
├── /bootstrap5
├── /nihod5
│      ├── .git
│      └── *.*
├── /nihod5__subtheme
│      └── *.*
└── *.*

to something like

/THEMES
├── /bootstrap5
├── /.git
├── /nihod5
├── /nihod5__subtheme
└── *.*

The important requirements are:

• Manage main theme vs subtheme (starter boilerplate) separately (two different repositories vs main + branch)
• Download only the subtheme upon first installation of the project: never upon updates
• the .git folder needs to stay outside of the ready-for-deployment theme folder. We cannot have lose files because of GitHub packaging mechanism (see above: OP)
• Avoid folder nesting -- this would bloat Drupal directory's structure and cause confusion

Questions:

• can we have two different .git folders in the same directory?
• how do we maintain the boilerplate branch?

---

Ideas are welcome

[AlexVanK]

Done ✔️

• [X] Manage main theme vs subtheme (starter boilerplate) separately (two different repositories vs main + branch)

Repository now contains main branch 5.x.x + 5.x.x--subtheme branch. This architecture needs to be respected for each major release:

/REPOSITORY
├── 5.x.x
├── 5.x.x--subtheme
├── 6.x.x
├── 6.x.x--subtheme
└── etc.

this will be reflected on the development file system as:

/THEMES
├── NIHOD5
│      ├── .git
│      └── *.*
├── NIHOD5__subtheme
│      ├── .git
│      └── *.*
├── NIHOD6
│      ├── .git
│      └── *.*
├── NIHOD6__subtheme
│      ├── .git
│      └── *.*
└── etc.

• [x] Download only the subtheme upon first installation of the project: never upon updates

Addressed somewhere else. Issue: #27

• [x] the .git folder needs to stay outside of the ready-for-deployment theme folder. We cannot have lose files because of GitHub packaging mechanism (see above: OP)

For now, ready-for-deployment theme folder needs to be provided as a binary .zip/tag.gz file. This file will have to be packaged up manually (for now).

• [x] Avoid folder nesting -- this would bloat Drupal directory's structure and cause confusion

Done. Point above solves this issue.