Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussion: New backend #118

Open
mateoclarke opened this issue Dec 18, 2017 · 0 comments
Open

Discussion: New backend #118

mateoclarke opened this issue Dec 18, 2017 · 0 comments

Comments

@mateoclarke
Copy link
Contributor

Creating this issue as a placeholder for discussion around replaced Airtable API as our backend.

Right now, we use Airtable's API to pull in data about projects. We did this for the prototype because it was easiest for the main content editor @danielhonker to use. We have already hit limitations with Airtable (see #75). And we know that as we add more content editors, we need a better experience.

We would also like to think ahead to a feature where a user (non-admin) could subscribe to a Project and get notifications. This feature may require user accounts.

Right now, this is low priority as we continue user testing with the data we currently have. But as we try to prevent data from going stale, this will become more important.

@mateoclarke mateoclarke changed the title Create a new backend Discussion: New backend Dec 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant