New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Versions to function documentation #2323
Comments
New features in v0.120.0 are visually tagged with "New in v0.120.0". That is our common practice, but I inadvertently removed a couple of the tags with a recent change.
I've added a deprecation notice to the site methods deprecated in v0.120.0:
Note that deprecated functions and methods will not appear in lists, including section menus. They will, however, appear in search results. You won't be able to search for them today. The search index will be updated in a few days... I'm guessing the pages will appear in the search results by 15 November 2023. I added two new sections to the documentation guidelines:
Our deprecation practice is described here: |
@jmooring I suggest the deprecation warning to be placed at the start of the page. |
@jmooring : Thanks for your fast response and work! |
Thanks for the work @jmooring. |
With Hugo 0.120.0 I'll get a message regarding
.Site.IsServer
:Since the is coming from one of my themes, I'd like to know since when the replacement
hugo.IsServer
is available to set the required min version intheme.toml
.My proposal is as follows:
Each function documentation page (like for
hugo.IsServer
) should have a fieldsince
indicating the version in which a function has been introduced. The same goes for deprecated functions (or variables) like.Site.IsServer
, they should't been silently removed from the docs, but marked as deprecated.BTW: Maybe this issue need to be moved.
The text was updated successfully, but these errors were encountered: