Manuel Kaufmann

Maybe related to: * https://github.com/readthedocs/readthedocs.org/pull/11003

Yeah, I did a quick try upgrading this to check if the TemplateSyntaxError was faster, but it was the same. So, there is no rush on moving forward with this...

> with the [ENV syntax](https://www.mkdocs.org/user-guide/configuration/#environment-variables) to read environment variables, making the `READTHEDOCS` vars available to the template context: Reading that documentation, I arrived at https://github.com/waylan/pyyaml-env-tag#enabling-the-tag. It doesn't work on Read...

Hi @j1elo! Thanks for replying. You have mentioned here some interesting points that have been in our discussions lately but we haven't yet had the time to fix them. >...

> I hope we can clarify these limitations in our documentation. @astrojuanlu what do you think about mentioning that non-standard (or advanced) YAML usage is not supported currently? It seems...

Once #10166 gets merged we will be exposing the canonical URL as `READTHEDOCS_CANONICAL_URL` environment variable that people can use from MkDocs and any other doctool. However, the normal build process...

@MetalKnight56 yes, take a look at option 2) from https://github.com/readthedocs/readthedocs.org/issues/8529#issuecomment-1477671374

Hi 👋🏼 . Starting on April 15th the usage of special `!` syntax will be allowed since we are going to stop the manipulation of `mkdocs.yml` we were doing previously....

Moving this under the new templates work, since it's more related to the UX when importing a project than anything else.

I think we want to do this at the frontend > A warning be displayed to the user at project creation if the generated slug exceeds a certain threshold. I'm...