Skip to content

{ Author Archives }

Updated bililiteRange

It seems like a long time ago that I started updating bililiteRange but it was only 3 months ago. And I think I'm done (though projects are never done!). bililiteRange 3.2 is released, and requires history.js, toolbar.js, jquery.status.js and jquery.keymap.js for all the functionality, though really the core only requires history.js. The documentation is at […]

Classic Editor

Well, that was easy. The Classic Editor plugin restores the old editor, with all my custom buttons. And installing it with the command line interface was just wp plugin install classic-editor

Updating WordPress with the command line has been great, but their security settings make it hard to update WordPress automatically. I just discovered that WP now has a command line interface that works fine over SSH. wp core update wp core update-dp And done!. You can do wp db export to back up the database first. And updating plugins (for […]

Prism on a CDN

This is something I didn't know about: Prism, the syntax highlighter I use, is available from a few free CDN's, so I don't have to host it. Cool!

A programmable color scheme

I'm not a designer, and I've never been happy with the color scheme for, so I decided to try something new. I use scssphp with scssphp server (and yes, you need both) to generate the CSS, and it allows variables, so I can do: $hue = 250; $saturation = '40%'; $textcolor: hsl($hue, $saturation, 10%); […]

Implementing the History interface

The way browser history is implemented, with the History interface, is useful for other things than site navigation. The same idea, basically an extended stack that allows going back and forward, is the same algorithm used for undo/redo, and command line history. It would be nice to be able to do const h = new […]

Moving bililiteRange into the modern age.

I haven't updated bililiteRange for years, but it's time to drop support for Internet Explorer and use modern constructs like Promise and input events. It should make things more simple. From here on in, I will only support Chrome, Firefox and Edge (the chromium-based one; I don't have Edge Legacy. I'm also working on moving […]

Extending Parsedown: attributes

Markdown Extra (including Parsedown Extra) allows for attributes to be applied to certain elements: headers, fenced code blocks, links, and images. I'd like to be able to apply them to any element. I'm going to use the syntax of Python Markdown attributes, but the attribute lists go before the elements. For block level elements, they […]

Extending Parsedown: Block elements

Continuing work on extending Parsedown. See the actual code. Adding block-level elements is not much different from adding inline elements. originally used <footer> elements to indicate the source of a block quote: <blockquote> Do or do not. There is no try. </blockquote> <footer>Yoda</footer> </blockquote> While marking blockquotes this way is now acceptable, for a […]

Extending Parsedown: Inline elements

Extending Parsedown involves adding elements to the $InlineTypes and $BlockTypes arrays, then adding methods to handle them. See the actual code. Italics I use <i> a lot, to indicate transliterated words. So I use could use "/" to indicate that: /Shabbat/ is a Hebrew word becomes <i>Shabbat</i> is a Hebrew word. To do that: do […]