Might be hard for me to phrase it for you (it means that note would include a statement about where
Might be hard for me to phrase it for you (it means that note would include a statement about where those products are heading in terms of support - which is usually something that triggers internal discussions around the phrasings 
). But feeling helpful I tried. Realized it's hard not to turn it into a deprecation notice though, but it's still nice to be open with this info to all the users from the beginning, so putting a PR for the last suggestion: https://github.com/cloudflare/cloudflare-docs/pull/17788
"We will continue support this solution, but our long-term support and new development will focus on deploying Next.js apps to..." messes up the meaning of the original phrasing though, but it'll change anyway before the PR get's merged, it always does
). But feeling helpful I tried. Realized it's hard not to turn it into a deprecation notice though, but it's still nice to be open with this info to all the users from the beginning, so putting a PR for the last suggestion: https://github.com/cloudflare/cloudflare-docs/pull/17788"We will continue support this solution, but our long-term support and new development will focus on deploying Next.js apps to..." messes up the meaning of the original phrasing though, but it'll change anyway before the PR get's merged, it always does
GitHub
Summary
People starting out new projects should easily see where the support for different products are heading. To avoid some friction. Got this info from the next-on-pages discord and it was sugg...
People starting out new projects should easily see where the support for different products are heading. To avoid some friction. Got this info from the next-on-pages discord and it was sugg...
