/CO2-Website

Primary LanguageCSS

🐢 Creative Olympics 🔥

This is the repository for the Creative Olympics website and Admin App

Website version App version

Repo

Issue board  Current Sprint


Issues / tasks are all categorized using the following labels:

  • Priorities: ~P0 ~P1 ~P2 ~P3 ~P4
  • Progress: ~Planned ~Doing ~"A/B" ~Clean
  • A/B progress: ~Pending ~"25%" ~"50%" ~"75%"
  • Main features: ~Feature
  • Type (Issue): ~accessibility ~enhancement ~performance ~SEO
  • Type (Meta): ~discussion ~documentation ~refactor
  • Bugs: ~bug (+~confirmed if replicable)
  • Blocked: ~BLOCKED

Progress labels are used as categories on the issue board.

Priorities follow the Google Issue Tracker issue priorities guidelines:

Priority Description
~P0 An issue that needs to be addressed immediately and with as many resources as is required. Such an issue causes a full outage or makes a critical function of the product to be unavailable for everyone, without any known workaround.
~P1 An issue that needs to be addressed quickly. Such an issue significantly impacts a large percentage of users; if there is a workaround it is partial or overly painful. The impact of the issue is to a core organizational function, or fundamentally impedes another team.
~P2 An issue that needs to be addressed on a reasonable timescale. Such an issue could be any of the following:
・ An issue that would be ~P0 or ~P1 but has a reasonable workaround
・ An issue that is important to a large percentage of users and is connected to core organizational functions
・ An issue that is an impediment to the work of other teams and has no reasonable workaround.
~P3 An issue that should be addressed when able. Such an issue is relevant to core organizational functions or the work of other teams, but does not impede progress or else has a reasonable workaround.
~P4 An issue that should be addressed eventually. Such an issue is not relevant to core organizational functions or the work of other teams, or else it relates only to the attractiveness or pleasantness of the system.

Admin App

Download  Explore files


  • Technologies: Koltin, Jetpack Compose

Website

Visit website  Explore files


  • Technologies: Svelte, Vite, Tailwind CSS
  • Hosting: Firebase Hosting

Scripts:

Run the website in dev mode:

npm run dev
# concurrently \"vite build\" \"cross-env TAILWIND_MODE=watch cross-env NODE_ENV=development postcss src/app.css -o src/app-output.css -w\"

Build a production version of the website:

npm run build
# npm run cross-env TAILWIND_MODE=build cross-env NODE_ENV=production postcss src/app.css -o src/app-output.css && vite build

Preview the production version of the website:

npm run preview
# vite preview


ONLY Run the website in dev mode (without Tailwind):

npm run dev:only
# vite build

ONLY Build a production version of the website (without Tailwind):

npm run build:only
# vite build

Tailwind watch:

npm run tailwind:watch
# cross-env TAILWIND_MODE=watch cross-env NODE_ENV=development postcss src/app.css -o src/app-output.css -w

ONLY Build a production version of Tailwind (without the website):

npm run tailwind:build
# cross-env TAILWIND_MODE=build cross-env NODE_ENV=production postcss src/app.css -o src/app-output.css

Run the website in dev mode and make it available to the local network (or the whole internet if you open the ports in your router):

npm run devhost
# concurrently \"npm run dev:only -- --host\" \"npm run tailwind:watch\"

Lint:

npm run lint
# prettier --plugin-search-dir . --check . && eslint .

Format:

npm run format
# prettier --plugin-search-dir . --write .

Back-end

  • Technologies: Firebase Remote Config, Firestore Database, Firebase Realtime Database, Firebase Cloud Functions, Firebase Cloud Messaging

Docs

Achievements  Giveaways