Skip to content

The ProEventos project was developed to optimize event management. This repository includes the complete proposal for both Front-End and Back-End of an efficient software for managing events, such as lectures.

Notifications You must be signed in to change notification settings

gizellemanu/ProEventoSync

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

8 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

English

ProEventoSync

INTRODUCTION

The ProEventos project was created to serve the event management sector. This repository presents the proposal for Front-End and Back-End for software designed to efficiently manage events such as conferences. The application’s Front-End was developed using Angular CLI (version >= 11.2.1), while the Back-End was built using C# and .NET, with the MySQL Server Express database.

Completion Certificate

This project was developed during the Udemy course, taught by VinΓ­cius de Andrade.
You can access the certificate directly β†’ here ←.

Index

Project Features

The application includes the following features:

  • 1. A Login Screen, containing a form with email and password fields.

    • The login form is only validated with the correctly filled fields.
    • The password must have 8 characters.
    • The speaker’s profile has three tabs: profile, speaker bio, and social networks.
  • 2. A Forgot Password Screen containing a simple form with the email field.

    • The Forgot Password form is only validated with the correctly filled email field.
  • 3. A top Menu with options for Dashboard, Events, Speakers, and Contact.

  • 4. A Speaker Registration Screen containing a form with name, company name, tax ID (CNPJ), and email fields.

    • The user registration form is only validated with the correctly filled fields.
    • The password must have 8 characters.
    • The password confirmation field also has validation; if the passwords do not match, registration is not possible.
    • The CNPJ must have 14 characters.
  • 5. An Event List Screen.

    • It has a search function by location, subject, or speaker.
    • You can collapse and expand the grid with the promotional images of already registered events.
    • You can edit or delete the desired event.
  • 7. An Event Registration Screen containing a form with event name, speaker, promotional image, social network, theme, location, time, date, attendee limit, and batch fields.

  • 8. An Event Edit Screen containing a form with the same fields as the Event Registration Screen.

  • 9. An Event Edit Screen containing a form with the same fields as the Event Registration Screen.

How to Run the Project

Before using this application, you need to have Node.js and Angular CLI installed on your computer. This project was developed using Angular CLI version 11.2.1. Follow the steps below to install and configure the development environment:

Prerequisites

  • Node.js (version >= 10.13.0)
  • .NET (version >= 5.0.402)
  • npm (version >= 6.11.0)
  • Angular CLI (version >= 11.2.1)
  • MySQL

Installing Node.js

  1. Go to the official Node.js website at https://nodejs.org/en/download/.
  2. Select the download option for your operating system.
  3. Download and run the Node.js installer. Follow the installer instructions to complete the installation.

Installing Angular CLI

  1. Open your system's terminal.
  2. Run the following command to install Angular CLI:
    npm install -g @angular/cli@11.2.1
  3. Wait for the installation to complete.

Installing Project Dependencies

  1. Clone the repository:
    git clone https://github.com/your-username/your-repository.git

Running the Backend

  1. Navigate to the backend directory:
    cd backend
  2. Start the backend server:
    npm start
  3. Check the backend connection: The server should be running at http://localhost:3000/. You can verify if the backend is working properly by accessing this URL.

Running the Frontend

  1. Navigate to the frontend directory:
    cd ProEventos/Front/ProEventos-App
  2. Install the frontend dependencies:
    npm install

After these commands, your project folder structure should look similar to this:

ProEventos/
β”œβ”€β”€ .vscode/
β”œβ”€β”€ Back/
β”œβ”€β”€ Front/
β”‚   └── ProEventos-App
β”‚       β”œβ”€β”€ e2e/
β”‚       β”œβ”€β”€ node_modules/
β”‚       β”œβ”€β”€ src/
β”‚       └── ...
β”œβ”€β”€ .gitignore
└── README.md
  1. Start the development server::

    ng serve
  2. Access the application: Navigate to http://localhost:4200/. The application will reload automatically if you change any of the source files.

Running Frontend and Backend Together

Start the backend:

  1. Make sure the backend server is running first. Navigate to the backend directory and run:
    cd ProEventos/Back/src
    npm start

