David Whittemore, here..

Historically, the contents of the jazzbutcher.com website has been a tightly-curated affair, and the accuracy of its contents has been dictated by information availability and personal free time.

Obviously, there is more information "out there", and having more people on the case could only be a good thing.

With a little bit of effort, the collected Jazz Butcher archives can have a fighting chance to make it past just the lifetime of one person.

With shared ownership in this repository, the raw information that drives jbc com will not be stuck "somewhere". Instead the information could be available for others to mine and repurpose and improve upon.

This is the first step to formalize a public/participatory framework for maintaining the jazzbutcher.com website: announcing the intent, and inviting participants in an open sharing of information.

Here is how you can participate

The v1 directory contains (most) of the .htdb files which drive the original HTDB version of the website, which is now found at: https://v1.jazzbutcher.com

The v2 directory contains the Work In Progress which is the conversion of the v1 site into a nextjs/React application

Changes made here will be deployed within a minute to https://jazzbutcher-com.vercel.app/, which is also where jazzbutcher.com now points.

As of this writing (2023-08-27), the V2 website is fairly faithful to the look and functionalty of V1 version.

I am completely open to collaborating with people with web design and/or UX experience. Let's work on this together. Hit me up!

• have git installed
• have nodejs 20+ installed (i use nvm)

nvm install 20 && nvm use 20

• install the code

git clone git@github.com:xpollen8/jazzbutcher.com.git

• get in the right directory

cd jazzbutcher.com/v2

• Add this to .env.local:

echo "JBC_HTDB_SERVER=https://jazzbutcher.com" > .env.local
echo "JBC_DATA_SERVER=https://data.jazzbutcher.com" >> .env.local
echo "## disables auth on /admin" >> .env.local
echo "LOCAL_DEV=true" >> .env.local

• install dependencies

npm i

• and run it!

npm run dev

• open http://localhost:3000 in a browser

Keep that npm run dev command running. If you edit any of the underlying files in the v2/src/[app/components] folders, any changes should almost immediately appear in the browser.

CSS is found in the v2/src/app/globals.css file, if you want to try a hand at turning things into a candy-coloured clown.