bowfolios / bowfolios_blaze

Portfolios and networking for the University of Hawaii commnity.

For details, please see http://bowfolios.github.io/.

bowfolios_blaze's Issues

Use methods, remove insecure package

Please do work for this task in a branch called issue-15.

• Implement Meteor Methods for all DB updates.
• Remove the insecure package.

Remove Semantic UI auto-theme generation

Please do work for this task in a branch called issue-22.

The package structure for BowFolios can be made more simple, and startup times might improve, if instead of generating the CSS from the LESS files, we just put direct links to the CDN files for Semantic UI into the .

Mockup landing page

• Do work for this issue in branch 'issue-1'.
• Create an HTML mockup for the landing page.
• Here's a sketch:
  

Update testing to dispatch:mocha.

Please do work for this task in a branch called issue-21.

Update bowfolios to use dispatch:mocha. This includes both the code and the screencast.

Add administrator account and role

Please do all work for this task in a branch called issue-14.

Define an administrator role.

• Use the alanning:roles package.
• Specify the administrator username(s) in the configuration file.
• The administrator gets an additional menu item in the navbar called "Interests".
• The Interests page allows the administrator to add and remove Interests. Interests cannot be removed if any user has specified it as their interest.
• Only administrators can access the Interests page.

Create fixture for test data

Please do work for this in a branch called issue 8.

Implement a json file that's loaded on startup when there is no data that initializes the database with sample interests and a couple of users.

Mockup profile page

• Do work for this issue in the branch 'issue-2'.
• Create an HTML mockup for the profile page.
• Here is a sketch:
  

Install meteor-application-template

• Do the work for this issue in a branch called 'issue-5'.
• Use meteor-application-template to get the ball rolling on mockup development.

Implement Profiles Collection

Do all work for this issue in a branch called issue-6.

For this task,

• implement the Profiles collection.
• implement a set of unit tests.

Add UH test CAS login

Please do work for this task in a branch called issue-12.

• Hook up CAS authentication following example in meteor-example-uh-cas
• Profile and filter pages require authentication.
• Landing and directory pages do not require authentication.
• When users login, the system checks to see if a Profile document exists for that user, and if not, one is created.

Connect filter page to data model

Please do work for this in a branch called issue 11.

Generate the filter page from the contents of the database.

Connect profile page to data model

Please do work for this in a branch called issue 9.

Enable the profile page to manipulate the data model.

Migrate to NPM simple schema

Please do work for this task in a branch named issue-20.

Convert the bowfolios code base to node simpl-schema

Mockup directory page

• Do all work for this issue in the branch 'issue-3'.
• Create a mockup of the directory page.
• Here's a sketch:
  

Connect directory page to data model

Please do work for this in a branch called issue 10.

Generate the directory page from the contents of the database.

Provide filter and profile links in navbar

Do work for this task in a branch called issue-13.

• Add filter and profile links to navbar for logged in users.

Mockup find page

• Do all work for this issue in the branch 'issue-4'.
• Create a mockup of the find user page.
• Here's a sketch:
  

Implement Interests collection

Do all work for this issue in a branch called issue-7.

For this task,

• implement the Interests collection.
• implement a set of unit tests.

.

Create native mobile app.

Do work for this task in a branch named issue-19.

For details on how to do this, see:

• https://guide.meteor.com/mobile.html
• https://www.meteor.com/tutorials/blaze/running-on-mobile

Improve ProfileCollection unit testing

Please do work for this issue in a branch called issue-16.

There are a couple of erroneous situations not tested in the ProfileCollection unit tests:

• Defining a Profile with undefined Interest Strings.
• Defining a Profile with duplicate Interest Strings.

To fix the first requires adding a new test case to ProfileCollection.test.js.

To fix the second requires adding code to ProfileCollection.define() to throw an error when an attempt is made to define a Profile with duplicate Interests, and then adding a test case to ProfileCollection.test.js to test that the error is thrown.