Deploy preview:

• Since visible: https://deploy-preview-93--dexidp.netlify.app/docs/connectors/ldap/
• Since not present: https://deploy-preview-93--dexidp.netlify.app/docs/connectors/

last force-push uses a sane if statement 😅

I have a question. Do we want to change the version in this field if we changed the config of the connector, e.g., added a new option?
For example, the LDAP connector was added a long time ago, but in the release v2.23.0 its settings were rearranged. Thus, documentation on the website is only valid since dex v2.23.0.

Thanks @nate-double-u

I had the following in mind:

• add a since version "badge" to pages
• add "badges" within pages for new features

I think that would answer your question @nabokihms

Also, I don't think we have to add it to every page/connector.

So something that could be added (almost like a label) next to a line of copy or a paragraph?

Either that, or something like this on the Symfony website: https://symfony.com/doc/current/routing.html

I understand now.

On their site, the following

.. versionadded:: 5.2

    The ability to use PHP attributes to configure routes was introduced in
    Symfony 5.2. Prior to this, Doctrine Annotations were the only way to
    annotate controller actions with routing configuration.

generates this

I like that, but it's a bit more involved. I think I can piggyback off the note or warning annotations to achieve this -- you can see how they look live here. (We may want to pull them (notes and warnings) in from upstream as well, but that's probably a separate issue)

Yeah, something like that would be great. I think we can create custom shortcodes/snippets in Hugo.

For example, a custom version admonition could accept a version as a parameter and use that internally to compare it to the current version in the config file. I don't know if Hugo templates has a semver function for that though.

This is still very much just an idea, so if there are other, better patterns out there, I'm all ears.

@nate-double-u I started something very simple in #132

Do you think you could help finishing it (adding some style, etc)

Hi--I'm on vacation this week, but can take a look when I'm back 🙂

I'm going to close this PR. Now we've moved to Docsy we'd need a different implementation I think.