Add blogpost about API Tools retirement

[arhimede]

@froschdesign I am not sure if is the right moment to publish this blog post , but i am targeting Jetbrains PHP Annotated newsletter

[froschdesign]

Overall, it reads like a summary of a meeting, but the focus should be on the results of the API tools. That's why the entire text seems too sober, even though it should be a promotional text and needs more advertising character.
At least that's the conclusion I draw if you're aiming at the newsletter.

[arhimede]

I am still thinking to add more phrases about Laminas API Tools

[froschdesign]

@arhimede

I am still thinking to add more phrases about Laminas API Tools

The other way round: there are too many trivialities. If the Dotkernel API is the new shiny thing then this should also be advertised accordingly. Look forwards and not backwards, because the API tools are history.

The following should be included:

• what are the new and better features
• why is the change a good idea
• and what is still to come

The reason why the API tools are not being continued should be included, but not more than this.

---

This post can serve as the basis for the new block on the homepage. (Later we can add a separate page.)

[arhimede]

Maybe we can use other titles ?

• Retiring Laminas Api Tools makes way for DotKernel API
• DotKernel API: a replacement for security-only Laminas Api Tools (formerly Apigility)
• Dotkernel API: an alternative for legacy Laminas Api Tools (formerly Apigility)

[froschdesign]

My suggestion:

"Dotkernel API: a replacement for legacy Laminas API Tool"

[arhimede]

Quite ready to be published.