uva-slp / pauselab Goto Github PK

Figure out the arrangement/flow of how users can navigate through the site.

Wireframe for all the pages/workflows.

The public should be able to see artist proposals after approval by moderators -- not all fields need to be presented (e.g. checklist) -- only the relevant things like description

After an artist has submitted a proposal and that proposal has been approved and they have been assigned to a project, they have the ability to post blog posts on the public blog. Also the public view of the blogs should be aggregated into a single page.

Incorporate a map that allows residents/mods/admins to view the location of a proposed idea with markers in those locations with the ability to click on the markers for more information.

Linked to #6

When artists sign up or have signed up for a project, any updates will be emailed to the artist.

To prevent bots from spamming the site with submissions

Sort proposals via MySQL table fields, make interface easy to use and understand

Duplicate of #13

If a person submits an idea at the site where they want to take action, they should be able to use geolocation services to fill out the location field automatically.

Look into how this might be provided.

If there were good ideas/proposals that did not get funding, provide a way for moderators to save them and in the next cycle either resubmit them or expose contact information so they can reach out to the idea creator again.

Conditions on who can the vote in the system based on what residents decide (age, location, etc.)

Set up TravisCI.

Adding unit tests will be an ongoing task for all devs.

For residents that do not have access to a desktop, but a smartphone. We're still deciding what functionality is necessary for the mobile site. It will likely just be responsive design (i.e. web pages will fit on small form factor devices).

The public should be able to see proposed ideas (after approval by moderators), ideally in a map view (where points on the map are the proposed locations of the projects). Clicking on an idea brings up a description.

Requires some integration with a Maps API.

If people forget their credentials, there should be some mechanism for restoring access to their account, possibly though a password reset feature.

Create a simple MVC website where anyone can submit an idea including name, email, and description

Some sort of auto-generated page that reflects the journey an idea has been through, from conceivement to realization.

Aggregate blog posts by artists into one view, likely chronological (linked to #16)

We should investigate existing blog tools.

Information like clicks and page loads can be useful in assessing how site can improve. Investigate an existing telemetry tool and develop pages for admins to view the data.

Confirm with client

Steering committee should have a view of ideas that lets them quickly assess which ones are popular (through a like counter or number of comments). This would mean lists + filters for ideas.

For users of site with accounts, look into using Gmail/Facebook/Microsoft account for authentication and authorization.

Confirm with client first

Create a workflow for viewing idea submissions for moderators. Moderators need to screen the content of an idea (for e.g. inappropriate words) before approving it to be seen by the public. This should be a quick process (easy to consume and approve).

How will this happen? Some sort of user system like Twitter or Facebook? Can artists view each other's proposals? Can they submit proposals as team?

Figure out some prebuilt editor component that can be embedded for descriptions when posting ideas and artist proposals.

Would be nice, but not necessary. We still have to figure out WHERE this feature would be implemented.

In case the artists are anxiously waiting for a decision.

Once site is working, email Bloomfield and have him configure it to http://server/pauselab.

After the idea submission and artist response phase has been completed, the approved ideas with artist backing are listed for the public to like anonymously.

IP Address? Name? email? Street Address?

Depending on whether the org is in the ideas collection, proposal submission, voting, or results phases, a different webpage will need to be front and center on the site.

Provide a way for admins to easily switch out which view is prominent.

To prevent voting fraud

Artists have the ability to create accounts with their information, including online portfolios. They can then have access to information such as budget and checklist pages (etc.).

To see where the community is trending towards in terms of ideas

In the public view of an idea, people should be able to share via Facebook or Twitter. The content of what's shared should be automatically filled (to some extent).

Requires Facebook/Twitter API.

Figure out what contents will be inside a form:
Title, information, location, date submitted

If we want the ability to have multi-language support (e.g. Spanish), our views will have to be designed with that constraint in mind (it's likely frameworks already exist).

Confirm with client

Categories are set ahead of time by moderators to sort ideas for public approval. Categories can be added/subtracted/changed as needed.

Creating various types of users: admins, moderators, artists, residents, steering committee.

Look into a Ruby authentication module.

An initial database schema representing idea submission by users should be created.

Once the idea submission phase has elapsed, artists can view the approved projects and submit one page responses (with pictures) if they want to take on the project.

Ensure there is strong documentation of how to install and use system so that it's useful once handed off.

Ensure code itself is generally well documented.

This is an ongoing task for all devs.

Once an idea has been approved by moderator, allow public to post comments (e.g. to refine the idea). These comments will likely need to be approved by moderator as well, meaning another workflow (similar to ideas approval) will need to be developed.

The homepage should be different depending on when in the submission process the site is in.

Getting a Ruby on Rails development environment set up locally and committed to GitHub.

After artists submit proposals, steering committee should be able to view proposals in (1) a bulk view with filtering capabilities and (2) single item view of whole proposal.

""

This is based on the information gathered from the ideas submissions, possibly more e-mails entered from a different portal.

Paper vs. e-mail vs. desktop site vs. mobile site. This will give pauselab an idea of which advertising methods are most effective within a community.