espoo-dev / espoo-dev

A learning platform similar to duolingo and customizable by teacher

Espoo-dev

Frontend CI (semaphore)

Backend CI (Ruby.ci)

✨ Demo

1. espoolingo - login
2. espoolingo - register

Project definion

Espoo-dev is a learning platform. There are three roles:

• Teacher: Creates Surveys with many Questions
• Student: Answers the Questions that belongs to a Survey
• Admin: (only relevant for developers) Can manage everything

😃 Contributing

1. Slack

2. CONTRIBUTING.md

Current features

	Login	Register	Logout	List surveys	Select survey	Answer questions	Show survey summary
Web (React, TS, Next)	✔️	✔️	✔️	✔️	✔️	✔️	✔️
Mobile (Kotlin)	✔️	✖️	✖️	✔️	✖️	✖️	✖️
Fullstack (Rails)	✔️	✔️	✖️	✔️	✖️	✖️	✖️
API (Rails)	✔️	✔️	✔️	✔️	✔️	✔️	✔️

espoo-dev's Issues

config deploy ci - backend

configure lint ci - frontend

create survey

add relationship between "user and question"

create logout component - frontend

add capybara driver

configure deploy - frontend

fix semaphore error on build step

https://andersonmalheiro.semaphoreci.com/workflows/738964d5-b506-4327-99af-2fbdf1129d1e

create endpoint to delete question

create project - backend

Improve vercel permission

I receive an email from vercel, but I have no permission to access the url

Add uniqueness to role_type(string) in the Role model

create main admin page

create endpoint to create user

config docker and docker-compose

configure environments

Get server URL based on current environment

Create "option" entity

A question can have 0 or many options.
If a question has type equals to SingleOption or MultipleOptions it needs to have answers_options
An option belongs to a question

example 1:
question: What is the plural of "you"?
question_type: SingleOption
answers_options: option 2
option 1) they
option 2) you
option 3) it
option 4) she

example 2:
question: What are the singular of "they"?
question_type: MultipleOption
answers_options: option 2, option 3, option 4
option 1) we
option 2) he
option 3) it
option 4) she

create login page

add missing unit tests

add missing unit tests to components and functions already created

delete not used branches

There are some branches that are not being used and should be deleted :)

unify docker-compose

• Remove from frontend and backend, create one docker-compose in project root
• Update READMEs

create register page

Config heroku to auto run migrations

create endpoint to return roles

choose and configure css framework - frontend

improve error message when creating user fail

convert roles to a model and define with roles should exist by default

bug fix - users request are public but they should be private

create database diagram

create question endpoint

create endpoint to return survey by ID

Fix slim layout (backend admin login page)

Add surveys to user json

user json should have a list of surveys

create survey page

create initial config github actions

create home page with teachers list

configure deploy ci - frontend

Improve seed

fix register api url

create survey page

create nav bar - frontend

Improve CI config for semaphore

1. parallelize jobs for semaphore
   
2. configure monorepo monorepo2 for semaphore
3. set semaphore check as required
   
4. run ci for forked repos

add semaphore badge to readme

Add endpoit to return users by role

add type enum to question

create auth context

add system tests for question and question type

update database diagram

remove github actions

create project - frontend