Skip to content

Conversation

@flicj191
Copy link
Contributor

@flicj191 flicj191 commented Feb 13, 2025

Description

Draft PR to build documentation separately

Parallel esmvalcore pr:
ESMValGroup/ESMValCore#2732


Before you get started

Checklist

It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

To help with the number of pull requests:

@valeriupredoi
Copy link
Contributor

wonderful, many thanks for taking on this @flicj191 🍺

@flicj191
Copy link
Contributor Author

https://esmvaltool--3914.org.readthedocs.build/en/3914/index.html

  • top navigation is simplified
  • document navigation on the side splits the parts
  • consider maintaining current domains? and keep subproject

@flicj191
Copy link
Contributor Author

Parallel esmvalcore pr:
ESMValGroup/ESMValCore#2732

@flicj191 flicj191 marked this pull request as ready for review May 23, 2025 04:31
@flicj191 flicj191 requested review from ehogan and malininae May 23, 2025 04:31
Copy link
Contributor

@ehogan ehogan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @flicj191 🎉

I added some thoughts. I hope they are useful! 😊

Comment on lines 47 to 55
How to contribute
-----------------
Refer to ESMValTool :ref:`contributing to the community<community>` for a guide on contributing recipes and diagnostics.

For more detailed information, the documentation is available below.
Refer to ESMValCore :ref:`Contributing <contributing>` for information on contributing code.

Get in touch! Contact information is available :ref:`here <Support-and-Contact>`.
Get in touch!
-------------
Contact information is available :ref:`here <Support-and-Contact>`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be useful to have this information on every page. Could it be added to the footer, or the secondary sidebar (under the "Show Source" link)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea!
So you mean each of the 3 links? (ESMValTool contributing, ESMValCore contributing, Support and contact)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe just "ESMValTool contributing", then "support and contact"? The ESMValCore pages can have the equivalent "ESMValCore contributing"?

(I have code that can create the following in the secondary sidebar, if you'd like me to share) 😊
image

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change would also make the main page less busy 😊

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @ehogan can you share the code please? I think there could also be a version thing going on as it doesn't look quite the same as what the theme documentation is showing

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I opened a new issue for this (#4215) to allow this PR to be merged 😊

Comment on lines +27 to +32
.. container::
:name: figarch

.. figure:: figures/ESMValSchemaDiagram.png
:alt: Brief topics for tool and core.
:figclass: align-center
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the diagram; would it be worth also adding specific links to the topics mentioned?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking its more a condensed diagram to assist in understanding with the broader topics but these topics might need to be reviewed and refined, I'm not sure there would be appropriate specific links to them all

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having a nice diagram like this one (plus the two describing sentences) on the landing page makes the relation of the packages very clear. Well done.
Providing links to each topic here would also require revision whenever structure in the documentation changes. I'd keep the image as conceptional and condensed as possible and make the sidebar as structured and self explanatory as possible. As the sidebar only shows the structure of the ESMValTool part, do you think we should link to the ESMValCore documentation again. In the last sentence here and/or the description of the ESMValCore package above?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bouweandela for the diagram, fair point with links as well but it was a rough diagram and I wasn't thinking of specific pages but just to help with understanding. If topics get out of date it would still need to be updated even if links are still correct?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I still think it would be nicer to generate it dynamically from the documentation pages, but if that's technically too challenging, it's fine to leave it as is.

@flicj191
Copy link
Contributor Author

@ehogan Thanks very much for your comments! They were useful, sorry it's been a delay to get back to this.

@flicj191
Copy link
Contributor Author

If we are sure, that the esmvalcore documentation will still be deployed as part of the esmvaltool documentation I'm happy to approve the PR. Otherwise I'd like to run some link checkers again, since I suspect there could be some hardcoded references in the documentation.

Thanks very much @lukruh! Your comments were helpful! This I'm not too sure with the advantages/disadvantages and may need to be discussed in a meeting/workshop

Copy link
Contributor

@lukruh lukruh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the additional changes. The documentation appears a lot cleaner and better structured. I'd like to see this merged before the next workshop.

@flicj191 flicj191 removed the request for review from malininae July 22, 2025 04:34
@flicj191
Copy link
Contributor Author

Thanks for your help @lukruh!
Any other thoughts? @ehogan @malininae @bouweandela @valeriupredoi @rbeucher

Copy link
Contributor

@ehogan ehogan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is really great, thank you for all your hard work on this @flicj191! 🎉

A few additional suggestions from me 😊

@flicj191 flicj191 changed the title Separate ESMValTool and ESMValCore documentation - restructure header Separate ESMValTool and ESMValCore documentation Sep 4, 2025
Copy link
Contributor

@ehogan ehogan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many thanks for your hard work on this @flicj191! 🎉

The outstanding comments I had have been captured in a new issue (#4215), so I am approving this PR 😊

@bettina-gier bettina-gier merged commit 5294af4 into main Oct 27, 2025
8 checks passed
@bettina-gier bettina-gier deleted the doc_split branch October 27, 2025 09:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Documentation separation ESMValTool and ESMValCore

6 participants