Best song ever. The motherfucking pterodactyl: theoatmeal.com/pterodactyl_video

@geekgirlweb Do it! We’ll have fun!

@geekgirlweb I really like French, learn that and then we can play Big Blue Moon en français.

@geekgirlweb French, it’s the language of love! Or Japanese so we can start a Tokyo DUG and have DrupalCon Japan in 2014 w/a Mech Drupalicon

@canarymason @bangpound @CLoudNYNE And we’ve come full circle to WYSIWTF.

@bangpound @CLoudNYNE @canarymason Partially agree for output (some WYSIWYG just output crap), but doesn’t solve the WYG expectation w/#rwd

@canarymason @CLoudNYNE At the Senate, we made anyone who entered content go through training. Training solves the need for WYSIWYG.

@canarymason @CLoudNYNE This started as a light hearted quip from a silly tweet and turned into full conversation. Will do for next client.

@canarymason @CLoudNYNE Styles in editor only goes so far when talking #rwd. They’re then gonna need to resize and complain when WYG breaks

@CLoudNYNE @canarymason I have yet to deal with a client where they demanded a WYSIWYG

@CLoudNYNE @canarymason Also, FTR, there are only two places I’ve implemented a mkdwn only solution, both of which are fairly technical, so

@canarymason @CLoudNYNE I’d prefer to teach them mkdwn’s “programing” than them complain their WYSIWYG isn’t WYG-ing for them.

@CLoudNYNE @canarymason …plain text with wrapping symbols, you aren’t likely to be upset when it gets translated for #rwd

@CLoudNYNE @canarymason Matter of expectations. If you see rendered output from WYSIWYG, you expect that to be the output. If you see…

@CLoudNYNE @canarymason My issue w/WYSIWYG, & my original point, is that WYS isn’t always WYG for #rwd, hence my preference for plain mkdwn

@canarymason @CLoudNYNE Maybe then we need to build a markdown editor w/buttons for syntax/extra stuff?

@canarymason @CLoudNYNE Well then we need to build a smarter robot, don’t we?

@canarymason @CLoudNYNE You can do images in Markdown and w/Markdown Extra can do tables. For Drupal, all in one: drupal.org/project/markdown

@CLoudNYNE @canarymason Fair enough, but I think my original point still stands in that case.

@CLoudNYNE @canarymason #scopeCreep sucks, but the argument is then “WYSIWYG when you can’t do it right”

@canarymason @CLoudNYNE Maybe something with a water drop for an icon?

@CLoudNYNE @canarymason Disagree. They should be plaintext fields that get built into a table through a CMS. Also, jCarousel error.

@CLoudNYNE @canarymason …HTML

@CLoudNYNE @canarymason My point is clients shouldn’t be writing HTML, they should be writing content and our CMSs should be translating to…

@canarymason @CLoudNYNE I think we agree with the exception that I prefer Markdown to WYSIWYG, but Markdown is easier to write on the go.