We need to make specific routines for contributing to the project:

• Branch names always include your name (e.g. user-dropdown-jay)
• Commit rules for master
• How to make a PR
• How to use GitHub mentions, issue references, etc.

Is your feature request related to a problem? Please describe.
There is/will be too much data to not paginate the ideas feed. The ideas feed should be paginated.

Describe the solution you'd like
Ideally, a configurable number of feed items would be returned, and there should be a pagination component at the end of the feed.

Describe alternatives you've considered
Right now, every single idea feed item is returned.

Additional context
There's pagination build into feathers. By looking at feathers docs and feathers-vuex docs, we can probably get a solution together. There is also a pagination component in spectre css.

As a user, I'd like my submitted idea to automatically be upvoted by myself.

Change type: backend

I think Feathers hooks are the route to go with this... an after-create hook to put the users' name on the voted[] array.

thoughts @matthewess?

Users can't navigate to /signin, but if theyre on it and auth via token in the background then they don't get bumped. Desired behavior would be getting bumped to /ideas if a user auths via session

I was able to register two email addresses by manually clicking "sign up" on the frontend and reregistering my email address. Backend changes (Mongo probably?) needed to prevent multiple email signups.

@matthewess would you mind looking at this? you probably will have the best insight for making this backend change

Is your feature request related to a problem? Please describe.
Not a problem.

Describe the solution you'd like
I would like a Home Screen icon for iOS.

Describe alternatives you've considered
Pinning the icon to the homescreen leaves a screenshot icon, which isn't desired.

Additional context
Android, iOS, Windows, (& browsers) all have specific directives for app icons. We should add all. There's an easy library on GitHub that can do this.

Best case, we add them into the webpack or build configs; worst case, we do it manually.

Is your feature request related to a problem? Please describe.
I'm frustrated when I load a new component, but the page doesn't scroll back to the top. You can see this behavior if you read the Terms page, scroll to the bottom, click the Privacy Policy footer link. It does not scroll to the top.

Describe the solution you'd like
Scroll to the top.

Describe alternatives you've considered
I haven't really considered alternatives because this is just an expectation of how web browsers work.

README.md doesn't include information about how to load env variables to make the project run properly. It would be good to include a little info about dotenv and how it loads stuff to make the project

(Hey @matthewess you don't need to take care of this right away... using it as an example for PM stuff on Wednesday)

Bug description
The comment field automatically scrolls out of view on iOS browsers. The automatic scroll/positioning happens on each keypress.

Expected behavior
The comment field should be in view at all times the user is entering their comment.

Steps to reproduce the issue:

1. Open an idea from the ideas feed (on iOS browser. perhaps android as well)
2. Scroll to the bottom of the comments to type a new comment. (must be logged in)
3. On each keypress, notice the issue

Technical details:

• Platform (windows/mac/linux/docker): iOS
• Browser: Safari

Additional context
There's a mixin that handles this. It needs rewritten so that it doesn't autoresize and scroll away.

Bug description

My comments are not being displayed when I submit them. When I refresh the page, I only see json data.

Expected behavior

I expected my comment to show up.

Steps to reproduce the issue:

1. Go to any idea page
2. Type a comment
3. Click submit
4. Refresh

Technical details:

• Platform (windows/mac/linux/docker): linux
• Browser: Vivaldi, Chrome

Additional context
Here is the json data output:
{"_id":"5af5cad5294fab4130fdd8e4","voted":["5af5c8294d89f70028db78f4"],"title":"My Idea 4","description":"4","authorId":"5af5c8294d89f70028db78f4","createdAt":"2018-05-11T16:54:45.401Z","updatedAt":"2018-05-11T17:05:52.610Z","__v":0,"author":{"_id":"5af5c8294d89f70028db78f4","token":"vGynWAXK8NoieLkEjPLFpmKRHBw","email":"[email protected]","name":"Jay H","createdAt":"2018-05-11T16:43:21.418Z","updatedAt":"2018-05-12T05:29:06.790Z","__v":0},"comments":null}

It looks like my comment on idea 4 ended up on idea 3, and my comment for idea 3 ended up on idea 1

Bug description
JSON api response data is displayed in the browser. The frontend does not intercept the routes. We need to prefix the API on some level.

Expected behavior
I expect visiting /ideas/<idea id> will load the specific idea in the frontend.

Steps to reproduce the issue:

1. Visit OpenIdeas, and open any idea from the ideas feed.
2. Refresh the page.
3. See the JSON output.

Technical details:

• Platform (windows/mac/linux/docker): Mac
• Browser: Safari

Additional context
The API should be prefixed. There's a couple approaches, but I'm not knowledgable enough to say which is the best.