Grind ICMC - Website

What is this?

This is the official website for Grind ICMC, a university extension group from the University of São Paulo (USP) - ICMC. We focus on preparing students for technical careers across Engineering and Science, covering software engineering, machine learning, data engineering, data science, applied science, research practice, soft skills, and networking.

Tech Stack

• Framework: Next.js (App Router)
• Language: TypeScript
• Styling: Tailwind CSS
• Components: Radix UI / Shadcn
• Icons: Lucide React & React Icons

How to Run Locally

1. Clone the repository:

   git clone https://github.com/Grind-ICMC/website.git
   cd website

2. Install dependencies: Make sure you have Node.js installed, then run:

   npm install
   # or
   pnpm install
   # or
   yarn install

3. Configure environment variables: Create a local .env file based on .env.example. AUTH_SECRET is the Auth.js session secret and is different from GITHUB_ADMIN_TOKEN.

   Required variables:

   • AUTH_SECRET: random secret used by Auth.js to sign/encrypt sessions.
   • AUTH_GITHUB_ID: GitHub OAuth app client ID for the login flow.
   • AUTH_GITHUB_SECRET: GitHub OAuth app client secret for the login flow.
   • GITHUB_ADMIN_TOKEN: GitHub token used by the server to read/write the Grind-ICMC/meetings, Grind-ICMC/docs, Grind-ICMC/studies, and Grind-ICMC/psel-empresas repositories.

   For local development, create a GitHub OAuth App with:

   • Homepage URL: http://localhost:3000
   • Authorization callback URL: http://localhost:3000/api/auth/callback/github

4. Start the development server:

   npm run dev
   # or
   pnpm dev
   # or
   yarn dev

5. View the app: Open http://localhost:3000 in your browser.

Contributing

Contributions are welcome! If you find any issues or want to add new features, feel free to open an issue or a Pull Request.

Admin document editor

Documents open in the visual editor. The Markdown avançado switch keeps the source editor and its preview available. Both modes save Markdown and support headings, emphasis, links, lists, tasks, tables, images, and fenced code with a language selector.

Document dates use the filename convention YYYY-MM-DD-name.md. The interface hides the prefix from the display name and reads the date from that prefix only; legacy YAML dates are not used. Files without a valid prefix display ? and can remain undated when edited. New documents require a date. Changing a date updates the filename in its existing folder, with the content and rename in one GitHub commit. Existing destination names and concurrent edits are rejected. Category, tags, and dates are no longer written into the YAML metadata.

Run npm test for Markdown conversion, filename/date handling, and mocked GitHub rename checks. Run npx tsc --noEmit and npm run build for the full type and production-build checks.