Tomodomo

WordPress-powered publishing platforms for the written web (@WordPress, @rcpwp, @Vanilla, & more.) Formerly @vanpattenmedia

[Tomodomo @TomodomoCo]

We launched our new Gutenberg-powered site this weekend! Check it out: https://t.co/Fzd3RylxmL

[Tomodomo @TomodomoCo]

Ideal person has extensive experience with the Google suite (Analytics, GTM, etc), implementing event tracking + cross-domain conversion tracking, etc.

[Tomodomo @TomodomoCo]

We're looking for a web analytics consultant, specifically with expertise working with online publishers. Know anyone? Maybe it's you? Get in touch!

[Tomodomo @TomodomoCo]

Hey #WordPress plugin devs, if we built an Easy Digital Downloads plugin that lets you run a Composer packages repo for your customers (license key for authentication), would you use it…?

[Tomodomo @TomodomoCo]

good morning to @serverpilot, @heatshieldio, @backupsheep, and no one else

(Seriously though, these apps are killer for your self-hosted WordPress infrastructure. Get on it!)

[WordPressTV @WordPressTV]

Chris Van Patten: “Decisions, not Options” in the Age of Gutenberg @wcpublishers @WordPressTV @ChrisVanPatten https://t.co/HqXhj8eg5i

[Tomodomo @TomodomoCo]

Also maybe consider starting to seriously play with Gutenberg and get over your fear? We were nervous too but are now totally on board. It's fun to build for and our clients love it.

[Tomodomo @TomodomoCo]

For myriad reasons, the classic editor will continue to exist in WordPress for the foreseeable future. A fork is dangerous and entirely unnecessary. That's all we have to say about that ¯\_(ツ)_/¯

[Tomodomo @TomodomoCo]

There are a lot of reasons for this that will eventually make their way into a blog post, but the tl;dr is that our projects increasingly resemble modern PHP/JS projects, so embracing modern standards makes sense for us

[Tomodomo @TomodomoCo]

We've open sourced our coding style guide! https://t.co/oVWNqWX6VY

[Tomodomo @TomodomoCo]

Even though the majority of our work is in WordPress, we're bucking the trends and embracing PSR-2 and Standard instead of the WP coding standards.

[Tomodomo @TomodomoCo]

It has come to our attention that we actually forgot to open source this repo. Our bad. Try again! https://t.co/Cy8A04NbfU

[Tomodomo @TomodomoCo]

We released an updated version of our #Gutenberg block starter repo. https://t.co/Cy8A04NbfU Feel free to use it for your own projects!

[Tomodomo @TomodomoCo]

We're having a blast!

[Tomodomo @TomodomoCo]

Oh hey it’s our friends @UnlockProtocol on this slide from @eulken at @wcpublishers

[Tomodomo @TomodomoCo]

Founder @ChrisVanPatten is speaking at @wcpublishers in a few moments!

[WordCamp for Publishers @wcpublishers]

Our first session and workshop both start at 9:30AM CT. Follow the signs or watch the livestream! #wcpub

“Decisions, not Options” in the Age of Gutenberg https://t.co/MLEqxiyk1z

Cooking With Gas: Quick and Easy Recipes for Developing Accessible Websites
https://t.co/NtapbVEwnh

[Tomodomo @TomodomoCo]

We're very excited to be in Chicago (first time!) for @wcpublishers. Founder @ChrisVanPatten is speaking about designing Gutenberg block UI

[Tomodomo @TomodomoCo]

There are many reasons we love about @DeliciousBrains, but providing a Composer package repo is especially high on the list

[Tomodomo @TomodomoCo]

And of course you need to do testing and planning before updating. Any sufficiently large site should have a staged update process w/ a QA step. Not testing and fixing bugs before rolling out updates is what's truly irresponsible!

[Tomodomo @TomodomoCo]

Strong disagree. As long as you're honest with the client about the risks, and they're willing to commit to ongoing maintenance, it's not irresponsible at all. https://t.co/FNOnZ0Cea6

[Brad Williams @williamsba]

IMO it is highly irresponsible to build and launch a #WordPress powered website of any importance on #Gutenberg today. You're building against a moving target on a feature that is critical to your website functioning. Risky!

[Tomodomo @TomodomoCo]

Gutenberg is changing quickly and frequently but if you follow #core-editor meetings, keep an eye on commits, etc., you can have a good grasp on the changes and avoid major breakage.