• Women, WordPress, & the Web

    This morning, Sarah Parmenter, a talented female web designer and frequent conference speaker, spoke up about the disgusting, abusive and degrading experiences she’s had as a female speaker. These kinds of experiences are not uncommon for women in tech. Women are underrepresented at conferences, and often when they are represented, they are sexually harassed, verbally abused, or are just plain talked down to. Attempts to discuss the lack of diversity and problem women face in tech conferences have even been met with disrespect and ridicule. (Aral Balkan does a good job of summing up that entire debacle.) It’s no wonder there aren’t as many women itching to speak at conferences:

    There’s many questions around why there aren’t more females speaking in this industry. I can tell you why,they are scared. Everytime I jump on stage, I get comments, either about the way I look, or the fact that I’m the female, the token, the one they have to sit through in order for the males to come back on again. One conference, I even had a guy tweet something derogatory about me not 30 seconds into my talk, only for me to bring up the point he had berated me for not bringing up, not a minute later – which caused him to have to apologise to my face after public backlash. I’ve had one guy come up to me in a bar and say (after explaining he didn’t like my talk)… “no offence, I just don’t relate to girls speaking about the industry at all, I learn better from guys”. Sarah Parmenter

    I want to talk a little bit about my experiences, specifically in the WordPress community. To start, though, here’s a bit about me. I’ve been taught from a young age that women are awesome. Though my mother might not have been the best parent as I was growing up, she is and always has been an incredibly strong woman who taught me, quite frankly, not to take shit from anyone. It’s something I internalized early. I spent thirteen long years as an active girl scout, being encouraged that whole time to be a strong leader and activist. This encouragement extended into my college years at Smith. Smithies are known for raising a raucous, and boy, do we like to give “the man” hell. Needless to say, I’ve never really been intimidated by “male spaces”.

    This leads me to WordPress. One of the things that immediately attracted me to WordPress was the number of visible women. I went to my first WordCamp (NY ’10) along with some coworkers. At that point I had probably spent about a year working on and off with WordPress, and had enjoyed it, but I wasn’t really in love with it like I am now. WordCamp NYC changed that. Part of it was the excitement, camaraderie and learning that comes along with any tech conference, but a bit part of it was who specifically was there. I was a little in awe of Jen Mylo, Automattic employee and the UX/UI lead for WordPress for several years. I still remember Sara Cannon’s session, Beyond the System Font. Women were involved with organizing the conference, women were volunteering, and women were speaking. It was my kind of place.

    I think one of the unusual(ly awesome) things about the WordPress community, in contrast to the overall tech community, is just how easy it is to find amazingly talented women to look up to. They’re everywhere: From designers like Jen Mylo, Sara Cannon and Chelsea Otakan, to Helen Hou-Sandi, rockstar core contributor, developer, and current UI team lead, to Siobhan McKeown, an amazing web writer now an editor at Smashing Magazine, to Lisa Sabin-Wilson, author, really dynamic and personable speaker, and now partner at WebDevStudios. I could go on listing people. The number of women working with, writing about, and speaking on WordPress is huge. WordPress really helped my find a place in the overall tech community. It really inspired me to start speaking, which is something I want to continue to do as I grow as a designer and a community member.

    Don’t get me wrong — I’m not saying the community is a bubble immune to discrimination, harassment, or all the other nasty things that plague the tech industry. I’m sure we have a lot of things we’re doing wrong. But my experiences within the WordPress community have helped positively shape me as a designer and as a woman, and for that I am thankful.

  • A review of the new Myspace

    If you’re anything like me, you haven’t touched your Myspace account in years. A social networking pioneer, Myspace’s fame waned with the rise of Facebook, which did social bigger, better, and more efficiently. Myspace was high school; Facebook was college.

    That’s why I was surprised and delighted to hear about the “new” Myspace. If you haven’t had a chance to check out the promotional video they put out a few months ago, check it out:

    It looked sexy, and boy was I intrigued. I signed up for the beta release and, low and behold, found an invite in my inbox earlier this week.

    Setting up my personal profile was a little confusing. Navigation is context-specific, so I had to click around a little before finding the option. (I’m also pretty sure that edit icon wasn’t there when I was trying to set up my profile, but I could be wrong) I’ve since gotten used to the context-specific navigation, but it was definitely a bit of a challenge the first day. I also had some trouble grasping the concept of “connections”, which is essentially Myspace’s “like.” You can connect with anything: music, mixes, images, videos, people, artists, etc. I still think it’s a little weird that you can “connect” with things that aren’t people, but at least it’s a consistent experience across the site.

    Screenshot of the new Myspace profile

    So far my absolute favorite feature has been Myspace’s new search. On any page, if you want to search, all you have to do is start typing. An overlay with your search pops up as you type. It organizes your results into relevant categories. It’s clean, simple, and really easy. Don’t actually want to search? Just press esc and you’re back to where you were.

    Screenshot of Myspace's new search functionality

    I’m going to let you guys in on a little secret: I love making playlists. Love it. I’ve spent hours in Winamp and iTunes making the perfect playlists for every occasion. Myspace’s process for creating “mixes” is one of the most seamless and enjoyable experiences I’ve had to date. I can search for music without leaving my mix page, unlike iTunes, where it’s a constant game of back-and-forth between playlist and library. If you’re listening to a genre radio or someone else’s mix, you can also quickly and easily add those songs to your mix from any page on the site. Your mixes get published to your activity feed so you can instantly share them with your friends.

    Unfortunately, I’ve run into a few frustrating spots with making mixes — the drag-and-drop reordering is a bit jagged. I’ve had trouble dragging songs from bottom to top, or vice-versa. Additionally, there’s no way to preview songs before adding them to your mix, so I’ve found a few available songs that are really bad quality. Lastly, the selection right now isn’t as awesome as I’d like it to be — a lot of songs I’ve found and enjoyed through services like Hype Machine and Turntable.fm are unavailable, and there’s no way to add your own music. Even still, Myspace’s mixes are definitely a step in the right direction.

    Myspace's new playlist feature

    Right now, there aren’t a lot of people using the new Myspace. Despite that, I’ve found myself coming back every day. This isn’t something I can say about Google+, which has all but been abandoned. Why is the new Myspace bringing me back when Google+ failed to? It’s actually quite simple — it doesn’t matter that no one’s using it yet. My enjoyment isn’t contingent on social interactions, but personal enjoyment of music. It’s everything I was hoping Spotify would be. Searching for music is fast and easy. Making playlists is fun, while on Spotify making a playlist is tedious, even agonizing. I can listen to albums or easily find mixes other people have made. The new Myspace isn’t trying to be the new Facebook, unlike Google+. It’s trying to be the new Myspace.

    Will it continue to keep my attention? Who knows. As of right now, however, I’d give the new Myspace a thumbs up.

    Want an invite? I’ve got one up for grabs! Tweet me your email @melchoyce.

  • Design for Non-Designers

    I presented today at WordCamp Philly on Design for Non-Designers. As promised, here are my slides, which I’ve fleshed out with some extra notes for web:

    If anyone wants the abridged version (which is what I presented), you can comment here to let me know.

    Along with my slides, I also gave a quick design demo. You can see the images and notes for my demo here:

    Some resources for each design principle I talked about:

    Thanks again to everyone who attended this morning!

  • I’m speaking at WordCamp Philly!

    I'm Speaking at WordCamp Philly

    I’ll be speaking at WordCamp Philly in a few weeks! (October 20-21, 10:15-11:00am in the Power User Track) Here’s what I’ll be presenting on:

    Design Basics for Non-Designers

    To non-designers, design can seem like a mysterious realm inhabited by natural artists — inscrutable beings whose heads are constantly in the clouds as they hunker down in Photoshop, desperately trying to get every last pixel aligned perfectly (Okay, maybe there’s a *bit* of truth to that). Realistically, design is just a series of informed decisions based on a set of principles guided by best practice. By learning the basics of design, you can make your WordPress sites and applications more usable and compelling. This session is meant for anyone new to design.

    Come and check me out if you’re there.

  • 3 Dynamic Web-based Stories

    The web is a pretty exciting right now. The significant and unprecedented change and improvement we’ve seen in the past two years is astonishing. There is a new level of interaction that was previously only achievable by using Flash. We’ve been unshackled from relying upon proprietary software to make significant interaction possible, and the web today is much better off because of that change.

    A particularly impressive trend I’ve noticed in the past year is how people are starting to approach digital storytelling. As an open and collaborative environment, the web has the potential to change the very way we tell stories. Just think about it — at this point, there are probably millions of people who read almost entirely on their portable wireless devices. I have personally started to pack away my collection of books because I almost exclusively read on my iPad. The ability to have my entire library with me at all times is seductive. It’s never been easier to find, buy, and read books.

    Storytelling goes beyond books, though. An interaction-friendly web allows for a new way to experience stories. Here are a few web-based stories I’ve found particularly impressive:

    Mega Shark Story

    Mega Shark is the story of a shark who finds himself ostracized because, well, he is a gigantic scary shark. The story leads you through Mega Shark’s quest to make a friend. The illustrations are gorgeous. The art style is lush and vibrant, emerging you in a stunning undersea world.

    Mega Shark screenshot

    The story looks just as good on iPad as it does on a desktop or laptop. The transitions are smooth and natural, evoking the feeling of flipping through a children’s book. It’s easy to imagine sitting down and read this story to your kid (or niece/nephew, in my case).

    Mega Shark Screenshot 2

    Mega Shark is, as far as I can tell, one of the first stories to be created, not adapted, for screens. And it succeeds — boy, does it succeed. It has proven that maybe there’s a very successful future for children’s books on the web. Not just as ebooks, but as living, breathing, interactive entities in their own right.

    However, if you do intend on reading this story to your kids, you might want to read it through all the way first. Just because, you know. No spoilers, but it’s good to know in advance what you’re sharing with your kids.

    The next story is definitely not for kids.

    Hobo Lobo

    Hobo Lobo of Hamelin is an ongoing, slightly risque and overall pretty bizarre take on the Pied Piper by Stevan Živadinović. It’s a parallax style site which responds very beautifully to gestures (though is sometimes a little too sensitive), at least on my Mac. Unfortunately it doesn’t work very well on iOS, but Stevan admits that with some effort it wouldn’t be too hard to make work well on all devices.

    One thing this story takes advantage of that Mega Shark didn’t was the ability to play sound and subtle animations to help captivate readers. Which some of the mechanics of the story need a little refining, it’s an interesting take on telling a story using the advantages of the web to enhance user experience.

    Hobo Lobo of Hamelin Screenshot

    Stevan was kind enough to write up an entire tutorial based around how he created his story, so if you’re intrigued or interested in doing something similar you should give it a read.

    The last example today is probably the most impressive case of storytelling on the web I’ve encountered.

    Why the Sky is Far Away

    Why the Sky is Far Away (Pixel Fable) is the web adaption of a Nigerian Fable about — as it says — why the sky is far away. It tells the tale of how Aondo, the Sky, fell in love with a beautiful woman and how that leads to him fleeing far away from the earth. This story is significant for a few reasons, the first of which is cultural:

    This project comes from the concept of Afro-Futurism. As a topic, Afro-Futurism is rooted in history and African cosmologies, using pieces of the past, both technological and analog, to build the future. It is concerned with African consciousness, especially in the Diaspora, and it explores the methodology of liberation.

    Pixel Fable Screenshot

    But Pixel Fable isn’t just culturally significant, it’s also technologically significant. The project is a hybrid solution of many different available web technologies. Like Hobo Lobo, it also uses parallax to help enhance and control the flow of the story. It has a bright, enchanting illustrative style that blends texture, geometry and photography. Pieces of illustration blend together, hide and appear as you progress through the story.

    The most remarkable aspect of the story, however, is what’s called augmented reality. At the beginning of the story, you’re prompted to print out augmented reality markers. At specific parts in the story, you’re instructed to hold up each marker to your webcam.

    Pixel Fable Screenshot 2

    When you hold up the markers and play the augmented reality segment, the marker you’re holding gets transformed on camera into a part of the story, effectively bringing you into the story itself. (If you aren’t using the markers, there’s a video you can watch of someone demonstrating.)

    With this fable, storytelling has transcended beyond written and spoken word into something integrative and immersive. It’s a beautiful example of the incredible capabilities of the web as a platform for storytelling, and it’s only the beginning. Just think of what might be possible for future stories on the web.

    Have any other good examples of digital storytelling? Feel free to share.

  • You Are Responsible for the Work You Put Into the World

    Recently, I finished re-reading Design is a Job by Mike Monteiro. It’s a handbook for designers. Even though it was my second time through, I still found it just as humorous, insightful, and groundbreaking as the first time. Topics range from working with everyone from clients to coworkers, receiving payments, delivering designs, and managing feedback. It’s a treasure trove of useful information for designers of all skill levels.

    While reading, I found that one concept really kept resonating with me: you are responsible for the work you put out into the world.

    During my career, I’ve put out a lot of work I wasn’t happy with, and a lot of work I wasn’t proud of. Sometimes it was because we ran out of time (I’ve had to pull together sites with under 10 hours of design budget for the whole project. Note for people making budgets: Never do this. Ever.). Sometimes it was because the client wanted it a certain way, and the client was allowed to make the final decision (I rallied against this. Every time. And every time, I lost that battle.) Sometimes, honestly, it was because I was lazy. Sometimes, I would think, “it’s okay that this work is subpar, because I’ve tried to stick up for my design before, tried to fight for the integrity of my work, and I failed. Maybe next time I’ll try harder. Maybe next time I won’t give up.”

    But during that time, I didn’t. Even if I did try harder, I didn’t win. Ultimately, the client was always allowed to override design decisions. It was infuriating. It was degrading. And it should never have happened.

    A while ago, I was the designer on a project that went downhill very quickly for a number of reasons. One of the biggest reasons, though, was our inability to control client feedback and expectations. While I’m not sure the project would have ever gone smoothly, it could have gone a hell of a lot better. The client was allowed to make a lot of design decisions. He would even create elaborate videos about his feedback where he would demonstrate the design changes he wanted. He would change our mockups and send them back to us. By the end of the project, I was a glorified pixel pusher. I objected throughout the whole process, and when I finally said I that I could not in good conscious continue to work on this project, I was told that I needed to get over it, and that I needed to finish the project so no one else had to pick up my slack. I needed to make everyone’s life easier and just make the changes the client demanded.

    So I caved. I did it, but I bitterly regretted it. I still regret it. It was the wrong decision. I should have said no. I hated the final product. And one of the worst things? In the end, the client never even used the site. It got launched with dummy content, and remains launched with dummy content, years later.

    Of course, that was a long time ago. Where does this put me now? Overall, pretty satisfied with my career. I’ve moved on to places that recognize the need for quality work, and ownership of the design process by those who have been hired for that task: designers. It’s been quite a while since I’ve put out work I was dissatisfied with. I feel proud as a designer, and I never want to slip back into pushing our subpar work again. I am responsible for the work I put out into the world.

    Design is a Job isn’t just a book about the design industry. It’s validation for all those times I fought for the integrity of my work. It’s a mentor. It should be every designer’s bible.

    If anything, read it for the lady bengal tigers. See? It’s already piqued your interest.

  • WCNYC: Brief Recap

    This past weekend, Kelly and I attended WordCamp NYC at Baruch College. It was my second WCNYC and overall, pretty fantastic. While the building we were in was very confusing, I was eventually able to find all of the rooms I wanted to go to sessions in. All the sessions I attended started and ended pretty much on time, which was a big change from the last WCNYC.

    There were a ton of sessions this year (over 12 tracks on Saturday) and a lot of really great design & front-end dev sessions I could attend. I especially enjoyed Jeremy Clarke’s session on DRY CSS and Sarah Winnem’s session on WP Template Hierarchy. There were a bunch of presentations I wanted to catch, but overlapped with other sessions I wanted to attend.

    I also spoke Saturday morning about Designer-Developer Communication. You can find my slides here.

    I met a lot of great people at the Speaker/Sponsor party Friday evening, and then again Saturday during the After Party. WP parties are definitely some of the best parties. I also got a chance to hand out a lot of my new business cards, which I’ll eventually be taking pictures of and posting up here.

    I had hoped to spend a lot of Sunday in the hacking room, trying to get involved in core contribution, but a lot of the attending core contributors ended up speaking on Sunday, so the room was mostly Codex editing and documentation. (We still met a few great people for the short time we were in there.) We watched a few of the Core presentations and the Q+A (which was both informative and highly entertaining) before the long trip back to MA.

    Overall, WCNYC was a complete blast and I’m really glad that we attended. Can’t wait for the next one!

  • WordCamp NYC!

    This weekend, I’m speaking at WordCamp NYC.

    Come by and say hi or tweet me at @melchoyce to meet up!

  • Soft-launched: redesigned choycedesign.com!

    If you’ve stopped by in the past week or so, you might have noticed a few (well, many) changes. I’ve redesigned my site!

    First, some quick insight into why. I’d been thinking about redesigning for a few months, but couldn’t decide on whether or not I wanted to completely redesign, or just refresh. My old site was static — it started out just html, then got a small upgrade when I learned a little php. That worked okay, but it made updating my portfolio kind of a pain. I eventually wanted to move my design-oriented tumblr directly onto my site, so I ended up setting up WordPress on a subdomain. However, this meant that even though I was keeping my blog on-site, there was a visual change between my main site and my blog (since I decided to use twentyeleven and keep it mostly unchanged).

    Well, with WordPress comes bliss and ease and all of those wonderful things. It was inevitable that I would move my whole site onto WordPress. Once I realized this, I debating whether or not to just convert what I had to a WP theme and call it a day, or make some changes. My old site was feeling a little monotonous, so I tried some simple refreshes in Photoshop. Nothing looked right. I got frustrated. I tried something new. It didn’t look right. I got frustrated.

    Finally, I managed to design something I liked. Then I sat on it for a few weeks. The more I looked at it, the more I wanted to simplify it. I tried an interior, scrapped it. Tried another interior, scrapped that one as well. I looked back at the homepage, and realized, did I really need that much text? I’m not much of a text-person. I don’t really blog all that often. Are my tweets even relevant?

    So, I decided to cut it down. I cut it down so much, I ended up with just a catchphrase. There was something really simple about it that really pleased me, so I ran with it. It was around that point that I realized I wasn’t going to get much further in Photoshop, so I decided to jump head-first into designing it in-browser as I went along.

    It worked out okay for me. I started with the _s WordPress theme, but ended up getting a little lost (I’m not much of a developer). I’m pretty comfortable and familiar with Toolbox, so I switched over to that and really got rolling. Interiors came pretty naturally from there. Things probably aren’t as cohesive as they would have been had I done it all in Photoshop, but I really need to just do it, or else I wasn’t going to do it at all. I had some fun trying out new things, such as Isotope and Lettering.js. Lettering.js was especially nice, since Chaparral had some pretty horrendous default kerning.

    Overall, I’m pretty pleased with my results. I wanted something simple and clean, and I think that I’ve mostly managed to achieve that. It’s still a work-in-progress, of course. A few things I have left on my list to complete:

    • Responsiveness. I know in my head how it will respond to difference browser sizes, just need to get it down in code.
    • Decreasing FOUT
    • Fixing some colorbox/isotope compatibility issues on my portfolio page… colorbox shows all images in a gallery by default, even if they’re hidden, so I need to fix that so it only cycles through filtered results.

    Thanks are also in order for a specific awesome person who helped me out. Thanks, Kelly Dwan, for being my dev support and helping me integrate Isotope with WordPress. You’re a champ. Seriously.

    Anyway, if anyone sees anything odd or things something I’ve done is awkward/looks bad/can be improve, let me know. Iteration is a healthy thing.