Skip to content
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 a new documentation group for "technical explanations" or "showcases" #2834

Open
seisman opened this issue Nov 27, 2023 · 3 comments
Open
Labels
discussions Need more discussion before taking further actions

Comments

@seisman
Copy link
Member

seisman commented Nov 27, 2023

Justification codes like BL and TR are commonly used in GMT and PyGMT. Currently, we have explanations like:

The justification is a two-character code that is a combination of a horizontal (L\ (eft), C\ (enter), or R\ (ight)) and a vertical (T\ (op), M\ (iddle), or B\ (ottom)) code.

Instead of repeatedly explaining justification codes in different plotting methods, I feel it makes more sense to have a separate page explaining justification codes then we can link to this page when necessary.

Looking at the divio documentation system, I feel it should belong to "Reference" documentation, rather than "Tutorials". Currently, we have an "API Reference" page (https://www.pygmt.org/dev/api/index.html), but apparently "justification" is not an API thing. Maybe we need another section like "Technical Reference" or something else?

@yvonnefroehlich
Copy link
Member

Thanks @seisman for pointing out this aspect! This documentation concept page looks interesting - thanks for posting the link!

We have multiple docstrings and examples that mention these 2-character codes for the position and justify parameters:

I agree it would be better to have this bundled in one place, and link to it in the docstrings and examples.

If we decide on any kind of "technical reference", what would make sense to include beside these 2-character codes? Maybe:

@seisman
Copy link
Member Author

seisman commented Dec 4, 2023

If we decide on any kind of "technical reference", what would make sense to include beside these 2-character codes? Maybe:

I believe there are a lot that can be added to this "section":

  1. List of plotting symbols/markers, similar to https://matplotlib.org/stable/api/markers_api.html
  2. List of supported fonts?
  3. How PyGMT parameters converts to GMT command line options [very technical but maybe useful to some new maintainers and even users]
  4. Explanation of some common options/parameters.
  5. How the "current" CPT works.
  6. ...

@seisman seisman changed the title Add explainations for justification codes Add a new documentation group for "technical explanations" or "showcases" Dec 19, 2023
@seisman
Copy link
Member Author

seisman commented May 25, 2024

Ping @GenericMappingTools/pygmt-maintainers for more discussions on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussions Need more discussion before taking further actions
Projects
None yet
Development

No branches or pull requests

2 participants