Have you checked for existing feature requests?
Summary
To avoid issues like we saw with the old site where things got deprecated and hard to maintain, it probably makes sense if we can keep the site up to date with the latest versions of things and go through the short term pain of making sure it stays with major versions.
Unfortunately it seems we have some issues, particularly surrounding templates. I had a very quick and uneducated attempt at getting it to run on v3 but failed miserably.
The main pain points I came up against (annoyingly not covered when running the upgrade helper) were these errors:
Problem writing Eleventy templates:
Cannot read properties of undefined (reading 'aliasKey') (via TypeError)
I did try to have a look to see what it might be and tried adding a key field to the template stuff e.g.:
eleventyConfig.addExtension("less", {
key: "less",
outputFileExtension: "css",
compile: async function (input, inputPath) {But then got stuck again:
Problem writing Eleventy templates:
An attempt to alias js to terser was made, but terser is not a recognized template syntax.
And quickly ran out of patience and talent and lack lack of knowledge of how the new docs site actually works. It is probably something not that complicated but I didn't want to start hacking things to bits in a futile effort to fix what aint currently broke.
What benefits does this feature provide?
Easier future updated/access to new features (v4 is currently being worked on and is already out in beta/pre-release form which would put the site two major versions behind). And another "fun" thing is that it won't even be 11ty any more, it is becoming build-awesome (https://www.11ty.dev/blog/build-awesome/)...)
Any alternatives?
Leave it alone? It isn't currently broken.
Other examples:
No response
Have you checked for existing feature requests?
Summary
To avoid issues like we saw with the old site where things got deprecated and hard to maintain, it probably makes sense if we can keep the site up to date with the latest versions of things and go through the short term pain of making sure it stays with major versions.
Unfortunately it seems we have some issues, particularly surrounding templates. I had a very quick and uneducated attempt at getting it to run on v3 but failed miserably.
The main pain points I came up against (annoyingly not covered when running the upgrade helper) were these errors:
I did try to have a look to see what it might be and tried adding a
keyfield to the template stuff e.g.:But then got stuck again:
And quickly ran out of patience and talent and lack lack of knowledge of how the new docs site actually works. It is probably something not that complicated but I didn't want to start hacking things to bits in a futile effort to fix what aint currently broke.
What benefits does this feature provide?
Easier future updated/access to new features (v4 is currently being worked on and is already out in beta/pre-release form which would put the site two major versions behind). And another "fun" thing is that it won't even be
11tyany more, it is becomingbuild-awesome(https://www.11ty.dev/blog/build-awesome/)...)Any alternatives?
Leave it alone? It isn't currently broken.
Other examples:
No response