Start the Frontend:

  1. To start the development server, run:
    cd ProEventos/Front/ProEventos-App
    ng serve
  2. Navigate to http://localhost:4200/. The application will automatically reload if you change any of the source files.

Directory Structure

ProEventos/
β”œβ”€β”€ .vscode/
β”‚   β”œβ”€β”€  launch.json
β”‚   └── tasks.json
β”œβ”€β”€ Back/
β”‚   └── src
β”‚   β”‚    β”œβ”€β”€  ProEventos.API
β”‚   β”‚    β”‚     β”œβ”€β”€ bin/
β”‚   β”‚    β”‚     β”œβ”€β”€ Controllers/
β”‚   β”‚    β”‚     β”œβ”€β”€ Controllers/
β”‚   β”‚    β”‚     β”œβ”€β”€ Extensions/
β”‚   β”‚    β”‚     β”œβ”€β”€ Helpers/
β”‚   β”‚    β”‚     β”œβ”€β”€ Models/
β”‚   β”‚    β”‚     β”œβ”€β”€ obj/
β”‚   β”‚    β”‚     β”œβ”€β”€ Properties/
β”‚   β”‚    β”‚     β”œβ”€β”€ appsettings.Development.json
β”‚   β”‚    β”‚     β”œβ”€β”€ appsettings.json
β”‚   β”‚    β”‚     β”œβ”€β”€ ProEventos.API.csproj
β”‚   β”‚    β”‚     β”œβ”€β”€ Program.cs
β”‚   β”‚    β”‚     └── Startup.cs
β”‚   β”‚    β”œβ”€β”€  ProEventos.Application
β”‚   β”‚    β”‚     β”œβ”€β”€ bin/
β”‚   β”‚    β”‚     β”œβ”€β”€ Contratos/
β”‚   β”‚    β”‚     β”œβ”€β”€ Dtos/
β”‚   β”‚    β”‚     β”œβ”€β”€ Extensions/
β”‚   β”‚    β”‚     β”œβ”€β”€ Helpers/
β”‚   β”‚    β”‚     β”œβ”€β”€ obj/
β”‚   β”‚    β”‚     β”œβ”€β”€ AccountService.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ EventoService.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ LoteService.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ PalestranteService.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ ProEventos.Application.csproj
β”‚   β”‚    β”‚     β”œβ”€β”€ RedeSocialService.cs
β”‚   β”‚    β”‚     └── TokenService.cs
β”‚   β”‚    β”œβ”€β”€  ProEventos.Domain
β”‚   β”‚    β”‚     β”œβ”€β”€ bin/
β”‚   β”‚    β”‚     β”œβ”€β”€ Enum/
β”‚   β”‚    β”‚     β”œβ”€β”€ Identity/
β”‚   β”‚    β”‚     β”œβ”€β”€ obj/
β”‚   β”‚    β”‚     β”œβ”€β”€ Evento.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ Lote.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ Palestrante.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ PalestranteEvento.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ ProEventos.Domain.csproj
β”‚   β”‚    β”‚     └── RedeSocial.cs
β”‚   β”‚    β”œβ”€β”€  ProEventos.Persistence
β”‚   β”‚    β”‚     β”œβ”€β”€ bin/
β”‚   β”‚    β”‚     β”œβ”€β”€ Contextos/
β”‚   β”‚    β”‚     β”œβ”€β”€ Contratos/
β”‚   β”‚    β”‚     β”œβ”€β”€ Migrations/
β”‚   β”‚    β”‚     β”œβ”€β”€ Models/
β”‚   β”‚    β”‚     β”œβ”€β”€ obj/
β”‚   β”‚    β”‚     β”œβ”€β”€ EventoPersist.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ GeralPersist.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ LotePersist.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ PalestrantePersist.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ ProEventos.Persistence.csproj
β”‚   β”‚    β”‚     β”œβ”€β”€ RedeSocialPersist.cs
β”‚   β”‚    β”‚     └── UserPersist.cs
β”‚   β”‚    β”œβ”€β”€  global.json
β”‚   └──  └──  ProEventos.sln
β”œβ”€β”€ Front/
β”‚   └── ProEventos-App
β”‚       β”œβ”€β”€ e2e/
β”‚       β”‚   └── ...
β”‚       β”œβ”€β”€ node_modules/
β”‚       β”‚   └── ...
β”‚       β”œβ”€β”€ src/
β”‚       β”‚   β”œβ”€β”€ app/
β”‚       β”‚   β”‚   β”œβ”€β”€ components/
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ contatos/
β”‚       β”‚   β”‚   β”‚   |   └── ...
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ dashboard/
β”‚       β”‚   β”‚   β”‚   |   └── ...
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ eventos/
β”‚       β”‚   β”‚   β”‚   |   └── ...
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ home/
β”‚       β”‚   β”‚   β”‚   |   └── ...
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ palestrantes/
β”‚       β”‚   β”‚   β”‚   |   └── ...
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ redesSociais/
β”‚       β”‚   β”‚   β”‚   |   └── ...
β”‚       β”‚   β”‚   β”‚   └── user/
β”‚       β”‚   β”‚   β”‚       └── ...
β”‚       β”‚   β”‚   β”œβ”€β”€ guard/
β”‚       β”‚   β”‚   β”‚   └── ...
β”‚       β”‚   β”‚   β”œβ”€β”€ helpers/
β”‚       β”‚   β”‚   β”‚   └── ...
β”‚       β”‚   β”‚   β”œβ”€β”€ interceptors/
β”‚       β”‚   β”‚   β”‚   └── ...
β”‚       β”‚   β”‚   β”œβ”€β”€ services/
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ account.service.ts
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ evento.service.ts
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ lote.service.ts
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ palestrante.service.ts
β”‚       β”‚   β”‚   β”‚   └── redeSocial.service.ts
β”‚       β”‚   β”‚   β”œβ”€β”€ models/
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ identity/
β”‚       β”‚   β”‚   β”‚   |   └── User.ts
β”‚       β”‚   β”‚   β”‚   |   └── UserLogin.ts
β”‚       β”‚   β”‚   β”‚   |   └── UserUpdate.ts
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ Evento.ts
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ Lote.ts
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ Pagination.ts
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ Palestrante.ts
β”‚       β”‚   β”‚   β”‚   └── RedeSocial.ts
β”‚       β”‚   β”‚   β”œβ”€β”€ shared/
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ nav/
β”‚       β”‚   β”‚   β”‚   └── ...
β”‚       β”‚   β”‚   β”‚   └── titulo/
β”‚       β”‚   β”‚   β”‚   └── ...
β”‚       β”‚   β”‚   β”œβ”€β”€ util/
β”‚       β”‚   β”‚   β”‚   └── ...
β”‚       β”‚   β”‚   β”œβ”€β”€ app-routing.module.ts
β”‚       β”‚   β”‚   └── ...
β”‚       β”‚   β”œβ”€β”€ assets/
β”‚       β”‚   β”œβ”€β”€ environments/
β”‚       └── └── ...
β”œβ”€β”€ .gitignore
└── README.md


