Omeka VS shite

Omeka

Omeka (https://omeka.org/) is OSS and has a REST API. Usually used by museums/libraries, but primary function is to upload and describe media files.

Adding new features to listmonk (mailing list / newsletter manager), preparing for its next release.

https://github.com/knadh/listmonk

Setting up and playing around with Omeka, a brilliant document publishing system, to help publish an archive of digitised physical books and documents.

https://omeka.org

If you Google "COVID-19 digital archive" you can also find a range of projects with different focuses. A benefit of technology is that now many organizations can create their own Omeka site and build a collection to document events in real time. However, I hope the post above demonstrates that while anyone can, any historian utilizing these various resources need to consider the practices undertaken to gather digital archives. We would never enter a physical archive and look at paper documents without questioning why those survive, what's missing, and thinking about voices specifically left out. A digital collection is the same, however they present an abundance of sources that can distract or distort- approaching the surviving records of the Salem Witch Trials is different from approaching a collection of 40,000 personal accounts. What voices might not volunteer a personal account to a website if it requires identifying information? How many images of people in masks at the grocery store do we need to deliberately save? These are not substantially different questions from what past historians and archivists thought about, but technology does reframe discussion. We'll see how many of these projects were developed with sustainability in mind.

Yes to this and other free, open source solutions such as Omeka.

I have not tried this yet but: https://wordpress.org/plugins/diviner-archive/ Or you might look into a non-Wordpress solution like Omeka https://omeka.org/

There are some great visual archives online that might serve as inspiration. Free tools to create them include Collection Builder, Omeka, and some other free, open source repository software. Most of their sites have links to projects that people have built using their tool, and I find them super inspiring to scroll through and get ideas for projects like yours.

A popular alternative is Omeka, which can't directly be used with WordPress but does have some workarounds to effectively show the digital collection in a frame. Search the Omeka forum for more info.

Omeka (https://omeka.org/)

Pandoc can be your friend. My site maker [1] is built around it.

I think a hundred or so well-chosen lines of your favourite scripting language can do wonders. Mine is ~300 lines of Bash because I over-engineered a thing or two for kicks. The core of it is maybe 50 lines.

[1] https://github.com/adityaathalye/shite

The README documents the architecture and rationale. Maybe it will help you figure out yours. Happy hacking!

[1] https://evalapply.org

[2] https://github.com/adityaathalye/shite?tab=readme-ov-file#te...

Bookmarked! These look like amazing study projects; the kind one can copy and learn from. Quite like how they do it in art school. Each one of them looks like it solves a nontrivial problem, and edifies the reader on the basic contours/tenets of the problem/solution space.

I love this kind of stuff, because it shows one _can_ solve a pretty juicy problem with not that much code, honestly. Also because it suggests that the industrial-strength equivalent has a lot more in for use cases, corner cases, and/or optimisations that are not relevant for one's requirements (at least not yet, maybe not ever).

I aspire to write code like that. Useful, concise, but not obtuse. Some of my code is not as significant as those examples, and maybe falls short of my ideals, but it gets a lot done in well under 500 loc. e.g. my website maker in Bash [1] (hot-builds and hot-refreshes without JS), or the JS that drives text art animations for Hanukkah of Data [2].

[1] https://github.com/adityaathalye/shite is about 350 LoC counted this way (excluding the script containing HTML templates).

  $ grep -E -v "^$|\\s?#" bin/{events,metadata,templating,utils,hotreload}.sh | wc -l

I love the code [1]. Mine [2] is a bit over engineered because I wanted hot-reloading (without JS), and it was a delightful yak shave.

But the basic idea is the same --- heredocs for templating, using a plaintext -> html compiler (pandoc in my case), an intermediate CSV for index generation.

Very nice!

[1] https://github.com/karlb/karl.berlin/blob/master/blog.sh

[2] https://github.com/adityaathalye/shite

xdotool emulates user actions under the X Window System (e.g. typing, mouse around, click etc.).

I'm using it to send keypresses to the browser, as you rightly observe.

So if I want to just reload a page, the browser gets F5.

To GOTO some page, it gets a stream of keystrokes for the URL characters and then Enter.

It's really that simple-minded, and it works!

This case statement covers my usage: https://github.com/adityaathalye/shite/blob/master/bin/hotre...

Pandoc powers my little static site maker:

cf. https://github.com/adityaathalye/shite/blob/master/bin/templ...

  __shite_templating_compile_source_to_html() {