Tomster Compendium #1895

Activity

1. trek commented on Dec 27, 2014

   

   trek

   on Dec 27, 2014

   Member

   More actions

   We don't current have one, but I think that would be a great idea. @wifelette can get you a canonical list of Tomsters we've had made so far.
2. trek

   assigned

   trek

   and

   wifelette

   and unassigned

   trek

   on Dec 27, 2014
3. wifelette commented on Dec 29, 2014

   

   wifelette

   on Dec 29, 2014

   Member

   More actions

   Heya—

   This is already in theoretical development, but I blocked on resources, mostly design :p In theory we could get away with making it fairly bare bones... but I haven't been spending much time prioritizing it because I didn't have anyone to build it for me (been working on a revamp of the community page first).

   If you're interested, I'd love the help!

   The plan so far for the MVP:

   • The page (community/tomsters) ought use a bit of Ruby to pull all the content from a Yaml file, same as we've got feeding most of our other big lists (/community for meetups, /ember-users, /team, etc). That way, when I need to add new Tomsters, I'm just updating a Yaml page (and we can have other non-coder volunteers help this way too).
   • The fields in the Yaml file will be:
     • tomster_ID
     • tomster_name
     • tomster_purpose
     • purpose_link
     • date_designed
     • licensed_to
     • image

   Tomsters are created either for Ember core purposes, or they're commissioned by approved community use cases we then grant licenses to (for example, the London User Group Tomster, commissioned by them, licensed to them for non-commercial use). So the URL will point to the organization who commissioned the Tomster.

   We should do whatever little things we can to prevent people from snatching them up and using them. The directory will only hold pngs or jpgs, but if there's anything else simple to be done to the images we should do that too.

   Lastly, we'll have text with some info on how to get in touch if you wanted to commission a Tomster.

   V2 ideally has a profile of the illustrators and a web form for requesting commissions or licenses.

   Thoughts? You could probably start by putting together the page with the Ruby code, the Yaml file template, and lastly, basic tweaks to the CSS we're using on things like the List page to have it styled more appropriately for slightly larger images (a la the Octodex, two per line should be good too).
4. wifelette

   added

   design

   content 📝

   on Dec 29, 2014
5. nwjohn commented on Dec 30, 2014

   

   nwjohn

   on Dec 30, 2014

   Author

   More actions

   I pulled together a basic version of the of the yaml file with Ruby slicing together the table similarly to the teams page. I created on a separate branch, tomster-wip. Should I request for a branch tomster-wip be opened or just submit a pull request against the master or some other currently existing branch?
6. wifelette commented on Mar 17, 2015

   

   wifelette

   on Mar 17, 2015

   Member

   More actions

   Aloha @ncwhitehead! Hope you haven't lost enthusiasm for this... I got busy drowning in EmberConf :p EmberConf has however resulted in 5-10 new Tomsters being designed as we speak, making this page even more useful.

   Assuming this is something we could use community help on, and even if not, best bet is a PR with a To Do list so we can knock off all the little tasks to get this done.

   This is the last one we worked on in this section, and it went super well, with a ton of people jumping in to help: #1904

   Want to do the honors and we can start making more progress from there?
7. wifelette commented on Apr 17, 2015

   

   wifelette

   on Apr 17, 2015

   Member

   More actions

   Closing this issue because we're (mostly @sandraor, and I'm helping!) getting to work on this! We'll get it into a PR once there's stuff to share :)
8. wifelette

   closed this as completedon Apr 17, 2015