Portugues

ProEventoSync

INTRODUÇÃO

O projeto ProEventos foi criado para atender o setor de gestão de eventos. Este repositório apresenta a proposta de Front-End e Back-End para um software destinado a gerenciar eventos, como palestras, de maneira eficiente. O Front-End da aplicação foi desenvolvido com Angular CLI (versão >= 11.2.1), enquanto o Back-End foi construído usando C# e .NET, com o banco de dados MySQL Server Express.

Certificado de ConclusΓ£o

Este projeto foi desenvolvido durante o curso Udemy, ministrado por VinΓ­cius de Andrade.
VocΓͺ pode acessar o certificado diretamente β†’ aqui ←.

Índice

Funcionalidades do Projeto

A aplicação contém as seguintes funcionalidades:

  • 1. Uma Tela de Login, contendo um formulΓ‘rio com campos de email e senha.

    • O formulΓ‘rio de login sΓ³ Γ© validado com os campos preenchidos corretamente.
    • A senha deve conter 8 caracteres.
    • _O perfil do usuario palestrante possui trΓͺÊs guias: perfil, palestrante bio e redes sociais
  • 2. Uma Tela de Esqueci a Senha contendo um simples formulΓ‘rio com o campo de e-mail.

    • O formulΓ‘rio de Esqueci a Senha sΓ³ Γ© validado com o campo preenchido corretamente.
  • 3. Um Menu superior, contendo as opçáes Dashboard, Eventos, Palestrantes e Contanto

  • 4. Uma Tela de Cadastro de Palestrantes contendo um formulΓ‘rio com os campos de nome, nome da empresa, cnpj, e-mail.

    • O formulΓ‘rio de Cadastro de UsuΓ‘rio sΓ³ Γ© validado com os campos preenchidos corretamente.
    • A senha deve conter 8 caracteres.
    • No campo confirmação de senha, tambΓ©m possui validação, caso sejam divergentes nΓ£o serΓ‘ possΓ­vel o cadastro.
    • O cnpj deve conter 14 caracteres.
  • 5. Uma Tela de Listagem de Eventos.

    • Possui a funcionalidade de buscar um evento por localidade, assunto ou palestrante.
    • Γ‰ possivel recolher e expandir o grid com as imagens de divulgação dos eventos jΓ‘ cadastrados.
    • Γ‰ possivel editar ou excluir o evento desejado.
  • 7. Uma Tela de Cadastro de Evento, contendo um formulΓ‘rio com os campos nome do evento, responsΓ‘vel/palestrante, imagem de divulgação, rede social, tema, local, hora, data, quantidade de pessoas e lote.

  • 8. Uma Tela de Cadastro de Eventos, contendo um formulΓ‘rio com os campos nome, responsΓ‘vel.

  • 9. Uma Tela de Edição de Eventos, contendo um formulΓ‘rio com os mesmos campos presentes no Cadastro de Evento.

