[wp-meta] [Making WordPress.org] #262: Automate WordCamp Gravatar Badge Creation

Making WordPress.org noreply at wordpress.org
Fri May 24 15:30:23 UTC 2019


#262: Automate WordCamp Gravatar Badge Creation
----------------------------------------+-----------------------
 Reporter:  iandunn                     |       Owner:  (none)
     Type:  enhancement                 |      Status:  assigned
 Priority:  high                        |   Milestone:
Component:  WordCamp Site & Plugins     |  Resolution:
 Keywords:  needs-patch good-first-bug  |
----------------------------------------+-----------------------

Comment (by tinkerbelly):

 Attached above are rough mockups suggesting how this might work from a
 user experience point of view.

 Notes & questions:

 1. I struggled with getting the labels right here. "Ticket type" feels
 confusing because there are types of *tickets*, and also types of
 *attendees*. I tried to avoid the label "Admin flag" because it feels a
 wee bit unclear, but it may be that if whomever is generating the badges
 is familiar with the ticket setup process (in which they would have set
 the admin flag, or are those provided by default?) understands this
 phrasing.

 2. Instead of "generate registrations since [x] date", which requires that
 organisers remember the exact date (and possibly time, for accuracy) that
 they last generated tickets, what about a toggle that only generates
 tickets that haven't already been generated? This would require storing
 data somewhere about what tickets had been generated already, but would
 allow for much easier batch printing like this.

 3. Instead of using a modal and spinner and asking people to wait whilst
 the job completes, would it be possible to run the job in the background?
 This would allow people to navigate elsewhere rather than waiting around,
 and then we could allow for downloading generated badges in a centralised
 place as well.

 4. This is using components from `@wordpress/packages` for simplicity
 (since those components exist in Figma!) but it'd probably make more sense
 to use the default WordPress input controls here for now, so as to be
 consistent with other wp-admin pages. The checkboxes may end up being a
 wee bit harder to parse on large screen with the side-by-side label
 alignment, but otherwise the functionality will be more or less the same.

 Note for the future: it might  also be possible to finagle a way of
 generating these badges with Figma, which more designers may have access
 to (and can easily access via the WordPress account). That said, Figma
 isn't a print design tool, their API is still limited, and it might not
 wind up being helpful at all. It has [https://www.figma.com/blog/our-path-
 to-creating-the-highest-quality-pdf-exporter/ PDF export] functionality
 but doesn't support the CMYK colour space, or any crop marks on artboards
 (without a hacky solution). Just throwing it out there for future
 consideration.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/262#comment:17>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list