RUBRIC

The genesis of Rubric lay in my inability to remember even the slightest outline of what a skeleton of an order of services entails. If it's not written out in front of me, I have no idea. I've been to church many times, I've written and led services, I've had a class where we studied the UCC order of services, and yet when it comes to beginning work on one everything is a surprise. So I thought: what if I wrote it down? And so I did, in an Obsidian note that swiftly fell into the aching chasm that is my disorganized Obsidian note-pile.

So what if, instead, I wrote it down in something purpose-built that allowed me to build service plans for churches other than the one I'm currently placed at, and it looks like a Gnome program even though I'm plasma-wed? And so began Rubric. Later features arose from my desire to not have to type the date and RCL into google, and to not have to turn my desk chair around and look at a relevant copy of Gathering for hymn suggestions. Later, I thought "what if I didn't have to type hymn names into youtube to find out what they sound like?" The feature set flowed freely from my endless cup of laziness. Soon I set it up to help me easily produce LaTeX outputs for manuscripts, bulletins, and music notes. GitHub integration followed. Previews... Too many features, arguably...

Now I'm at the state where I realize this could be useful for other worship leaders, and I'm hard at work making it more accessible, and loosening the grip of LaTeX on it (first I made it export to Typst, used by even fewer people, but then to DOCX/ODT and even HTML...) If I hadn't designed it entirely, unbreakably for use on OPENSUSE Tumbleweed, its possible user-base would already be in the higher single-digits! I'm working on that. I've mapped out dependencies on other Linux distros, have an appimage that might work, and set it up for distro through PYPI/PIP! Maybe it will be an rpm soon, a deb even, maybe snap?? Windows? Mac? Maybe!

Pубрика?