Skip to content

Conversation

@pdmosses
Copy link
Contributor

@pdmosses pdmosses commented Sep 24, 2022

Extension of PR #977 to v0.4.0.rc1:

  • Replace a warning paragraph by a callout.
  • Use a reference link instead of an explicit url for @pmarsceill .
  • Add link reference definitions for PRs and new contributors in v0.4.0.rc1.
  • Replace inline urls by shortcut link references.

The changes to replace URLs by link references would be too tedious and error-prone to do completely manually for v0.4.0.rc1. The following regexp replacements were applied to the sections of v0.4.0.rc1, using Atom:

Copy a section of changes.

  • In the copy, replace .*(https://.*pull/)([0-9]+).*$ by [#$2]: $1$2.
  • In the original, replace (https://.*pull/)([0-9]+) by [#$2].

Copy a section of new contributors.

  • In the copy, replace \* @([^ ]+) .*$ by [@$1]: https://githhub.com/$1.
  • In the original, replace @([a-zA-Z0-9]+) by [@$1].

Add (co)authors in #578:

To test:

  1. Check that the CHANGELOG contents looks the same in the docs and in the repo (apart from the callouts) with clickable links to all PRs and contributors for v0.4.0.rc1.

  2. Check that none of the lines with changes or new contributors have been removed.

Extension of PR just-the-docs#977 to v0.4.0.rc1:

- Make callouts `loud`.
- Replace a warning paragraph by a callout.
- Use a reference link instead of an explicit url for @pmarsceill .
- Add link reference definitions for PRs and new contributors in v0.4.0.rc1.
- Replace inline urls by shortcut link references.

The changes to replace URLs by link references would be too tedious and error-prone to do completely manually for v0.4.0.rc1.
The following regexp replacements were applied to the sections of v0.4.0.rc1, using Atom:

- Copy a section of changes.
- In the copy, replace `.*(https://.*pull/)([0-9]+).*$` by `[#$2]: $1$2`.
- In the original, replace `(https://.*pull/)([0-9]+)` by `[#$2]`.

- Copy a section of new contributors.
- In the copy, replace `\* @([^ ]+) .*$` by `[@$1]: https://githhub.com/$1`.
- In the original, replace `@([a-zA-Z0-9]+)` by `[@$1]`.

Add (co)authors in [just-the-docs#578]:

* [@AdityaTiwari2102] made their first contribution in [just-the-docs#477]
* [@svrooij] made their first contribution in [just-the-docs#544]

[@AdityaTiwari2102]: https://githhub.com/AdityaTiwari2102
[@svrooij]: https://githhub.com/svrooij

To test:

1. Check that the CHANGELOG contents looks the same in the docs and in the repo (apart from the callouts) with clickable links to all PRs and contributors for v0.4.0.rc1.

2. Check that none of the lines with changes or new contributors have been removed.
@pdmosses pdmosses requested a review from mattxwang September 24, 2022 22:06
@pdmosses
Copy link
Contributor Author

In view of the many changes in the forthcoming v0.4.0, I think it's important for readers of the theme docs who are migrating from v0.3.3 to see:

  1. a link to the formatted CHANGELOG in the navigation panel, and
  2. clickable links to PRs (and contributors)

(I don't intend to extend this to the changes made in v0.3.3 and earlier, as the entries there are less regular.)

Copy link
Member

@mattxwang mattxwang left a comment

Choose a reason for hiding this comment

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

Generally LGTM, really appreciate you putting the effort into this!

Quick question - any specific reason on making the callouts loud? In a side-by-side comparison, I actually find the quiet ones (i.e. what's on the site now) easier to read!

@pdmosses
Copy link
Contributor Author

Quick question - any specific reason on making the callouts loud? In a side-by-side comparison, I actually find the quiet ones (i.e. what's on the site now) easier to read!

I don't have a particular preference on this. You previously mentioned:

Note: think we need to adjust some of the defaults for the dark theme. Seems too inaccessible - for example, the green callout on the homepage is hard for me to read personally (from a contrast perspective). Same thing with the copyright footer, etc.

But we're using the light scheme for the theme docs, so making them loud there doesn't address that issue.

After v0.4.0, I think we should try to improve callout colours in connection with WCAG. Maybe GitHub Primer has some good suggestions.

@pdmosses
Copy link
Contributor Author

Anyway, please feel free to change the config for the theme docs back to quiet before merging. Let me know if you prefer me to update the PR branch myself.

@pdmosses
Copy link
Contributor Author

@mattxwang the PR interface is encouraging me to update the branch by merging main into it. But I'm hesitating to do that, in case it would have unforeseen consequences for the commit history…

@mattxwang
Copy link
Member

encouraging me to update the branch by merging main into it.

This should always be fine, since we squash merge! It's okay though, I'll handle this merge!

@mattxwang mattxwang merged commit ce82082 into just-the-docs:main Sep 26, 2022
@pdmosses pdmosses deleted the make-more-CHANGELOG-urls-clickable branch November 3, 2022 11:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants