johnheenan/minform

Fork 0

refactor: final migration to @anyblades scope, switching to newer pico, and liquid.js security updates #2

Merged

tonystar merged 1 commit from main into main

2026-04-09 16:05:39 +10:00

tonystar commented

2026-04-09 11:14:02 +10:00

(Migrated from github.com)

refactor: final migration of dependencies to https://github.com/anyblades scope, switching to newer pico, and liquid.js security updates

hi @johnheenan please consider these changes
I will be soon exiting from @alpha/@beta into stable releases, wanted to make sure everything settled and works before that

let me know if you find any issues! I'm active on https://www.11ty.dev/blog/discord/ btw

PS: and thanks again for using Blades!

refactor: final migration of dependencies to https://github.com/anyblades scope, switching to newer pico, and liquid.js security updates hi @johnheenan please consider these changes I will be soon exiting from `@alpha/@beta` into stable releases, wanted to make sure everything settled and works before that let me know if you find any issues! I'm active on https://www.11ty.dev/blog/discord/ btw PS: and thanks again for using Blades!

johnheenan commented

2026-04-09 16:16:06 +10:00

(Migrated from github.com)

Thanks @tonystar for this pull request.

Very pleased to see you have forked picocss.

A practice note for this merge that applies because of package name changes and symlinks

It is easier to merge this request from the local command line as it is necessary to run npm update after the merge to correct symlinks due to change of name of package sources. This then needs to be committed before pushing back to github.

This may have side effect of altering package-lock.json again.

Thanks @tonystar for this pull request. Very pleased to see you have forked picocss. ## A practice note for this merge that applies because of package name changes and symlinks It is easier to merge this request from the local command line as it is necessary to run `npm update` after the merge to correct symlinks due to change of name of package sources. This then needs to be committed before pushing back to github. This may have side effect of altering `package-lock.json` again.

👍 1

johnheenan commented

2026-04-09 16:29:30 +10:00

(Migrated from github.com)

@tonystar

I have joined the 11ty discord server with same username.

I will release new template version and include changes for hostfurl minformhf in a VM server image being prepared, with built version to be automatically copied and used with creation of new customer virtual shared servers, same as demo at https://minformhf.hostfurl.com.

I don't know when the Hostfurl server VMs will be ready to deploy. It is hoped the time deploy new servers will reduce from over two days to under two hours. Even less with pre prepared cloud-init.

I don't want to add in the minform template to 11ty Starter Projects until servers have been deployed.

@tonystar I have joined the 11ty discord server with same username. I will release new template version and include changes for hostfurl minformhf in a VM server image being prepared, with built version to be automatically copied and used with creation of new customer virtual shared servers, same as demo at https://minformhf.hostfurl.com. I don't know when the Hostfurl server VMs will be ready to deploy. It is hoped the time deploy new servers will reduce from over two days to under two hours. Even less with pre prepared cloud-init. I don't want to add in the minform template to 11ty [Starter Projects](https://www.11ty.dev/docs/starter/) until servers have been deployed.

👍 1

johnheenan commented

2026-04-09 23:49:38 +10:00

(Migrated from github.com)

@tonystar

There are the current initial further work goals for minform

At the moment I am only at goal 1 below.

With regard to goal 2, I intend to write a script to automate updates. There are only a few files affected.

Ongoing initial goals

Keep up to date with npm packages, such as yours. Your packages are great, a huge boon.
Incorporate changes from symlinked directory in _includes directory with parallel _includes_minform directory

One off initial goals

Add basic usage notes for with and without using git
For git users, show how to use github actions with examples, code and demo
For git users, show how to use Sveltia CMS with examples, code and demo

@tonystar ## There are the current initial further work goals for minform At the moment I am only at goal 1 below. With regard to goal 2, I intend to write a script to automate updates. There are only a few files affected. ### Ongoing initial goals 1. Keep up to date with npm packages, such as yours. Your packages are great, a huge boon. 2. Incorporate changes from symlinked directory in _includes directory with parallel _includes_minform directory ### One off initial goals 4. Add basic usage notes for with and without using git 5. For git users, show how to use github actions with examples, code and demo 6. For git users, show how to use [Sveltia CMS](https://sveltiacms.app/en/) with examples, code and demo

👍 1

tonystar commented

2026-04-10 07:11:24 +10:00

(Migrated from github.com)

all sounds like a good plan! wish you success

With regard to goal 2, I intend to write a script to automate updates. There are only a few files affected.

yes! would love to see that, I try to keep @anyblades packages to be very easy to update, so you can focus on your business logic
eager to see your project evolving

all sounds like a good plan! wish you success > With regard to goal 2, I intend to write a script to automate updates. There are only a few files affected. yes! would love to see that, I try to keep @anyblades packages to be very easy to update, so you can focus on your business logic eager to see your project evolving

👍 1

johnheenan commented

2026-04-10 23:02:11 +10:00

(Migrated from github.com)

@tonystar

With regard to goal 2, I intend to write a script to automate updates. There are only a few files affected.

yes! would love to see that, I try to keep @anyblades packages to be very easy to update, so you can focus on your business logic

I would agree it is core functionality and should be up sooner rather than later. It might encourage others to try this approach also.

So here it is at
github.com/johnheenan/minform@b42f420aa3/minform/syncblades.js

New releases include the script.

Minimal usage notes (at the moment) at https://github.com/johnheenan/minform#updates

@tonystar > > With regard to goal 2, I intend to write a script to automate updates. There are only a few files affected. > > yes! would love to see that, I try to keep @anyblades packages to be very easy to update, so you can focus on your business logic I would agree it is core functionality and should be up sooner rather than later. It might encourage others to try this approach also. So here it is at https://github.com/johnheenan/minform/blob/b42f420aa34e2297d939ffbc28c4dd92f6df4456/minform/syncblades.js New releases include the script. Minimal usage notes (at the moment) at https://github.com/johnheenan/minform#updates