Welcome to the official ITNC Website repository.
This is where we build and maintain the official website for the Informatics & Technology Club (ITNC).
src/→ css, js, etc.docs/submodule:docs/→ Documentation, guides, and tutorials.resources/→ Shared assets, libraries, and references.
git config --global user.name "Your Name"
git config --global user.email "you@example.com"- On your desktop, create a new folder named "ITNC (anything you want)"
- Open the folder and in the folder path bar, type cmd and press Enter

- Once Command Prompt opens, clone the Repository and open the folder in Visual Studio Code:
git clone https://github.com/ITNCNitra/itncnitra.github.io.git cd itncnitra.github.io code .
- Open new terminal in Visual Studio Code from the terminal bar at the top, or use the shortcut Ctrl + `.
- Optional (currently): Pull
docs/submodules files:Note: rerun the cmd to updategit submodule update --remote --rebasedocs/submodule - install deps:
npm install - run/build tailwind:
#run this when developing npx @tailwindcss/cli -i ./src/input.css -o ./src/output.css --watch#run this when building (before adding output.css and committing) npx @tailwindcss/cli -i ./src/input.css -o ./src/output.css --minify - Optional: sync local files with remote (github):
Note: rerun the command to pull latest commit,
git fetch origin git pull
you can also read more about git cmd here itncnitra.github.io\docs\docs\git.md
Members of ITNC who want to contribute directly can request access to be added as a collaborator on this repository. Just contact one of the maintainers or open an issue titled “Access Request.”
For contributors outside the organization, you’re welcome to fork this repo and open a Pull Request (PR) with your improvements. Make sure your changes are clear and follow our commit style (e.g., feat:, fix:, docs:).
- Fork this repository
- Create a new branch for your change
- Commit with a clear message
- Push to your fork
- Open a Pull Request
We’ll review your PR and merge it if it fits our goals.
git checkout -b <branch name>Work on your code inside the new <branch name> branch.
Commit changes regularly to your project branch.
git add <file>
git commit -m "<commit message>"
git push -u origin <branch name>When the project is stable, open a Pull Request to merge it into main.
- Always create a new branch for your project or feature (
git checkout -b project-nameorfeature-name). - Always build first before adding output.css, deployments breaks without it.
- Write clear, descriptive commit messages.
- Push your branch and open a Pull Request when ready to merge into
main.