Move some features out of Beta in documentation

[privatemaker]

There are multiple really great features under Beta Features in Decap, but the only way to find them is to feel adventurous and navigate there in the documentation.

Many of these nice features have been available and some are stable for awhile now. Do some of them have bugs? Sure. Just like many other parts of Decap, just like a lot of software.

Is there a process to determine when one of these features is no longer in Beta and thus moved to be alongside it's more logical place within the documentation?

It seems this should be discussed and some things probably moved out of Beta status 😄

[martinjagodic]

That's a very good point @privatemaker.

My proposal: remove that Beta Features section, and just tag Beta features as such. Based on your criteria I think the only Beta Feature is the Editorial Workflow. Everything else works as documented. At worst, there are known issues that are well described here.

[privatemaker]

Yeah that seems correct to me @martinjagodic I can try sending a pull-req if there is more consensus to do this and no-one else wants to!

[martinjagodic]

A PR would be amazing. I am ready to help once you open it.

Note that this is actually a duplicate of #4608. I will close the older one as activity is happening here.

[privatemaker]

While working on #7051 I realized the changes made in these pull-reqs are likely to leave a lot of old links on the internet such as: /docs/beta-features/#working-with-a-local-git-repository which will show 404 pages and thus confused users.

Before this is marked as closed, this should be looked into. I am not a Gatsby developer, but AFAICT from their redirect documentation it does not mention handling links with /url/path/#anchor-tag

[martinjagodic]

I agree. I can add redirects to the _redirects file so it's handled by Netlify.