---
title: Exploring generative art
description: A fully autonomous generative art flow creates and publishes unique pieces daily on Instagram and WordPress, blending creative coding with automation.
doc_version: current
last_updated: '2026-03-31T09:56:04.000Z'
date: '2021-12-14T14:51:13.000Z'
author: Rich Tabor
summary: A fully autonomous generative art flow creates and publishes unique pieces daily on Instagram and WordPress, blending creative coding with automation.
tags:
  - Design
published: true
type: blog
url: /generative-art
canonical: https://richtabor.com/generative-art
id: 2075
---

TLDR; I built a generative art flow that is fully autonomous: generating art daily from creative code, and publishing to Instagram and WordPress without any humans. Cool, eh?

[Creative coding](https://en.wikipedia.org/wiki/Creative_coding) — programming towards a visual pursuit, instead of functional, is a medium that I’ve wanted to personally explore for some time now. I love that it’s a mass of creativity, somewhere between design and programming, which is right up my alley. A key component of creative coding is the idea that the creator must relinquish a certain level of creative control. The resulting pieces are generated by combinations of variables, to help determine interesting art.

So with a couple of hours over last weekend, I set out to start learning the workings of [p5.js](https://p5js.org) and spin up a micro site to share the generative art on. For the site itself, I naturally wanted to use WordPress (with the upcoming [Full Site Editing](/full-site-editing/) functionality) as another excuse to jump into real-world usage of the upcoming release.

Every day a script is triggered autonomously, which runs the p5.js creative code I’ve written, picks a random integer as a series ID/name, and saves the one-of-a-kind generative piece as a high-resolution file. The idea behind this was largely inspired by [Andrei Korchagin](https://andreikorchagin.medium.com/creating-a-living-generative-art-nft-project-with-javascript-google-cloud-instagram-and-opensea-2b245344ae10).

![](https://i0.wp.com/rich.blog/wp-content/uploads/2023/01/78aee-series-7720-1.png?ssl=1&resize=2000%2C2000)

![](https://i0.wp.com/rich.blog/wp-content/uploads/2023/01/d55f1-series-7720.png?ssl=1&resize=2000%2C2000)

![](https://i0.wp.com/rich.blog/wp-content/uploads/2023/01/6f6d7-eef4c20e-1d16-43aa-bfac-c4d065c4bb7f.png?ssl=1&resize=2000%2C2000)

![](https://i0.wp.com/rich.blog/wp-content/uploads/2023/01/fd7c8-series-1159.png?ssl=1&resize=2000%2C2000)

That’s pretty cool — but I didn’t stop there. As part of the production workflow, the file is then sent to an Instagram account I created for this particular project.

Then a post is programmatically published on the WordPress site that I’ve spun up, attaching the generated file as the post’s featured image. Now whenever you check out my new gallery site, [tabor.gallery](https://tabor.gallery), you’ll see each generative piece as they’re created daily.

For the site, I used a variant of the upcoming [Twenty Twenty-Two](https://github.com/WordPress/twentytwentytwo) block theme, to build out the gallery. And although there are a number of Full Site Editing quirks to be ironed out yet, I can confidently say that a year ago this would have taken much longer to publish.

## Sitemap

[Full site index](/sitemap.md)