• Disable search when still fetching
• Case insensitive search

Cache all authors and repos but detect specific changes to the list

Example:
A repo has been added to the project list. Then only the new repo related fetches should be called and then added to the project list cache

Add edit remove projects

Change the login from banner to a dropdown menu in the navbar

• Add loading overlay over manage page on add and delete

Sub task of #13

Create a login page for users.

• API usage
• Setting up firebase

Some more info in the readme

• Sort the different fields
• Search keyword. Target authorName, repoName, description
• Add support for choosing which authors to show projects from

• REACTOUR
• React Joyride

1. Show complete tour for new users
2. Spotlight the new features when they exist on the page

Previously, repository data is fetched fresh every time, so all the data are up to date.

Now that I've changed it to a way that when a repository is added to the list, the state of that repository is fetched and saved to firebase. And then this data is what is shown to the user.

But with this, we're no longer getting the latest data. My purpose was to save the calls to the Github API. But this doesn't seem to be the case anymore.

Add an about page to explain a bit more of the app, how it works, and what data are stored.

• Update settings stuff

Add loaderoverlay while checking for init on login page

Fetchhttps://api.github.com/repos/codesandcoffees/react-kit/events

Get first event and store the created_at as updatedAt to firebase. On fetching again, compare the created_at vs updatedAt from firebase.

Create a server side app to call Github APIs to bypass the rate limits

GraphQL seems to be promising since it's easier to get all the needed data in just 1 call.

Reads:

• Deploying a GraphQL Server with Cloud Functions for Firebase
• GraphQL Server on Cloud Functions for Firebase

• Add pre-deploy script to check if current branch is master
• Customized commit message in gh-pages

Customization of the settings: colors and stuff

Add more info on the repo cards:

• Show latest 5 activities/prs/commits

This will be not prioritized. I will prepare a documentation for forking.

This feature will allow users to add their own data if they choose not to fork the project.

I'm not sure if there will be a limit since Firebase has a limit and the API usage also has a limit.

Currently.
When user visits the site, they will only see my data. If they log in, nothing happens. They won't be allowed to do modifications since they are not me.

What this feature will bring.
When user visits the site, they will still see my data. But once they log in, their data will be fetched if there is. Then they can manage their own data.