docs: add a minimal changelog page
This commit is contained in:
@@ -3,7 +3,11 @@ tableOfContents: true
|
|||||||
---
|
---
|
||||||
|
|
||||||
# Changelog
|
# Changelog
|
||||||
|
Tiptap consists of more than 50 separate packages, so it’s not that easy to keep that one big changelog. We got you covered though. Here is everything you need to follow the development during the beta phase:
|
||||||
|
|
||||||
:::warning
|
1. You can find the [changelog for the core package](https://github.com/ueberdosis/tiptap/blob/main/packages/core/CHANGELOG.md) on GitHub here.
|
||||||
Oops, we didn’t find time to fill this page. Writing documentation needs attention to detail, a great understanding of the project and time to write. Though Tiptap is used by thousands of developers all around the world, it’s still a side project for us. Let’s change that and make open source our full-time job! [Become a sponsor!](https://github.com/sponsors/ueberdosis)
|
2. All packages have [a separate `CHANGELOG.md`](https://github.com/ueberdosis/tiptap/blob/main/packages), too.
|
||||||
:::
|
3. During beta, it’s also helpful to keep an eye on the [merged Pull Requests on GitHub](https://github.com/ueberdosis/tiptap/pulls?q=is%3Apr+is%3Aclosed).
|
||||||
|
4. And we keep track of [what we want do do before a stable release](https://github.com/ueberdosis/tiptap/issues/2087) in a public issue.
|
||||||
|
|
||||||
|
Once we’re transitioning to a stable version, [we’ll write blog posts](/blog) about bigger changes and keep them in a changelog here.
|
||||||
|
|||||||
@@ -50,7 +50,6 @@
|
|||||||
link: /overview/upgrade-guide
|
link: /overview/upgrade-guide
|
||||||
- title: Changelog
|
- title: Changelog
|
||||||
link: /changelog
|
link: /changelog
|
||||||
type: draft
|
|
||||||
- title: About the project
|
- title: About the project
|
||||||
link: /about
|
link: /about
|
||||||
type: sponsor
|
type: sponsor
|
||||||
|
|||||||
Reference in New Issue
Block a user