I should be able to charge extra for editing content on any site with Visual Composer involved. That plugin is the bane of my existence, and the sooner it completely disappears, the better. It is absolutely possible to edit VC content by hand. This is also absolutely not a skillset I should have to maintain. We have standards for a reason. It is very time-consuming and tedious, along with probably being traumatizing, for anyone to have to learn the non-standard idiosyncracies of this kind of generated markup. Friends don’t let friends use this plugin. Enemies probably shouldn’t let enemies use it either.

I spent some time today putting a system in place to track the unbillable time I spend on contributions to free software, and when I say contribution I’m being pretty liberal about what counts as contribution: Advocacy, not just code, for example. I believe in the mission of free software, but the fact is free software isn’t without cost, and sometimes that cost can get pretty high. I’m also working out how to document my contributions in my portfolio, including the free accessibility advocacy that I do. This is going to take a little more work and some more research, but I feel it needs to be done. I need to be able to keep track of this stuff so I can limit it when necessary. Right now I’m thinking of setting the limit at ten percent of free time outside of shabbat and festivals, because those are times when no work of any kind is done, as a general rule. I’m not going to get into the exceptions around festivals because it’s a lengthy topic, but to say no work of any kind can be done on festivals would be technically inaccurate. I think ten percent is a reasonable amount of time. It’s not a ton, but it places an upper limit on the time I have available to do this kind of work. I will also document the time spent, although I haven’t decided whether I will publish a weekly or monthly or yearly report. This is going to be an interesting project.

I’m participating in the Ultimate Blog Challenge for personal and professional reasons. The personal reasons are partly documented here, and I’ll document my professional reasons on this site.

Content creation is hard work, and I need to get back into the swing of it. I have several lengthy tutorials sitting in my drafts, and I need to finish them, and I think the only real way to get back into the swing of content creation is to practice. So I’ve decided to take up this blogging challenge so that I can do that, as well as find new content to read and absorb. There are a lot of things floating around my brain regarding business, the tech landscape, and the web development landscape specifically, and I’d like to start getting those things out of my brain and onto my website where I can flesh them out better. My plan is to not turn over all my thoughts to social media platforms and instead document them on my own site, linking to them in larger posts where appropriate, and of course changing them when appropriate. Plus this will be a really great way to share what I learn by sharing my notes on the books I’m reading, (there are several professional development as well as technical books on my anticipated reading list for 2019), as well as the articles written by others, especially experts in particular fields like accessibility. I’m looking forward to this, and I think it will be a lot of fun. If you want to sign up, I believe there’s still time left to join. No pressure or anything, but it’s a great way to start owning your own content if you haven’t started doing that already.

Until next time.

Researching if I can add blocks in Gutenberg using the non-visual editor by typing block comments. As long as the interface is inaccessible I have no problem hacking around it if possible, I will not be cut off from the future of WordPress, temporarily or otherwise.

Friendly public service announcement: If you store, process or transmit credit card data, you are responsible for ensuring that you are PCI compliant. Use a third-party payment processor and transmit your data securely if you don’t want end-to-end responsibility. Thank you.

I have come to the conclusion that Matt is not going to take accessibility seriously until it affects him personally, and this is incredibly sad. Accessibility should not be the domain of those who are part of the disabled list, or those whose loved ones are part of it.

Maybe privacy and accessibility work would be valued by employers in the WordPress space if @photomatt would do his Goddamn job and advocate for them. Walking is very painful now but I have zero problem inching across that convention center tomorrow to say that to his face. #WCUS

I will respond to Matt’s call to learn blocks deeply when Mat learns accessibility deeply. Accessibility is not a nice-to-have, or an afterthought, or a feature, and I will not promote a thing I know full well not everyone can use, no matter how great the UX is for some. #WCUS