December 10, 2017 — Using WordPress to queery (not a typo) data and generate statistics based on the entire history of television and understand the impact of fictional death in the media on real life people. As seen on https://lezwatchtv.com
This presentation will discuss the complications of using WordPress to manage a site filled with cross-related data, in order to understand the social and psychological impact of the Bury Your Gays trope on TV. By using WordPress, we were able to easily output the data, but building out a site without planning what data will be captured leads to headaches. There were difficulties in the growth of data, including handling multiple actors and shows, with separate roles, characters who changed names and genders, and the death and revival of another character (does she count as dead)? Through it all, we prioritized open data and open discovery of the data to allow people to take the content and use it for their own purposes.
– The dead lesbian / bury your queers trope (see also: The Lexa Effect of 2016)
– Rest API for data promulgation and distribution
– Confirming theories with data
– How WordPress makes it ‘easier’ for people to find themselves reflected in media
December 6, 2017 — Suggested tag: Plugins
The part of your plugin that is hardest is the part that isn’t the code. Developing your first plugin for the WordPress directory means thinking beyond yourself and your own goals. In this workshop we’ll build a plugin together, a simple one, and work through the common pitfalls like function names, user permissions, and how much to sanitize.
August 9, 2017 — Have you ever wondered WHY you can’t do some things in plugins? Why we don’t let you use your own jQuery or call wp-load or offload images? I’ll tell you the real reasons why your plugins get flagged for fixes beyond the obvious like….
* Call my own jquery
* Call wp-load directly
* Offload images
* Put Google Analytics on the Backend of my plugin/theme
* Use FancyBox 2.x
* Name My Plugin X….
This talk will be CODE LITE, so if you’re working on your first plugin or want to get started, this can be for you!
August 7, 2017 — One of the things that makes WordPress as amazing as it is is the vast community of people who give so freely of their time and expertise to make it that way. And there are all kinds of ways, beyond being an ace coder, to make a contribution and become part of the ecosystem. Come listen to a panel of regular folks talk about the ways they are involved in supporting and growing the WordPress community and WordPress itself. If you’ve benefited from this generous community and are ready to pay it forward, this promises to be a fun, inspiring panel and will give you ideas on ways you can contribute, too.
August 5, 2017 — Writing the code is the easy part. Naming things, figuring out versions, and handling all that in SVN is not as easy as it should be. Even experienced developers mess this one up. Regularly. So don’t feel like you’re a loser if you don’t get it. Be prepared to Google and keep an open mind.
June 4, 2017 — You wrote a really awesome bit of code and submitted it to the directory, only to find out your code MAYBE wasn’t so great. And worse, even after it was approved, people can be pretty terrible about things. Judgmental. Mean. And now you have complaints, conflicts, bad reviews, broken code, security patches, and more. AUGH!
Everyone’s first plugin sucks. Everyone runs into unexpected conflicts. Learning how to handle them is what will take you from a good developer to a great one.
In this talk, I’ll discuss :
* That first review (what really happens)
* Preventing name conflicts (classes, functions and when to use if-exists)
* Replying to reviews (and when not to)
* Replying to support tickets (and when to say ‘no’)
* Handling security reports (what we really mean by ‘responsible disclosure’)
December 11, 2016 — One of the bigger take aways from my WCEU talk is the reminder that your representation in the WordPress community is not your code but you. This talk will address the issues when we have to represent something bigger than ourselves, be it the company we work for or the community in general. How do you handle the days when people hate you for nothing more than enforcing rules? How does it feel to have your reputation shattered when you know you did right? When DO you fight back if you do at all? How do you do it without causing more harm than good? After 14 years working for a bank and 4 for a webhost, with 6 in the middle helping the .org community in support and plugins, I have a unique set of experiences to call from when it comes to remembering the biggest thing. I am not my code. And I am not the haters.
December 2, 2016 — Have you wondered what goes on when a plugin is reviewed? Want to know tips and tricks to making your plugin pass on a first go? Curious about what happens when a security issue is revealed in a plugin? As the representative for the plugin review team, I handle everything from reviews and reports to sock puppets and trademark infringements, and I can answer your questions about all of it.
June 30, 2016 — Why You Want a Four Star Review Everyone gets bad reviews. It’s the nature of the beast when you put your product and code out there for everyone to use and abuse. But too many people spend their time fighting the wrong battle and striving for the wrong ratings. Don’t become the death of your own product; handle your reviews sanely and you will be the success you’ve always wanted to be. Key Takeaways: What to look for in reviews, how to take good from the worst reviews, how to handle yourself in bad reviews, understanding what is experience, making the most of reviews.
March 29, 2016 — When you submit a plugin, it seems to fall into a big black box. Then, suddenly, you get an email telling you things that are incorrect and need some attention. What actually happens is at once incredibly simple and painstakingly annoying. I should know. I do it every single day. And I’m here to help you understand what it is.