Jetpack Tiled Gallery Example
In terms of basic accessibility guidelines each page should have only one H1 element. In WordPress that’s usually built into the template and is usually the title of the post or page. I was thinking about that last night and wondered if we should just remove it as an option from the TinyMCE editor in WordPress. Removing options goes against my typical stance but I couldn’t think of any scenarios that demanded an H1 element but plenty of scenarios where offering it seemed like it’d create confusion. A brief perusal of the WordPress Codex’s TinyMCE section led to the code above. I put it in our generic network-activated plugin for Rampages. Next steps could include integrating a filter in kses to remove/replace H1 elements with H2 elements but that’ll wait for now as it seems a chunk more aggressive.
VCU is reading The Circle by Dave Eggers. All of the first year students will read the book in addition to a number of different faculty members and it’ll play various roles in various classes. So all that means lots of potential for interesting connections but very, very little consistency or hope for consistency.I talked to Joseph Cates about potential options for online annotation but I don’t think there’s much likelihood the publisher will give us the type of file we’d need to make that work well cross platform and between sections. The usual things that help you structure a site an experience like this aren’t going to happen but I would really like to allow people to engage with the larger community around this book. That’s the whole point of everyone reading the same book! So I’m relying on the basic blog-based aggregation hub option. The plan is for it to be a lot like the #thoughtvectors site which Alan has explained at length. People can enroll via a Gravity Form that’ll get them tied to their teacher/class and/or we can cherry pick anything with the #VCUcircleWe do need that to be consistent as an opt in element. tag from the Rampages community feed. That is pretty standard these days. 🙂 But a major uniting factor in these sites […]
As part of some thoughts on building out a series of reflective views for student portfolio blogs, I thought seeing your WordPress posts in the TimelineJS view might be a useful way to look back over your progress. I intend to wrap this into a custom spreadsheet template and/or a pluginOr maybe just a page where you throw in a blog URL and get a bunch of alternate view/data options. but figured I’d sketch out how it works so far in case anyone was interested. The WP Rest API makes it pretty easy to write the data via Google Script. I just want to cut out chunks of the data and put it in the right fields. The following script does that and writes it to a page named “wp.”