Publishing Call for Proposals (English edition) #3677
Merged
Conversation
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
Create EN call for proposals blog post.
Correct YYYY, line 14
Adjust list sub-headings and spacing, lines 34-45
- Add Q on translation sample - Combine final two optional questions on draft code/draft text
- Remove example topics - Minor revisions to formatting
Update note in author-guidelines
Update note in contribute.md
Minor adjustments
Add Laura's middle name
Rename file.
Minor edits.
- Re-organise sub-headings.
- Edit line 26.
Revise structure to align with revised Google Form.
Replace 'case study' with 'use case'.
hawc2
approved these changes
Nov 19, 2025
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.
Preparing a Call for Proposals (English edition).
Closes #3676
Checklist
Closes #ISSUENUMBERto your summary aboveif 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.