chore: docs: Add more aliases for ++version++ to current

[martin-g]

Reported at apache/avro-rs#22
Discussed at apache/avro-rs#20 (comment)

What is the purpose of the change

• Add more aliases from ++version++ to current in the Hugo based docs

Verifying this change

• cd .../avro/doc
• Start the website locally: hugo server --buildDrafts --buildFuture --bind 0.0.0.0
• in a browser navigate to http://localhost:1313/docs/current/specification/#schema-resolution

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? not applicable

[KalleOlaviNiemitalo]

When 1.13.0 is released, will doc/content/en/docs/++version++/ be copied to doc/content/en/docs/1.13.0/? Will the current aliases have to be deleted from doc/content/en/docs/1.13.0/ at that time?

[martin-g]

Will the current aliases have to be deleted from doc/content/en/docs/1.13.0/ at that time?

Yes! They will have to be deleted.

[KalleOlaviNiemitalo]

The copying and deletion might be worth documenting in the "New release" section of doc/README.md. But I see it's not a new omission as there's already a similar alias since AVRO-4041 commit ea17b9d:

avro/doc/content/en/docs/++version++/_index.md

Lines 5 to 6 in 86fde69

	aliases:
	- /docs/current/

[martin-g]

The copying and deletion might be worth documenting in the "New release" section of doc/README.md.

Please send a PR!

But I see it's not a new omission as there's already a similar alias since AVRO-4041 commit ea17b9d:

I am still learning how Hugo works. I thought that the previous commit will cover all requests to /docs/current/** but it seems it does not. So, we have to cover each and every path manually ...

[martin-g]

IMO the best would be to rename ++version++ to something nicer, like snapshot.
But this itself will need aliasing to prevent 404 links ...