Web client of QuePasa - The collaborative, community governed Event Calendar (React & GraphQL) quepasaorgiva.com/
Find a file
Amit Jakubowicz 4298fa3397 Create form
2018-09-16 20:09:19 +02:00
functions Create form 2018-09-16 20:09:19 +02:00
public Get firebase to work 2018-05-18 10:35:28 +02:00
webapp Create form 2018-09-16 20:09:19 +02:00
.firebaserc Get firebase to work 2018-05-18 10:35:28 +02:00
.gcloudignore Builds and deploys 2018-04-02 20:23:44 +02:00
.gitignore Configure functions from CI 2018-05-19 12:57:03 +02:00
.gitlab-ci.yml Separate build commands 2018-09-14 16:16:39 +02:00
Dockerfile esModuleInterop 2018-09-08 22:23:44 +02:00
firebase.json Remove predeploy actions, use gitlab ci only 2018-09-02 18:29:36 +02:00
Makefile Stop spitting out secrets in cleartext form 2018-06-01 13:22:11 +02:00
package.json Remove fetch-isomorphic from the whole project 2018-07-08 15:24:54 +02:00
README.md Add README and save events 2018-06-09 09:08:29 +02:00
tsconfig.json Refactor for classes 2018-05-04 19:53:16 +02:00
webpack.config.js Builds and deploys 2018-04-02 20:23:44 +02:00
yarn.lock Update lock 2018-07-08 15:25:06 +02:00

Communal events calendar

This is a weekend project of mine and you can use this code at your own risk as there is no guarantee that this code is secure or complying to any privacy rules.

Motivation

I often visit a region that I like very much. I like it because it's very rural and has a lot of beautiful nature. There's also a lot going on, and tons of great people but there is nowhere to get information about all the events going on. I would like to provide a place for people to promote their events and get informed about what's going on in their communities. A place that respects the user's privacy and strengthen local communities.

Features

Following is a list of existing and planned featured for an MVP. The non checked boxes indicate a to do item.

  • CI Pipeline for deployment on staging
  • CI Pipeline for deployment on production

Server-Side Features (non-check is to do)

  • passwordless authentication via email invitations and cookie sessions, with external dependencies only for persistence and email service
  • Basic integration with google calender REST API for saving just the time of an event
  • Aggregation of event data with a gcal event (The idea is to only share the minimum necessary with gcal, and to take advantage of the scheduling features only of recurring events etc')

Client-Side Features

  • Set up a project structure for a web client
  • List events
  • Filter events by tags
  • Sign up feature
  • Sign in feature
  • Nicer email templates for the authentication features
  • Add event feature available for users with an active session