-
Notifications
You must be signed in to change notification settings - Fork 56
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
Newsletter December 2022 #189
Conversation
newsletter-december-2022.rst
Outdated
The latest updates from our team: | ||
|
||
- 🐘️ We started *tooting* in the Fediverse (Mastodon): `@readthedocs@fosstodon.org <https://fosstodon.org/@readthedocs>`_ | ||
- 🎬️ Visit the upcoming landing page `about.readthedocs.com <https://about.readthedocs.com/>`_ and let us know if you have comments or ideas for it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@agjohnson is it good to announce it like this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's looking good!
Unrelated, would you mind adding https://github.com/readthedocs/actions/tree/main/preview so we can have a link to the rendered PR?
Co-authored-by: Manuel Kaufmann <humitos@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This newsletter is definitely getting very long. I'd really like to avoid adding more editorial content, and pulling that content out into discrete blog posts and twitter threads. They are much more discoverable as their own postings, and users will rarely find this kind of stuff as an h2 inside something called "newsletter". It's also much better for SEO to have a discrete blog post. We will not really rank for sphinx 6 release
with this content, but a dedicated post would.
Co-authored-by: Eric Holscher <25510+ericholscher@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is ready to ship with the changes. I don't think we need to block on the Sphinx 6 changes, we can just mention them in the Possible issues
section and that we'll have more soon. Though I'm also fine shipping them together, perhaps tomorrow so we have time to polish the Sphinx 6 stuff.
Not sure what to make of these sudden warnings:
The referenced resource seems to be present: https://sphinx-hoverxref.readthedocs.io/en/stable/usage.html#tooltip-on-sphinx-domains |
Oh now the warnings went away on the latest build 👍 |
… into newsletter-december2022
Merging with some minor improvements of prose. |
No description provided.