url for cm3 config docs.

[chrisb13]

With this experiment table PR and the cm3 dev eval meetings, we're likely to start sharing a link to the cm3 config docs.

In two other contexts we have:

• https://access-om3-configs.access-hive.org.au/
• https://access-ram3-configs.access-hive.org.au/

I believe these urls might change with the other upcoming doc infra changes? Will a re-direct be used when they are changed?

Hence, would it be possible to get https://access-cm3-configs.access-hive.org.au/ created? (The same problem exists for esm1.6 config docs.)

Or perhaps we are better off waiting until the above is sorted. In any case, my impression is that if we move to RTD then the current link (https://access-nri.github.io/access-cm3-config-docs/) will no longer be used.

ping @atteggiani @MartinDix @heidinett

[atteggiani]

The current URL https://access-nri.github.io/access-cm3-config-docs/ will likely not be used anymore when we move to RTD.
However, since we haven't finalised the URL structure yet, I would not create any other subdomain for now.

I think the temporary RTD link can be shared for now, and when the final URL is set up, we can update that. For the moment, we could add a banner to the website to indicate that the URL is temporary and is likely going to be changed in the near future.

[chrisb13]

However, since we haven't finalised the URL structure yet, I would not create any other subdomain for now.

Ok

I think the temporary RTD link can be shared for now, and when the final URL is set up, we can update that. For the moment, we could add a banner to the website to indicate that the URL is temporary and is likely going to be changed in the near future.

Sounds good -- sorry I forgot you suggested this last year. Can you please add this.

I think it would be sensible to add one to the esm1.6 config docs as well.

[atteggiani]

Can you please add related issues to the repos and assign them to me?

[chrisb13]

H'm, do you think we should for om3 and ram3 too?

Experiment generator?

Have any other subdomains / config docs been created?

[atteggiani]

Yes we could do that for all documentation websites.

[atteggiani]

It might actually be better to avoid doing this now, and plan some redirections whenever the URL are changing.
I think it's easier and will avoid spending time now to flag something most of the people wouldn't notice.

[chrisb13]

It might actually be better to avoid doing this now, and plan some redirections whenever the URL are changing. I think it's easier and will avoid spending time now to flag something most of the people wouldn't notice.

Ok, sounds good.

So does this mean there will also be a re-direct for the cm3 config ones?

[atteggiani]

Yes, we can redirect any website that we control. So we could set up redirections (for a fixed period of time) from one of our websites hosted through GitHub Pages to the new website URL (hosted through RTD).
Of course, if the URL happened to be the same (very unlikely), no redirections are needed.

[chrisb13]

Sounds great. 😄