chore: prepare for v3 release

[jonaslagoni]

Description
This PR removes all v2-specific resources and tracks what needs to change for v3.

Saw a lot of tooling related docs that might or might not need to update once the library supports v3, not sure what to do about that one 🤔

It might look like a lot needs to change, however, for many of these resources, they require a small change.

Tasks todo after merge:

• Create an issue to track each change needed on the website

Changes required:

• Frontpage demo animation components/DemoAnimation.js (probably the highest priority as its not something that can be removed 😅)
• Adapt GH-actions tooling page
• Remove links to v2 AsyncAPI spec documents
• Change the last Remember section of docs/concepts/application
• docs/tutorials/getting-started/coming-from-openapi
• docs/tutorials/getting-started/hello-world
• docs/tutorials/getting-started/asyncapi-documents
• docs/tutorials/getting-started/servers
• docs/tutorials/getting-started/security
• docs/tutorials/create-asyncapi-document
• docs/tutorials/studio-document-validation
• docs/tutorials/streetlights-interactive
• docs/guides/validate
• docs/guides/message-validation
• tools/parsers

Related issue(s)
Related to #1650

[quetzalliwrites]

Whoaaaa, are you trying to delete several of these docs? 😄

I specifically remember @smoya saying that the tutorials were fine and only a few spots needed updates. I don't think mass deletion is the way to go here. 🤔 We should def discuss more in our Thursday meeting this week for sure, there are def items we want to clarify ✌🏽

[jonaslagoni]

I deleted all that needed to be re-written, so yes the selection are intentional 😄 does not matter what @smoya might have said, I went through all the docs that had v2 related stuff (also examples) that needed to change, some i fixed because it was 20s fix. Others not so much 😄

But yea definitely gonna bring it up there as well 🙂

[jonaslagoni]

Also, I am not removing them, I am preparing for them to be upgraded to v3 😄

[quetzalliwrites]

I can't wait to ask you my other 1,000,000,000,000,000,000 questions on Thursday call 📞🤪

[jonaslagoni]

Lets hope we have enough time then 😆

[quetzalliwrites]

expect to be fully exploited for the entire meeting hour at least 😈

[derberg]

if we go with cleanup and removal, then @jonaslagoni all the reference docs prior 3.0 should also be removed from the website that will cover 3.0

[smoya]

All removed docs are ok to me as the list of documents that should change for v3.
However, I believe we should also include the github-actions page as generator will need to be upgraded (updating the parser version) at some point after releasing v3 so it supports it.
Correct me if I'm wrong @jonaslagoni

[jonaslagoni]

if we go with cleanup and removal, then @jonaslagoni all the reference docs prior 3.0 should also be removed from the website that will cover 3.0

@derberg I actually think it's relevant to keep those, also why I have not removed them 🤔 It's something we can discuss in another issue I think.

[jonaslagoni]

All removed docs are ok to me as the list of documents that should change for v3. However, I believe we should also include the github-actions page as generator will need to be upgraded (updating the parser version) at some point after releasing v3 so it supports it. Correct me if I'm wrong @jonaslagoni

@smoya No idea how that library works 😄 Probably. Not something I want to change here I think.

[smoya]

@smoya No idea how that library works 😄 Probably. Not something I want to change here I think.

I confirm you that the GH action usage of that example will change.

      - name: Generating HTML from my AsyncAPI document
        uses: asyncapi/[email protected]

The version in use of that action will change, because a new release of asyncapi/github-action-for-generator will be needed updating the generator which will update the parser to the version that supports AsyncAPI v3.
So, I suggest you remove the file as well.

[jonaslagoni]

@smoya this is not a final PR, just the first one, lets get this merged and I can adapt the GH-actions stuff afterwards. I think we can do

      - name: Generating HTML from my AsyncAPI document
        uses: asyncapi/github-action-for-generator

[smoya]

@smoya this is not a final PR, just the first one, lets get this merged and I can adapt the GH-actions stuff afterwards. I think we can do

      - name: Generating HTML from my AsyncAPI document
        uses: asyncapi/github-action-for-generator

But why dont you just remove the file as you did with the others?

[jonaslagoni]

But why dont you just remove the file as you did with the others?

@smoya because it's linked in the menu, so it's not JUST removing the file, it needs additional change which I really try to avoid. I.e. why I manually changed the parser page and the frontpage have not changed.

[smoya]

But why dont you just remove the file as you did with the others?

@smoya because it's linked in the menu, so it's not JUST removing the file, it needs additional change which I really try to avoid. I.e. why I manually changed the parser page and the frontpage have not changed.

Ok then i guess LGTM. CC @alequetzalli

[derberg]

@derberg I actually think it's relevant to keep those, also why I have not removed them 🤔 It's something we can discuss in another issue I think.

you mean relevant for what? docs for v2 should be under different domain, spec is docs. So the only thing we can have is a panel above v3 spec saying where v2 is

[jonaslagoni]

you mean relevant for what? docs for v2 should be under different domain, spec is docs. So the only thing we can have is a panel above v3 spec saying where v2 is

@derberg Hm, I disagree with the spec-related documents, they are THE standard, not just documentation, I always find it super annoying that I don't with one click have access to previous versions. But then again I don't have any strong feelings, I'll adapt 😆

But anyways, we can change it after this is merged 🙂

[derberg]

@jonaslagoni this PR is called preparation, so why not do it now?

I always find it super annoying that I don't with one click have access to previous versions

as I wrote, we can add some panel with easy link. We should not have v2 just like in v2 we do not have v1

[jonaslagoni]

Because this PR is one of many, so i try to keep them as small as possible 😅

I have already added it to the todo list

[quetzalliwrites]

LGTM

[jonaslagoni]

/rtm

[jonaslagoni]

Thanks @alequetzalli 🎉

Gonna follow up with a bunch of issues 😄

[jonaslagoni]

Ah, nwm, still need a codeowner to review 😆

[derberg]

/rtm

[jonaslagoni]

Seems like netlify CI is stuck 🤨

[derberg]

yeah, there are no previews configured for that branch 😄
I will not make it required for next-major-spec

[derberg]

/rtm

[jonaslagoni]

Added all the followup issues.