Thailand Election 2023

Monorepo for Thailand Election 2023 projects using Turborepo.

🌎 Environments

/apps - Application for each project.
- designyourmp - Design your dream representative
- electionsim - Election simulation
- landing - Landing page with projects directory
- mpasset - MP asset (Politician-asset)
- theyworkforyou - Your candidate matching quizes
- underconstruction - Dummy page for coming soon project
- yourcandidates - Look Up Your Candidates
/packages - Packages shared between apps
- styles - Shared stylesheets according to the design systems
- components - Shared web-component elements
- database - WeVis NocoDB fetching utility
- wordpress - WeVis WordPress API fetching utility
- metadata - Projects metadata
/bundler - Project built artifacts merging script

Requires NodeJS (v18 LTS is recommended) and Yarn v1

Install dependencies with Yarn

yarn

Pre-commit hook using Husky is set up to

For VSCode user, format on save is enabled and prettier-vscode extensiones will be recommended when open the project.

Create a new project inside apps directory eg. apps/project-name. Follow initization step according to the framwork you use.
Change name in the project's package.json to @thailand-election-2023/project-name

{
	"name": "@thailand-election-2023/project-name"
}

Make sure that dev (run development server) and build (build production files) scripts is specific in the package.json
Set base path according to each framwork instruction. Every project will be at /project-name except the landing page
Add shared packages into the project. Follow each packages instruction:
- @thailand-election-2023/styles
- @thailand-election-2023/components
Set build output to be /dist in each project

Using turborepo to run specific with all the package dependencies in development mode.

yarn dev --filter=<project-name>...

Note that ... at the end is nessesary to run dependencies script as well. Without filter, every apps and packages will be run.

We will use trunk-based development: Everyone will work on the main branch
- WHY? Continueus integration reduce merge conflic and make sure that everyone is using the newest codebase
- If you don't have a permission on the main branch, please submit the PR :)
- Always pull --rebase before continue your work, and before push.
- Push often, as long as it doesn't fail the build command.
We will use conventional commit for commit message.
- WHY? We work on the same branch. This helps the commit history well organized.
```
<type>(project-name): <description>

example:

feat(landing): add link to external projects
```
- Commit types explanation can be found here
- If commit message is invalid, error will be shown and preventing you from committing the code.
We use Prettier to format code
- WHY To make the whole repository have formating standard and improving reability for the team.
- This should be done automatically on pre-commit and on save for VSCode user.
- Configuration is in .prettierrc

Read more at WeVis's Terms of Use (in Thai)