davidbisset.social

wcsf14

  • “A developer is a composer of music.” @helenhousandi #wcsf #wcsf14

  • “Music, like code, is a structured language. There’s an element of personal artistry.” @helenhousandi #wcsf #wcsf14

  • #WCSF IS A TRAP! All of us are walking out of here employees of: @automattic @webdevstudios @10up @reaktivstudios or @crowdfavorite #wcsf14

  • “What is a website? Your fridge might respond to a HTTP request… does that make it a website?” @jeckman #wcsf14 #wcsf

  • “Do some research with people (like @squarespace) to see how they approach problems differently.” @jeckman #wcsf #wcsf14

  • “The four freedoms” @jeremyfelt #wcsf #wcsf14

  • .@jeremyfelt talks about sharing with the research community. #wcsf14 #wcsf

  • “Corporate wants more multisite options, more granular import/export, and JSON API.” @rachelbaker #wcsf14

  • “Corporates want to use WordPress because it’s flexible and they want to OWN their own data.” @rachelbaker #wcsf14

  • Wow. In a few minutes @rachelbaker is showing how corporations uses WordPress. #wcsf #wcsf14

  • “We are narrowly focus WordPress, but theres a larger web not using it. We should learn from them. ” @jeckman #wcsf14

  • Hey #wcsf14 sponsors: you’ll win if you offer free backpacks so attendees can carry more of your competition’s #wcsf swag.

  • Here’s a great getting started guide for translating WordPress: translate.wordpress.org/getting-started @nacin #wcsf #wcsf14

  • “2/3 of all WordPress installs are in English… but 10% of the world speaks English (5% English first language).” @nacin #wcsf #wcsf14

  • All developers need to do to translate your WordPress plugin. @nacin #wcsf #wcsf14

  • “WordPress doesn’t just support big languages. One translation only currently supports 3k users. Size doesn’t matter.” @nacin #wcsf #wcsf14

  • “WordPress 4.1: you’ll be able to switch to a new language in your dashboard.” @nacin #wcsf #wcsf14

  • “WodPress 4.0 is fully translated to 41 languages.” @nacin #wcsf #wcsf14

  • “@glotpress: no need for translators or plugin authors to know what POT files are.” blog.glotpress.org @nacin #wcsf #wcsf14

  • “WordPress… and publishing itself… should be accessible by all.” @nacin #wcsf #wcsf14

  • Hey #wcsf14 folks: It’s ok to mention @drupal and other CMSs. We are all a larger part of the open source community. #wcsf14

  • “Contributing to WordPress: look for what you’re interested in and scratch that itch.” @boone #wcsf #wcsf14

  • “You can contribute to WordPress without thinking it’s a nobile quest. You can do it because it makes business sense.” @boone #wcsf #wcsf14

  • .@boone talking about BuddyPress docs, which I’ve used and it’s excellent: wordpress.org/plugins/buddyp… #wcsf #wcsf14

  • “Guilting people into contributing into WordPress makes them Martyrs, and that’s not something we should want.” @boone #wcsf #wcsf14

  • Anyone at #wcsf14 who wants to talk to a WordPress/BuddyPress freelancer (*cough* for projects *cough*) let’s talk! #wcsf

  • Those at #wcsf interested in web accessibility should check out @joedolson github page: github.com/joedolson #wcsf14

  • WAVE accessibility tool with a Chrome extension: wave.webaim.org mentioned by @joedolson #wcsf14 #wcsf

  • “Don’t write code you know you’ll need to fix later.” @joedolson #wcsf14 #wcsf

  • “Making accessibility hard – we can blame technology but developers can go that extra mile. But that will be work.” @joedolson #wcsf14 #wcsf