Skip to content

ElectricAlgorhythm/kaichou-graduation

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

25 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Kaichou Graduation Project

The Kaichou Project is a graduation tribute website for the VTuber Kiryu Coco.

Setup

To set up and run the project you will need to have node (at least version 12) and yarn installed.

First run yarn install and wait for the dependencies to finish installing.

Next, copy and rename the .env.example files in both front- and backend to .env. Do not delete the .env.example.

Lastly you should be able to start the project by simply running yarn dev.

To get linting to work in your IDE of choice (for example VSCode), install the prettier and eslint plugins.

Project Structure

The project is currently split into a frontend and backend package, both being tied together in the project root using yarn workspaces.

Both frontend and backend are using typescript for type safety.

Frontend

The frontend uses nextjs, which makes routing pretty simple. There is a components folder for anything that isn't supposed to show up on the actual website.

Use the public folder for images and assets.

For styling there is scss with css modules, so do not ever put any css inline unless absolutely required.

Also for styling there is the variables.scss which is to be used for global variables like colors and mixins. The globals.scss is mainly used for standardization and should rarely be touched at all.

Backend

The backend structure is still up to debate and will change in the near future.

The backend uses express as a server for hosting a REST API, which is all set up inside the index.ts.

Contributing

You do not need to be a member of the Kaichou-Project organization to contribute. Follow these steps:

  1. Fork the repository from here.

  2. Clone your fork locally.

  3. Optional, but recommended: Create a new branch on the latest commit of the branch you want to contribute to.

  4. Commit to the new branch (or the branch you want to contribute to, if you decided not to make a new branch).

  5. Push to your fork.

  6. Create a pull request from the branch you committed to in your fork to the branch you want to contribute to in the organization repository. We don't have a format for pull request descriptions, but please include any details that would help a reviewer.

Releases

No releases published

Packages

No packages published

Languages

  • TypeScript 67.6%
  • SCSS 30.3%
  • Shell 2.1%