The climateconnect from climateconnect

Create database table to store projects

Sketches:

Implement simple forum

This issue is a requirement of climateconnect/climateconnect_archived#32
Ideally a reskinned open source solution, that is compatible with out system, should be used for this to avoid additional work.

Requirement: needs to include sections, that are only accessible to specific user groups

Create progress component

Relates to #14

Create a generic progress display component

Design System for proposing changes to the impact algorithm

This issue is a requirement of climateconnect/climateconnect_archived#32

Implement badges for users

These badges can be given out as rewards.
Badges should be shown in the profile page. Users should be able to have multiple badges but only be able to choose one badge to display in their profile. This badge will be displayed whereever a user's profile is mentioned..

Make decision on database system

Possibilities are for example
-Elasticsearch
-MongoDB
-Postgres
-Redis Store for some parts

Design reputation system

The inspiration for the reputation system is bitcointalk's merit and trust system.
The idea is to have assign a pool of people you trust as the "default reputation pool". They can give out as many reputation points as they wish to users. Anybody outside that pool can give half the reputation points, that they received, to other users. There is going to be a forum topic for reputation fraud and reputation can be revoked from users if enough default reputation users vote for it.

Create database table(s) to store organizations

Sketches for layout(s):

Add data of 6 interesting projects

We already have one - "CO2-labels for university canteen".

To do user testing with a prototype, we'll need to have 5 more interesting projects, that are shown on the main page. This is because the main benefit of the platform comes from the quality of projects, that are on there. Test users will take the content on the page into account. If we only have one cool project, it's less likely, that they want to use the platform when we ask them to put their projects on there at a later stage. Therefore we should have 5 more interesting projects, preferably from different sectors and different types of organisations.

Set up database system

The database should be accessible from anywhere during development

Create project preview component

Create a component that encompasses the elements in the below image

Create Organisation page

Create a page with an overview over an organisation.
This should include a picture, a description, a list of the projects of that organisation as well as a list of their members.

Implement impact review system

This issue is dependent on #24

Take into account the reputation score of users as well as confirmed local users

Design gamified reward system for impact, activity and reputation

This issue is a requirement of climateconnect/climateconnect_archived#29
Design certain cool ranks or symbols that you get when reaching a certain threshhold of activity, impact or reputation. Activity can include reviews, feedback comments, ...

Create generic tab component

Relates to #14

Create a generic tab component component based off material-ui component

test issue for slack

Implement first screen of "Create a project" workflow

This is a sub-issue of #11

Create this interface: https://xd.adobe.com/view/395518bf-7e51-4eb2-6ff2-3f1b57fdaa17-4f64/screen/8080cb18-a8ac-43d2-ad78-8512918a0e29/Create-Project-Step-1

This should be the first screen (organization, project name, and location).

As we are building a front-end only prototype atm, we're using json files for data that will later be pulled from the database.
If a user is part of multiple organisations, they can choose in the name of which organisation they want to create a project on this page. Therefore you'll need to create a json file with a mock user-object, which just contains 2 different mock-organisations out of which you can choose in this interface.

For location, one possibility would be to use the https://nominatim.openstreetmap.org/ db for autocomplete. For the mockup it would be fine if this is just a text field without validating the location

Create interfaces for filtering/searching projects on the main page

Specifications will follow shortly

Calls these API route(s):

#119

Create generic button component

Using Material UI as a base, create a generic button component to be used across the app.

Needs outline and solid style options

Implement system for proposing changes to the impact algorithm

This issue is dependent on #29

Implement basic impact algorithm

Even if the impact calculation is not completely finished yet, an example impact calculation for specific project types should already be implemented into the "create a project" workflow and the "project" page.

Implement project preview list on the front page

This page: https://xd.adobe.com/view/395518bf-7e51-4eb2-6ff2-3f1b57fdaa17-4f64/

Prevent showing normal buttons on mobile for a short time before the burger icon is shown

Right now if you load the header on mobile, the normal buttons are shown until javascript kicks in and replaces them with the burger icon. If possible, we could use css to do that job to prevent the waiting time and prevent issues with users who don't have javascript enabled.
If we keep using javascript to do that job, the normal buttons should be shown only to users who have javascript disabled. For users who have javascript enabled, the header links should only be shown once javascript knows the screen size.

Use Material UI across the site

Create "sign in" page

Create interfaces for filtering/searching users on the main page

Specifications will follow shortly

Calls these API route(s):

#120

Create env variable that enables us to deploy just the static pages from the dev branch

Right now we're deploying pre-launch-website branch to climateconnect.earth. On that branch all pages besides a few necessary static pages are commented out.
The problem with this setup is, that we need to always manually comment out new pages, if we merge in develop and this might lead to manual errors. Therefore we should create an env variable PRE_LAUNCH.

In PRE_LAUNCH mode, if you access the main page should serve the /about page. Also none of the links in the header besides the logo should be shown. The only other pages, that should be accessible are /impressum and /faq. The footer can be shown as usual.
This depends on #49

Design "Sign up" workflow

This issue is a requirement of #5
Think through all options needed for the sign up process. An example walkthrough can be seen at https://xd.adobe.com/view/395518bf-7e51-4eb2-6ff2-3f1b57fdaa17-4f64/screen/dc5a4350-f691-4d73-b45d-3e8ab36691e6/Create-Account-Interface-Step-1

Design "Create an organisation" workflow

This issue is a requirement of climateconnect/climateconnect_archived#11

Create organisation page

Create a page with an overview over an organisation.
This should include a picture, a description, a list of the projects of that organisation as well as a list of their members.

Implement header and footer in react

Keep authentication in mind when designing the header and footer

Create a project: create interface for specifying the details of the project

Mockup here: https://xd.adobe.com/view/395518bf-7e51-4eb2-6ff2-3f1b57fdaa17-4f64/screen/efb34c3b-643e-42b8-a20b-6823e460440a/Create-Project-Step-2

Calls these API route(s):

#11

Create Timeline Component

Relates to #14

For the progress tab on the project page, create a timeline component as seen on the bottom of https://xd.adobe.com/view/395518bf-7e51-4eb2-6ff2-3f1b57fdaa17-4f64/screen/bdf48a4e-501b-482a-a052-24f94e9e1baa/CO2-Labels-Project-Page-Project

Design "create a project" workflow - without impact calculation

This issue is a requirement to #11.

-make a list of all possible project types
-refine this draft of a project creation page https://xd.adobe.com/view/395518bf-7e51-4eb2-6ff2-3f1b57fdaa17-4f64/screen/efb34c3b-643e-42b8-a20b-6823e460440a/Create-Project-Step-2

The impact calculation is very complicated and will be finished in parallel to developing the platform. Therefore it is going to be excluded from the first design

the interfaces of #114

Functionality:

Inserts a new user into the users table. This entry will be marked as confirmed=false. This makes the account unusable until it is confirmed
Sends an email with a link to API route to confirm your email address (#115)

Restrictions: