Welcome to the EspaçoGeek organization repository — an initiative to bring the geek community together in a single place by offering tools to track media consumption, share content, and interact socially.

This README explains the project's purpose, main components (including the GraphQL API under development), how to contribute, and basic instructions to run the development environment.

Provide a unified platform for users to record, organize, and share their consumption of geek media (series, movies, games, books, anime, manga, light novels, visual novels, etc.), while also enabling social interaction through posts, comments, and reviews.

Build a scalable, modular, and accessible application that centralizes hobby tracking and content sharing for the geek community, following software engineering best practices and a modern technology stack.

• User system (registration, login, credential recovery and updates)
• User profiles and custom lists (e.g., Playing, Plan to Play, Paused, Abandoned)
• Multi-media support (series, games, visual novels, books, anime, manga, light novels, etc.)
• Search and detailed media pages (synopsis, images, trailers, seasons, etc.)
• Social features: posts, comments, ratings, and reviews (progressive implementation)
• GraphQL API for efficient client-server communication
• Responsive web UI built with React and PrimeReact

Current status (from project document): GraphQL API is in an advanced stage with user management and media data (series, games, visual novels) implemented. Frontend is in development.

• Backend: Java + Spring Boot (GraphQL)
• Database: MySQL
• Frontend: ReactJS + PrimeReact
• Tools: Visual Studio Code, Postman (API testing)
• Architecture / Process: MSC (Model > Service > Controller), Kanban for task management

Contributions are welcome! Suggested workflow:

1. Open an issue describing the idea or bug.
2. Fork the repository and create a branch with a clear name (e.g., feature/graphql-auth).
3. Keep commits small and descriptive; follow project coding standards.
4. Open a pull request explaining the change and how to test it.

Guidelines:

• Follow MSC (Model > Service > Controller) structure.
• Add automated tests for critical functionality.
• Use the project Kanban board and labels (feature, bug, docs, infra).

• Write clean, readable code.
• Follow SOLID principles.
• Document endpoints and update /docs.
• Provide unit and integration tests for important features.

Handle user data responsibly. Store passwords securely (hashed), use TLS for network traffic, validate and sanitize inputs, and provide moderation tools and terms of use for social features.

• Vitor Hugo Alves Ferreira — vitorhugoalvesferreira@outlook.com
• @@AbigailGeovana - GitHub
• Anderson Pazin — anderson.pazin@fatec.sp.gov.br

Thank you for contributing to EspaçoGeek — join us to build a central space for geek culture!