As part of my iterative intentions for 2018, I started a project to rebuild and simplify my website. I’ve used Jekyll for quite some time (either by itself or with Octopress), and as part of the latest iteration of the site, I’ve been working to align the site more with Indieweb principles, and to smooth the deployment path for my site by hosting it on Netlify.
One challenge with Jekyll and other static site generators is that “dynamic-ish” functionality, including sending notifications through protocols like WebSub. The trouble is knowing where these actions fit into the build process for your site: you don’t want to send the notifications before your site gets built, or pushed to the CDN hosting your site. Recently, Netlify announced a private beta for its new Netlify Functions service, which provides lambda-style functions deployed as part of your site deployment. One of the neat features that exists as of the beta is the ability to trigger the functions via Netlify events, like when your site successfully deploys.
I completed my reading and viewing assignments for my cohort’s IT Leadership Program Workshop 1 (- at UC Berkeley.) This is a brief set of notes for my own use about how all of them tie together.
While I enjoy seeing what my friends are setting their intentions towards in the new year, I don’t really believe in new year’s resolutions for myself. They tend to wear on me heavily whenever I’ve proclaimed a long list of things I’m hoping to get better at. Instead, this year, I’m starting with a very short list. My hope is that I can commit to a small number of good habits at a time, which I can then build on iteratively. I want to have the windows of reinforcement stay small at first (maybe a week or two), and once I feel satisfied about whichever habits I’ve committed to, I can add more.
I’m starting with three items:
- Rebuilding this website: simplified tooling; new layout/style; using and publishing more structured data, and a partial implementation of a stack following Indieweb and Solid principles. The last part is intentionally slippery, but I mostly really care about sending and receiving notifications at this point. I’m giving myself about a week to get this done.
- Eating better breakfasts. I started 2018 with overnight oats, which happened to be mildly successful. I have a lot to master in terms of proportions and taste, to say the least.
- Budgeting and financial tracking to better understand my ongoing expenses. This is something I’m undertaking with my partner, and we have actionable (but private) goals for this.
Wish me luck.
My current position at DPLA, especially since we are remote-first organization, requires me to be on lots of conference calls, both video and audio. While I’ve learned the value of staying muted while I’m not talking, there are a couple of things that make this challenging. First, I usually need the window for the call to have focus to unmute myself by the platform’s designated keystroke. Forget that working well if you need to bring something up in another window, or switch to another application. Secondly, while we have our own preferred platform internally (Google Hangouts), I have to use countless others, too; each of those platforms has its own separate keystroke to mute.
This all leads to a less than ideal situation, and naturally, I figured there must be a better way.
One of the most important aspects of the work of the DPLA Technology Team is ensuring that we maintain a common frame of reference for all of our efforts. This is situated in multiple aspects - in terms of our shared technical knowledge, the overall DPLA strategic plan, and more. Overall, however, the guiding principles for our work are best understood through the core values that inform how we work together within our team, as well as with our colleagues at DPLA and across the network of our stakeholders and collaborators. These values are not only designed to be aspirational; instead, they also inform practical aspects of our day to day work, allowing us to work together effectively through their articulation of cultural norms and expectations. In addition, our values encourage us to be intentional about our work, even when faced with challenges from deadlines, staff capacity, and other external pressures.
DPLA is pleased to announce that the entirety of our website, including our portal, exhibitions, Primary Source Sets, and our API, are now accessible using HTTPS by default. DPLA takes user privacy seriously, and the infrastructural changes that we have made to support HTTPS allows us to extend this dedication further and become signatories of the Library Digital Privacy Pledge of 2015-2016, developed by our colleagues at the Library Freedom Project.
DPLA, along with representatives of a number of institutions including Stanford University, the Yale Center for British Art, the Bibliothèque nationale de France, and more, is presenting at Access to the World’s Images, a series of events related to the International Image Interoperability Framework (IIIF) in New York City, hosted by the Museum of Modern Art and the New York Academy of Medicine. The events will showcase how institutions are leveraging IIIF to reduce total cost and time to deploy image delivery solutions, while simultaneously improving end user experience with a new host of rich and dynamic features, and promote collaboration within the IIIF community through facilitated conversations and working group meetings.
This is the written version of my presentation from Code4lib 2016 in Philadelphia, on March 8, 2016. My presentation was part of a panel with my friends Christina Harlow, Ted Lawless, and Matt Zumwalt, after which we had some discussion moderated by Matt Miller. My slides are available, as are the video of all talks from the panel.
A running list of things I want to do or have done. A lot of this relates to adopting the IndieWeb ethos
Enable sending and receiving webmentions
Minimal h-entry markup
- New theme!
- Enable incoming webmention displays from Webmention.io.
- Redo build process, perhaps running on Travis or my own server.
- Enable automatic POSSE to Twitter, Medium, Slideshare, LinkedIn, and Facebook(?). Consider using Bridgy if this will lower friction.
- Send automatic webmentions through Webmention.io on build.
- Mobile post creation and editing using an existing Git client and Markdown editor.
- Adopt Micropub or something comparable to potentially stage posts through pull requests. Longer term goal is to have a nice mobile client.
- Refactor the publication and resume to be data driven.
- Reuse and refactor existing codebases, like Aaron Gustafon’s Jekyll plugin for webmentions (Github repo) and Will Norris’ syndication plugin.
- Implement Jekyll collections as a proxy for managing h-entry post-types.
- Cache and eventually move commenting away from Disqus.
This is the written version of my keynote presentation from the 2015 LITA Forum in Minneapolis, Minnesota, on November 14, 2015. I am grateful for the thoughtful and critical feedback from my friends and colleagues Maureen Callahan, Jarrett M. Drake, Hillel Arnold, Ben Armintor, Christina Harlow, and Chela Weber in their review of earlier drafts of this text. My slides are also available.