Official Angular theme template for public-facing projects inside the IT Kamianets GitHub organization.
Follow these steps when creating a new project based on this theme.
git clone https://github.com/IT-Kamianets/theme-tailwind.git my-project
cd my-projectIt is strongly recommended to start with a fresh Git history so your new project does not inherit the theme’s commit history.
rm -rf .git
git init
git add --all .
git commit -m "chore: init project from theme"Now connect your new repository:
git remote add origin https://github.com/YOUR_ORG/YOUR_PROJECT.git
git branch -M master
git push -u origin masterYou now have a clean standalone project.
Open the CNAME file in the root directory and replace the domain with your new project domain.
Example:
voltlab.itkamianets.com
Then verify:
- Repository → Settings → Pages
- Custom domain matches
CNAME - SSL is enabled
npm install
npm run startYou are now ready to build your new project.
This repository includes a CNAME file for GitHub Pages deployment.
When using this template:
- Open the
CNAMEfile - Replace the domain with the new project domain
If not updated, GitHub Pages will continue pointing to the previous project domain.
Always verify:
- Repository → Settings → Pages
- Custom domain matches
CNAME - SSL is enabled
Global theme configuration is located in:
src/styles.scss
Before launching a new project, review and adjust:
--c-primary--c-primary-hover--c-secondary--c-secondary-hover
--c-bg-primary--c-bg-secondary--c-bg-tertiary
--c-text-primary--c-text-secondary--c-text-muted--c-placeholder
--c-border--shadow-sm--shadow-md--shadow-lg
All UI components must rely strictly on CSS variables. Hardcoded colors are not allowed.
Every project built from this theme contains the following foundational pages.
Purpose:
- Project introduction
- Value proposition
- CTA blocks
- Highlight key features
Used for:
- SEO entry point
- Social sharing
- Brand positioning
Purpose:
- Describe the organization or project mission
- Present background, values, vision
- Explain ecosystem integration (if applicable)
Used for:
- Credibility
- Transparency
- Partner introduction
Purpose:
- Showcase active initiatives
- List products, tools, or platforms
- Provide navigation to sub-projects
Used for:
- Ecosystem visibility
- Traffic distribution
Purpose:
- Present community initiatives
- Events, collaboration, partnerships
- Call to action for joining
Used for:
- Developer onboarding
- Student engagement
- Local ecosystem growth
Purpose:
- Publish updates
- Share announcements
- Document progress
Used for:
- SEO growth
- Activity signals
- Public transparency
Purpose:
- Provide official communication channels
- Display email, social links, location
- Allow partnership inquiries
Used for:
- Lead generation
- Business communication
Purpose:
- Terms of service
- Privacy policy
- Data handling transparency
Used for:
- Compliance
- Trust building
- Public clarity
src/
app/
pages/
components/
styles.scss
CNAME
CONTRIBUTING.md
pages/→ main 7 pagescomponents/→ reusable UI elementsstyles.scss→ global design tokensCNAME→ production domainCONTRIBUTING.md→ contribution workflow
All contributors must strictly follow CONTRIBUTING.md.
This applies to:
- Developers
- External contributors
- AI tools
Core principles:
- Use Conventional Commits
- One logical change per commit
- Proper branch naming
- No direct commits to
master - PR must reference an issue
Before starting work:
- Create a branch
- Follow naming convention
- Link GitHub issue
- Keep commits clean and focused
When using AI tools:
- Always provide
CONTRIBUTING.md - Enforce commit format
- Enforce branch naming rules
- Review generated code manually
- Do not allow uncontrolled structural changes
AI assists development − it does not define architecture.
Deployment is managed via:
- GitHub Pages
CNAMEdomain configuration- Optional GitHub Actions workflow
After pushing to master:
- Verify Pages build status
- Confirm correct domain resolution
- Check SSL certificate
MIT License