IT Manager Onboarding
Start here when you take over BISO Sites. Step-by-step guidance tailored for non-technical maintainers.
IT Manager Onboarding
Welcome! This guide is for future IT managers or committee members who inherit BISO Sites and need a structured way to understand, run, and maintain the platform—even if you have minimal coding experience.
What You'll Achieve
- Know what lives inside the monorepo and how the applications connect.
- Set up a working development environment you can demo to stakeholders.
- Understand where to find feature-specific docs and operational playbooks.
- Capture a punch-list for handover or incident response.
⚠️
Before you begin
Make sure you have access to the GitHub repository, Appwrite console, Vipps account, and any environment-variable vault the previous maintainer used.
Guided Path
Get oriented (15 min)
- Skim the Repository Project Structure and Architecture Overview.\n - Visit the Applications Overview to see how the web and admin apps are positioned.\n - Bookmark the Commands Reference so you always know which scripts to run.
Run the stack locally (30 min)
- Follow the Quickstart and Installation Guide.\n - Use the Development Workflow to start the dev servers.\n - Log into the admin app with a test account and walk through the critical flows (events, membership, shop).
Review operations & credentials (30 min)
- Read the Operations Overview to understand how deployments work.\n - Compare
.env.localfiles with the Environment Variables checklist.\n - Verify Appwrite, Vipps, and hosting consoles are accessible and note who controls billing.
Plan your first improvements (ongoing)
- Capture issues or questions in GitHub under a
handoverlabel.\n - Document recurring tasks (publishing events, onboarding new units) inside the Admin App section.\n - Schedule a quarterly review of dependencies and security updates.
Daily Toolkit
- Applications → Web App for anything public-facing.
- Applications → Admin App for editor workflows and permissions.
- Packages to understand shared logic (API, payment, editor, UI).
- Operations for deployments, secrets, and external services.
When to Ask for Help
ℹ️
If something feels risky or you lack access, pause and reach out:
- Open a GitHub issue tagged
help wanted - Contact the previous IT manager or faculty advisor
- Ask within the student union’s tech channel for context
Keep improving this page as you learn—future maintainers will thank you.