ITA Wiki is a project built with React.js and Node.js for students at the IT Academy from Barcelona Activa. The goal is to allow them to familiarize themselves with a generic development setup that could be found in their future career. One of the purposes of this project is to allow students to deal with new features, legacy code, fixes and teamwork challenges. As a consequence the priority is not only excellent technical execution, but to provide a full learning experience to our students.

If you're a new student landign on the project, please read everything before getting started.

Welcome to the IT-Academy-BCN's Wiki GitHub repository! We're glad to have you on board. This section will guide you through the process of getting started with our project, which is divided into frontend and backend development. To help you understand the importance of our onboarding process, we'll discuss the benefits of the Work Breakdown Structure (WBS), our Git workflow, and the tools and libraries you'll need to familiarize yourself with. Remember, be proactive and seek answers on Google and Stack Overflow when you encounter challenges.

Quicklinks:

• Visual design.
• Demo front dev.
• ITA API Swagger docs.
• SSO Swagger docs.

• We hold a daily meeting at 9.00AM from Monday to Thursday, and it is mandatory to assist.
• We have sprint planning every two weeks, preferably on Mondays.
• We have a sprint review (retro) every two weeks, preferably on Thursdays.
• The project requires a weekly dedication of 15~25 hours.

IMPORTANT: If you cannot dedicate enough time, nor be on the meetings, please reach out to the project lead.

Our project is divided into two main areas: frontend and backend development. Depending on your itinerary specialization you will be working on one or the other. Fullstack profiles are also welcome.

Use Node 18.

Frontend developers are responsible for creating and maintaining the user interface, ensuring that the website is visually appealing, user-friendly, and responsive. Our frontend is built with React, Vite, and Vitest. We also use an atomic design system and a CI/CD pipeline to lint, test, build, and deploy the project on the development environment.

• React: A JavaScript library for building user interfaces.
• Vite: A build tool and development server that focuses on speed and simplicity.
• Vitest: A testing framework designed to work seamlessly with Vite.
• Atomic Design System: A methodology for creating design systems by breaking down components into atoms, molecules, and organisms.

Backend developers are responsible for managing the data, logic, and server-side infrastructure of the website. They ensure that data is transferred smoothly between the frontend and backend, as well as handle database management, API integration, and server-side programming. Our backend stack includes Koa, Prisma (ORM), Supertest, Docker, PostgreSQL, and bash terminal, with a basic routing/router/repo folder structure.

• Koa: A lightweight and flexible web framework for Node.js.
• Prisma: A modern ORM (Object Relational Mapping) library that simplifies database management and data querying.
• Supertest: A library for testing HTTP servers and APIs, making it easy to assert, test, and simulate HTTP requests and responses.
• Docker: A platform that simplifies the process of building, shipping, and running applications in containers, ensuring consistency across different environments.
• PostgreSQL: A powerful, open-source object-relational database system.
• Bash Terminal: A command-line interface for interacting with the operating system, executing commands, and running scripts.

In both frontend and backend, we use Zod schemas for validation, which provides a convenient and efficient way to ensure data consistency and integrity across the application.

The Work Breakdown Structure (WBS) is a key project management tool that helps us break down tasks and deliverables into manageable units. This approach allows for better organization, tracking, and allocation of resources. Our onboarding process may seem challenging, but it is crucial in understanding the project structure, workflow, and coding standards.

By going through this onboarding process, you'll:

• Gain a comprehensive understanding of the project's goals and requirements.
• Learn how to collaborate effectively with the team.
• Familiarize yourself with the tools and technologies used in the project.
• Be better prepared to contribute meaningfully and efficiently to the project.

While we encourage collaboration and support among team members, it's important for you to be proactive in your learning and problem-solving. Before reaching out for help, try to search for answers on Google and Stack Overflow. These resources contain a wealth of information and can often help you solve issues on your own. By doing so, you'll develop your problem-solving skills and become a more self-sufficient developer.

1. When new features or fixes are required we create a new issue.
2. Issues are assigned to one person.
3. The number of the issue is created as a new branch name following git branch naming conventions: https://deepsource.com/blog/git-branch-naming-conventions/
4. Once the issue is resolved, a new pull-request from your branch to main is required.

1. Install the ESLint VSCode extension.
2. In the root folder of the whole project create a .vscode folder.
3. Create a settings.json file in the .vscode folder with the following content:

{
  "eslint.workingDirectories": [
    "web/wiki",
    "web/usuaris",
    "services/wiki",
    "services/sso",
    "packages/ui"
  ]
}

The code above allows the ESLint VSCode extension to properly find each ESLint project configuration file. This will help ensure that you're following the project's coding standards and guidelines as you contribute to the project.

With this guide, we hope you feel better prepared to contribute to our project. Remember, don't hesitate to ask questions and reach out for support if needed. We're excited to have you on board and look forward to your contributions!

Deployments are managed by the developers. The project is deployed on a development environment and a production environment. The development environment is used for testing and debugging, while the production environment is used for the final product.

We use Semantic Versioning for versioning. It is the responsibility of the developers to update the version number in the package.json file of the respective apps.

Changes are documented in the CHANGELOG.md file of the respective apps.

To deploy the development environment, follow these steps:

1. Go to github actions and select the Deploy script.
2. Write down the version you wish to deploy 1.12.4 and select the environment dev or prod.
3. Click run on the dropdown menu.