Como Executar o Projeto

Antes de utilizar esta aplicação, é necessÑrio ter o Node.js e o Angular CLI instalados em seu computador. Este projeto foi desenvolvido usando Angular CLI versão 11.2.1. Siga os passos abaixo para instalar e configurar o ambiente de desenvolvimento:

PrΓ©-requisitos

  • Node.js (versΓ£o >= 10.13.0)
  • .net (versΓ£o >= 5.0.402)
  • npm (versΓ£o >= 6.11.0)
  • Angular CLI (versΓ£o >= 11.2.1)
  • MySQL

Instalando o Node.js

  1. Acesse o site oficial do Node.js em https://nodejs.org/en/download/.
  2. Selecione a opção de download correspondente ao seu sistema operacional.
  3. Baixe e execute o instalador do Node.js. Siga as instruçáes do instalador para concluir a instalação.

Instalando o Angular CLI

  1. Abra o terminal do seu sistema operacional.
  2. Execute o seguinte comando para instalar o Angular CLI:
    npm install -g @angular/cli@11.2.1
  3. Aguarde o término da instalação.

Instalando DependΓͺncias do Projeto

  1. Clone o repositΓ³rio:
    git clone https://github.com/seu-usuario/seu-repositorio.git

Executando o Backend

  1. Navegar atΓ© o diretΓ³rio do backend:
    cd backend
  2. Iniciar o servidor backend:
    npm start
  3. Verificar a conexΓ£o com o backend: O servidor deve estar rodando em http://localhost:3000/. VocΓͺ pode verificar se o backend estΓ‘ funcionando corretamente acessando esta URL.

Executando o Frontend

  1. Navegar atΓ© o diretΓ³rio do frontend:
    cd ProEventos/Front/ProEventos-App
  2. Instalar as dependΓͺncias do frontend:
    npm install

ApΓ³s esses comandos, a estrutura de pastas do seu projeto deve ser semelhante a esta:

ProEventos/
β”œβ”€β”€ .vscode/
β”œβ”€β”€ Back/
β”œβ”€β”€ Front/
β”‚   └── ProEventos-App
β”‚       β”œβ”€β”€ e2e/
β”‚       β”œβ”€β”€ node_modules/
β”‚       β”œβ”€β”€ src/
β”‚       └── ...
β”œβ”€β”€ .gitignore
└── README.md
  1. Iniciar o servidor de desenvolvimento:

    ng serve
  2. Acessar a aplicação: Navegue para http://localhost:4200/. A aplicação serΓ‘ recarregada automaticamente se vocΓͺ alterar qualquer um dos arquivos de origem.

