feat: add changelog page

[cpreston321]

🔗 Linked issue

#32

❓ Type of change

• [ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• [ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
• [ ] 👌 Enhancement (improving an existing functionality like performance)
• [X] ✨ New feature (a non-breaking change that adds functionality)
• [ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• [ ] ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Currently can be accessed:

https://feat-changelogs.undocs.pages.dev/changelog

TODO

• [ ] OG Image
• [ ] Put link within header?

Resolves: #32

📝 Checklist

• [X] I have linked an issue or discussion.
• [ ] I have updated the documentation accordingly.

[cloudflare-workers-and-pages[bot]]

Deploying undocs with    Cloudflare Pages

Latest commit:	e68493f
Status:	✅  Deploy successful!
Preview URL:	https://af125f82.undocs.pages.dev
Branch Preview URL:	https://feat-changelogs.undocs.pages.dev

View logs

[cpreston321]

@pi0 I'm not for sure what we want the OG Image to look like but here is a quick take at it:

[pi0]

Probably no or with less advertising title. It is simply a changelog page.

[atinux]

I do find it quite cool personally, it's not too much IMO 😊

[pi0]

(i still prefer a shorter/no description as such -- also it is not "what is happening"!, but respect you might have different marketing goals when we generalize undocs to add something like this in the future)

[cpreston321]

Updates:

• Using OGImageDocs template for now
• Changed changelogs -> changelog
• Added Changelog to CMD+K command pallet
• Better optimized for mobile phones

[pi0]

i expect og description to be removed still.

[cpreston321]

i expect og description to be removed still.

I removed the OG Image description.

[atinux]

Shall we maybe find a way to reduce the gap when there are not a lot of updates?

See https://feat-changelogs.undocs.pages.dev/changelog

[danielroe]

Also, see lower down the page:

[pi0]

(moving back to draft status. i like to make some changes to make sure it works stably for adoption)

[cpreston321]

@pi0 the only problem with using ungh was the caching, if you were to release it wouldn't update until the cache is busted. Unless we can force reload on new versions passing in a param to url.

Just an fyi. I am not for sure if we can add anything so the page can be updated with the releases of github.

[pi0]

Yes. I am thinking to rely on CHANGELOG.md instead also we need to render a normal multi section page because generated release notes can have more variable contents (see temporary fixed value for unjs/nitro)