Repository navigation
Issue-3894-Bulletin-12 - #3896
Merged
Merged
Conversation
Create Markdown file for Q3 Bulletin.
- Add buttondown subscribe button
Update Next issue date, line 107.
Italics, line 53.
Close line break, line 55.
Contributor
Author
|
Hola Riva @rivaquiroga, I've staged Bulletin // Boletín // Bulletin // Boletim Issue 12 for publication, including (right near the bottom of the page), a Buttondown subscribe button so people can receive the next newsletter direct to their inbox if they prefer! You can read it in preview here. The only problems are the characters č and ć which don't render well on our site 😞 |
rivaquiroga
approved these changes
Oct 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Staging publication of Bulletin // Boletín // Bulletin // Boletim Issue 12.
Closes #3894
Checklist
Closes #ISSUENUMBERto your summary above[ ] if the text needs to be translated, please follow the translation request guidelines, then assign the relevant language team(s) as "Reviewers" and tag both the team as well as the managing editor in your PR.