Executando Frontend e Backend Juntos

Iniciar o backend:

  1. Certifique-se de que o servidor backend estΓ‘ rodando primeiro. Navegue atΓ© o diretΓ³rio do backend e execute:
    cd ProEventos/Back/src
    npm start

Iniciar o Frontend:

  1. Para iniciar o servidor de desenvolvimento, execute:
    cd ProEventos/Front/ProEventos-App
    ng serve
  2. Navegue para http://localhost:4200/. A aplicação serΓ‘ recarregada automaticamente se vocΓͺ alterar qualquer um dos arquivos de origem.

Estrutura de DiretΓ³rios

ProEventos/
β”œβ”€β”€ .vscode/
β”‚   β”œβ”€β”€  launch.json
β”‚   └── tasks.json
β”œβ”€β”€ Back/
β”‚   └── src
β”‚   β”‚    β”œβ”€β”€  ProEventos.API
β”‚   β”‚    β”‚     β”œβ”€β”€ bin/
β”‚   β”‚    β”‚     β”œβ”€β”€ Controllers/
β”‚   β”‚    β”‚     β”œβ”€β”€ Controllers/
β”‚   β”‚    β”‚     β”œβ”€β”€ Extensions/
β”‚   β”‚    β”‚     β”œβ”€β”€ Helpers/
β”‚   β”‚    β”‚     β”œβ”€β”€ Models/
β”‚   β”‚    β”‚     β”œβ”€β”€ obj/
β”‚   β”‚    β”‚     β”œβ”€β”€ Properties/
β”‚   β”‚    β”‚     β”œβ”€β”€ appsettings.Development.json
β”‚   β”‚    β”‚     β”œβ”€β”€ appsettings.json
β”‚   β”‚    β”‚     β”œβ”€β”€ ProEventos.API.csproj
β”‚   β”‚    β”‚     β”œβ”€β”€ Program.cs
β”‚   β”‚    β”‚     └── Startup.cs
β”‚   β”‚    β”œβ”€β”€  ProEventos.Application
β”‚   β”‚    β”‚     β”œβ”€β”€ bin/
β”‚   β”‚    β”‚     β”œβ”€β”€ Contratos/
β”‚   β”‚    β”‚     β”œβ”€β”€ Dtos/
β”‚   β”‚    β”‚     β”œβ”€β”€ Extensions/
β”‚   β”‚    β”‚     β”œβ”€β”€ Helpers/
β”‚   β”‚    β”‚     β”œβ”€β”€ obj/
β”‚   β”‚    β”‚     β”œβ”€β”€ AccountService.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ EventoService.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ LoteService.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ PalestranteService.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ ProEventos.Application.csproj
β”‚   β”‚    β”‚     β”œβ”€β”€ RedeSocialService.cs
β”‚   β”‚    β”‚     └── TokenService.cs
β”‚   β”‚    β”œβ”€β”€  ProEventos.Domain
β”‚   β”‚    β”‚     β”œβ”€β”€ bin/
β”‚   β”‚    β”‚     β”œβ”€β”€ Enum/
β”‚   β”‚    β”‚     β”œβ”€β”€ Identity/
β”‚   β”‚    β”‚     β”œβ”€β”€ obj/
β”‚   β”‚    β”‚     β”œβ”€β”€ Evento.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ Lote.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ Palestrante.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ PalestranteEvento.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ ProEventos.Domain.csproj
β”‚   β”‚    β”‚     └── RedeSocial.cs
β”‚   β”‚    β”œβ”€β”€  ProEventos.Persistence
β”‚   β”‚    β”‚     β”œβ”€β”€ bin/
β”‚   β”‚    β”‚     β”œβ”€β”€ Contextos/
β”‚   β”‚    β”‚     β”œβ”€β”€ Contratos/
β”‚   β”‚    β”‚     β”œβ”€β”€ Migrations/
β”‚   β”‚    β”‚     β”œβ”€β”€ Models/
β”‚   β”‚    β”‚     β”œβ”€β”€ obj/
β”‚   β”‚    β”‚     β”œβ”€β”€ EventoPersist.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ GeralPersist.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ LotePersist.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ PalestrantePersist.cs
β”‚   β”‚    β”‚     β”œβ”€β”€ ProEventos.Persistence.csproj
β”‚   β”‚    β”‚     β”œβ”€β”€ RedeSocialPersist.cs
β”‚   β”‚    β”‚     └── UserPersist.cs
β”‚   β”‚    β”œβ”€β”€  global.json
β”‚   └──  └──  ProEventos.sln
β”œβ”€β”€ Front/
β”‚   └── ProEventos-App
β”‚       β”œβ”€β”€ e2e/
β”‚       β”‚   └── ...
β”‚       β”œβ”€β”€ node_modules/
β”‚       β”‚   └── ...
β”‚       β”œβ”€β”€ src/
β”‚       β”‚   β”œβ”€β”€ app/
β”‚       β”‚   β”‚   β”œβ”€β”€ components/
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ contatos/
β”‚       β”‚   β”‚   β”‚   |   └── ...
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ dashboard/
β”‚       β”‚   β”‚   β”‚   |   └── ...
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ eventos/
β”‚       β”‚   β”‚   β”‚   |   └── ...
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ home/
β”‚       β”‚   β”‚   β”‚   |   └── ...
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ palestrantes/
β”‚       β”‚   β”‚   β”‚   |   └── ...
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ redesSociais/
β”‚       β”‚   β”‚   β”‚   |   └── ...
β”‚       β”‚   β”‚   β”‚   └── user/
β”‚       β”‚   β”‚   β”‚       └── ...
β”‚       β”‚   β”‚   β”œβ”€β”€ guard/
β”‚       β”‚   β”‚   β”‚   └── ...
β”‚       β”‚   β”‚   β”œβ”€β”€ helpers/
β”‚       β”‚   β”‚   β”‚   └── ...
β”‚       β”‚   β”‚   β”œβ”€β”€ interceptors/
β”‚       β”‚   β”‚   β”‚   └── ...
β”‚       β”‚   β”‚   β”œβ”€β”€ services/
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ account.service.ts
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ evento.service.ts
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ lote.service.ts
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ palestrante.service.ts
β”‚       β”‚   β”‚   β”‚   └── redeSocial.service.ts
β”‚       β”‚   β”‚   β”œβ”€β”€ models/
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ identity/
β”‚       β”‚   β”‚   β”‚   |   └── User.ts
β”‚       β”‚   β”‚   β”‚   |   └── UserLogin.ts
β”‚       β”‚   β”‚   β”‚   |   └── UserUpdate.ts
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ Evento.ts
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ Lote.ts
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ Pagination.ts
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ Palestrante.ts
β”‚       β”‚   β”‚   β”‚   └── RedeSocial.ts
β”‚       β”‚   β”‚   β”œβ”€β”€ shared/
β”‚       β”‚   β”‚   β”‚   β”œβ”€β”€ nav/
β”‚       β”‚   β”‚   β”‚   └── ...
β”‚       β”‚   β”‚   β”‚   └── titulo/
β”‚       β”‚   β”‚   β”‚   └── ...
β”‚       β”‚   β”‚   β”œβ”€β”€ util/
β”‚       β”‚   β”‚   β”‚   └── ...
β”‚       β”‚   β”‚   β”œβ”€β”€ app-routing.module.ts
β”‚       β”‚   β”‚   └── ...
β”‚       β”‚   β”œβ”€β”€ assets/
β”‚       β”‚   β”œβ”€β”€ environments/
β”‚       └── └── ...
β”œβ”€β”€ .gitignore
└── README.md

About

The ProEventos project was developed to optimize event management. This repository includes the complete proposal for both Front-End and Back-End of an efficient software for managing events, such as lectures.

Topics

Resources

Stars

Watchers

Forks