sethetter/catalog-app-ui

Angular.js front end for Catalog App.

catalog-app-ui's Issues

User login interface

There should be a mechanism to handle registration and login for users. This should be the first page seen when visiting the root route and not logged in.

For now, the login process can be stubbed out with a json file containing fake user information.

New routes

Routes should be as follows:

/ - Login / register, or if logged in, redirect to /:username for currently logged in user
/settings - User profile / preferences for current user.
/:username - List of catalogs, with edit, remove, create actions if currently logged in user.
/:username/:catalog - An individual catalog owned by a user.
/:username/:catalog/settings - Settings for an individual catalog.
/:username/:catalog/:list - View of user defined custom list in a catalog.
/:username/:catalog/tag/:tag - View of all items matching specific tag in a catalog.

There will most likely be more, but this is a start.

User defined lists within a catalog

An owner of a catalog should be able to define custom "lists" that are viewable within that list. These lists are created based on filters that use the available custom item attributes in a catalog.

Public viewers may submit items to a list for admin approval. Items will be able to be viewed and edited by the catalog owner before entering the catalog.

The ability to view the list in the catalog menu for public viewers should be configurable, as well as the ability for public viewers to submit items to a list.

Should there be a wish list?

I think this would be a nice feature to have. I'm wondering what would be the best way to implement it.

One way would be to have a specialized "WishList" collection of catalog items.

A more generic approach could be to allow the catalog owner to create their own custom lists that include items based on certain criteria. Then custom tags or attributes can be added to catalog items for list criteria.

Catalog creation and management

Need to create an interface for listing, creating, and editing a user's catalogs. This view should be available at the user's username route /:username.

If the person viewing that user's list of catalogs is the currently logged in user, the edit, create, and delete functions will be available. Otherwise only viewing is available.

One of the attributes of a catalog will be the "list in public profile" option. This will determine whether other user's can see the catalog listed in your profile page.

Custom attributes on catalog items

The ability to define custom attributes that will be available on items in a catalog should be created. Eventually custom "lists" within a catalog can be defined based on these attributes.

New "attributes" on items should be able to be created within the new / edit item view. However, creating a new attribute should make it available to all items in the catalog (so available attributes should probably be saved at the catalog level).