The only pet showcase you'll ever need! (Truly my pet project, until Parse went away, and I, sadly, never migrated it to a vanilla MongoDB with vanilla Backbone)
Can currently only see your own. Possible enhancement to allow for a private pet page but all pages should be public initially. This is likely resolved with a change to the parse query associated with the pet view route. (The actually Browse functionality is a separate issue).
Pet object has a name property and a uniqueName property. No conflicts yet, but need to let user choose or select an app-chosen uniqueName when there is a conflict (append a number as a default option)
Determine cases for when Masonry works as-expected and when it does not, to prep for demo and detail open issues. It does render pic collections properly on initial load, which is what counts. Intend to use Masonry for Browse view, as well.
It has been a coming-soon site and currently not up. Deploy an initial working version. (It has been regularly deployed as a Github page but Heroku site is where http://pett.io routes)
Because it's already essentially done. Even though, in practice, few might ever use it, I would like to implement it in a very basic way. As I did with the POC:
User asked to provide Vine account and tag in order to have last N vines rendered on pet page
The Flickr API POC that had referenced my own personal account is finally working per user setting, but tag setting applies to all pets, so all pets would get same Flickr photos.