It was a great event and I was really happy with my performance. Notably, I hit faster and faster splits in the last five miles: 8:19 (mile 9), 8:02 (mile 10), 7:44 (mile 11), 7:51 (mile 12), and 7:23 (mile 13).
ADU legislation, pro-housing density efforts, software eats retail, and PDX exploring.
ADU Legislative Initiatives Abound (Kol Peterson) — While Senate Bill 1051 is requires all cities to “allow ADUs”, the Oregon Department of Land Conservation and Development guidance recommends dropping owner occupancy requirements, dropping off street parking requirements, allowing detached ADUs up to 800 sq ft by right, and even allowing two ADUs.
Since I last wrote two weeks ago, we’re making progress! Key achievements for Gutenberg and the REST API include:
Support for who=authors was added to GET wp/v2/users, making it possible to accurately query for authors. WordPress, for better or for worse, defines an author as user_level!=0. See WordPress/gutenberg#6361 for the context on why we can’t add this logic client-side (#42202 for WordPress 4.9.6).
Improved performance for the _fields= query parameter (e.g. GET wp/v2/pages?_fields=id,title) by ensuring WordPress core will only process the fields requested for the response. Notably, this helps us avoid running the_content when we don’t need to be (#43874 for WordPress 4.9.7).
Minor enhancements to reflect existing WordPress behaviors:
The “Merge Proposal: REST API” GitHub milestone represents the distance we still need to close. Slowly, steadily, we’re bridging the gap, but we could use your help. Here are some of the issues we’re still working through:
To ensure all necessary data is available to Gutenberg, we’ve settled upon permitting unbounded per_page=-1 REST API requests for authorized users. This landed for GET wp/v2/users (WordPress/gutenberg#6627), is in-progress for GET wp/v2/(pages|blocks) (WordPress/gutenberg#6657), and needs to be addressed for categories, tags, and custom taxonomies. We also need to patch core with this enhancement (#43998 for WordPress 4.9.7?)
Capabilities can’t be processed directly client-side (WordPress/gutenberg#6361), so we’ve introduced a new targetSchema concept to communicate which actions a user can perform. See it in action with wp:action-sticky (WordPress/gutenberg#6529) and wp:action-assign-author (WordPress/gutenberg#6630). There are a few other actions we will need to work out, and then we’ll need to patch core (no ticket yet).
Adam is putting together an improved autosaves implementation (WordPress/gutenberg#6257) that I literally cannot wait to see complete. I’m sure he could use some help testing in the near future.
Strava is a social network, but you can pay for premium features. When someone asks me, “Is paying Strava worth it? What premium features do you like?” I answer, “I could care less about the premium features. I need Strava to exist.”
While the value that Strava the social network provides me is undeniable, Strava creates another construct. The humans who choose to be there are bound together by a shared purpose that I see each time I ride my bike. I often stop at the side of the road and get off my bike for a quick drink or bite. As other bikers pass, it is normal for total strangers to stop their ride and ask, “Hey are you ok?”
media_buttons is only one of the many ways the Classic Editor can be customized. Wouldn’t it be great if there was a database covering all of them?
This is where you come in! Take a look through the Gutenberg Migration Guide. For each action, filter, and so on, we’d like to document real-world examples of how they’ve been used. Then, for each of those real-world examples, identify how the feature might be replicated in Gutenberg.
Since announcing the database on March 1st, 70 people have been granted testing status. However, of 5000 total plugins, we’re still at 4139 untested plugins. No companies have stepped up to contribute a significant amount of person-hours.
Of the 861 tested plugins:
219 (25.44%) are compatible.
518 (60.16%) are likely compatible.
25 (2.9%) are likely not compatible.
39 (4.53%) are not compatible.
60 (6.97%) are in “testing”, which means someone started test and abandoned the process.
Notably, this data is largely biased by the “likely compatible” results. For the most part, these are plugins I pre-screened (e.g. caching plugins) prior to March.
In the original data set, 18 (28.125%) of the 64 incompatible and likely incompatible plugins were updated in the four weeks prior to March 1st. This means the majority are on slower development cycles.
Of the 64 incompatible and likely incompatible plugins, the reasons include:
Missing Add Media and TinyMCE buttons (NextGen, WPForms, Formidable, FooGallery, Page Scroll to ID and others).
Missing QuickTag buttons (Quick AdSense).
Meta box doesn’t display at all (Page Links To, Revision Control).
Semi-live preview of SEO title doesn’t work in Gutenberg (All In One SEO).
Custom Short or Long Product Description fields don’t appear at all (WooCommerce).
Featured thumbnail previews aren’t being generated (Auto Post Thumbnail).Whitescreen of death (qTranslate X, CKEditor).
Registers a CPT with editor support that doesn’t include show_in_rest=>true (Portfolio Post Type)
Adds section to Media Library that isn’t displayed in Gutenberg (Add From Server).
Access restriction from plugin not applied in Gutenberg (Advanced Access Manager).
Last Thursday, as a part of Design Week Portland, I had the chance to tour this basement conversion ADU (accessory dwelling unit) off NE Prescott:
It was pretty cool! From the outside, you’ll notice both sliding glass and French doors where garage doors used to be. This is because it’s a basement and garage conversion ADU.
In case you aren’t already aware, ADU is shorthand for adding a second living space (bed, bath, and kitchen) to a residential property. ADUs can be inside the existing structure or somewhere else on the property (space-permitting).
More generally, ADUs are neat because they open up a number of opportunities:
In communities without new land to build on, ADUs can be cost-effective infill housing.
ADUs make homeownership more attainable by adding cash-flow to cover the mortgage.
For seniors wanting to downsize, ADUs can offer a “downsize in place” option that lets them stay within the community.
Here’s a pano of the immediate interior:
The developer, Kol Peterson, has been building and consulting on ADUs for almost a decade now through his company, Accessory Dwelling Strategies. He’s also written a book, Backdoor Revolution, that’s incredibly informative and information-dense. I’m already at page ~150.
As far as building an ADU in our house goes, I’ve already discovered what Kol identifies in the book as a classic regulation blocker:
(5) In addition to the parking spaces required in TDC 73.370 for the detached single-family dwelling, one paved on-site parking space shall be provided for the accessory dwelling unit and the space shall not be within five feet of a side or rear property line.
In short, we need a three car driveway in order to permit an ADU. But, we only have two slots and there’s no place to put a third. And, ironically, our neighbor can park six cars in their garage, driveway, and street just fine.