blog post: Auspice 2024 summary #1089
Conversation
nextstrain-bot
temporarily deployed
to
nextstrain-s-victorlin--45xpgm
| ## View in Other Platforms | ||
|
|
||
| Interoperability between platforms is something we've been big proponents of, | ||
| and are part of [PH4GE](https://pha4ge.org/) to help support this. For many |
There was a problem hiding this comment.
As per comment in the google doc, can someone double check this
There was a problem hiding this comment.
Independent of James's comment: during the move from the GDoc to here, this got turned from a parenthetical aside to a secondary clause in the sentence. The sentence flow is very awkward as a result -- the verb tenses are muddled ("have been" vs "are" ) and the "this" reference reaches a long way back for its antecedent.
I would advocate for changing this to something like "Historically, we have always been strong advocates for interoperability between platforms." and leave it at that, unless there's a specific reason to bring PH4GE into it.
There was a problem hiding this comment.
Thanks, I like your suggested sentence. Switched to it:
nextstrain.org/static-site/content/blog/2024-12-10-auspice-2024.md
Lines 49 to 50 in 58e0190
Also, I've split the changes into verbatim GDoc conversion (706eb89) and my edits on top of that (ca88c2e) to solicit feedback on changes such as this one.
| ## View in Other Platforms | ||
|
|
||
| Interoperability between platforms is something we've been big proponents of, | ||
| and are part of [PH4GE](https://pha4ge.org/) to help support this. For many |
There was a problem hiding this comment.
Independent of James's comment: during the move from the GDoc to here, this got turned from a parenthetical aside to a secondary clause in the sentence. The sentence flow is very awkward as a result -- the verb tenses are muddled ("have been" vs "are" ) and the "this" reference reaches a long way back for its antecedent.
I would advocate for changing this to something like "Historically, we have always been strong advocates for interoperability between platforms." and leave it at that, unless there's a specific reason to bring PH4GE into it.
victorlin
force-pushed
the
victorlin/add-blog-auspice-2024
branch
from
62b2f8c to
ca88c2e
Compare
victorlin
changed the base branch from
master
to
victorlin/blog-heading-links
victorlin
force-pushed
the
victorlin/add-blog-auspice-2024
branch
from
58e0190 to
c7d73f7
Compare
victorlin
force-pushed
the
victorlin/blog-heading-links
branch
from
ac19562 to
5548769
Compare
victorlin
force-pushed
the
victorlin/blog-heading-links
branch
from
5548769 to
ea6f00f
Compare
victorlin
force-pushed
the
victorlin/add-blog-auspice-2024
branch
from
c7d73f7 to
e412d55
Compare
victorlin
force-pushed
the
victorlin/add-blog-auspice-2024
branch
from
e590f44 to
1f9cc8c
Compare
victorlin
force-pushed
the
victorlin/add-blog-auspice-2024
branch
from
51ffcfe to
cd610f4
Compare
A well-deserved blog post for Auspice features! Initial drafting happened in a Google Doc¹, followed by edits from PR review. ¹ https://docs.google.com/document/d/1HxBl_ncaAe6lWxyS5X7JzGoZOSmDGj6pVdfU6JF30Z0/edit Co-authored-by: james hadfield <[email protected]> Co-authored-by: John SJ Anderson <[email protected]> Co-authored-by: Trevor Bedford <[email protected]>
victorlin
force-pushed
the
victorlin/add-blog-auspice-2024
branch
from
cd610f4 to
19c22d9
Compare
preview
Description of proposed changes
A well-deserved blog post for Auspice features!
Related issue(s)
Checklist