-
Notifications
You must be signed in to change notification settings - Fork 227
Closing comment
Anisa Hawes edited this page Dec 6, 2023
·
5 revisions
After publication, we thank contributors, share our suggested citation, and invite participants to help circulate our social media announcements about the lesson. This step also provides an opportunity to build support for the project through our Institutional Partnership Programme.
Contents of this page:
_Lesson title_ is published!
Congratulations @author / @translator!
Thank you **all** for your contributions
---
Our suggested citation for this lesson is:
>[CITATION], https://doi.org/10.XXXX/phxxXXXX.
We appreciate your help to circulate our social media announcements about this lesson among your networks:
Twitter/X: https://twitter.com/ProgHist/status/xxxx
Mastodon: https://hcommons.social/@proghist/xxxx
---
I'd be also grateful if you might consider supporting our efforts to grow _Programming Historian_'s [community of Institutional Partners](https://programminghistorian.org/en/ipp). This is a [network of organisations](https://programminghistorian.org/en/supporters) across Europe, Canada, North America and Latin America who have invested in our success by contributing an annual membership fee in lieu of subscription.
Institutional Partnerships enable us to keep developing our model of sustainable, open-access publishing, and empower us to continue creating peer-reviewed, multilingual lessons for digital humanists around the globe.
If you think that supporting Open Access initiatives may be among the strategic priorities of the university or library where you work, please let me know.
You can email me <admin [@] programminghistorian.org>, and I can send you an information pack to share with your colleagues. Alternatively, feel free to put me in touch with the person or department you think would be best-placed to discuss this opportunity.
Sincere thanks.
_Lesson title_ is published!
Congratulations @author / @translator!
Thank you **all** for your contributions
---
Our suggested citation for this lesson is:
>[CITATION], https://doi.org/10.XXXX/phxxXXXX.
We appreciate your help to circulate our social media announcements about this lesson among your networks:
Twitter/X: https://twitter.com/ProgHist/status/xxxx
Mastodon: https://hcommons.social/@proghist/xxxx
---
I'd be also grateful if you might consider supporting our efforts to grow _Programming Historian_'s [community of Institutional Partners](https://programminghistorian.org/es/pia). This is a [network of organisations](https://programminghistorian.org/es/colaboradores) across Europe, Canada, North America and Latin America who have invested in our success by contributing an annual membership fee in lieu of subscription.
Institutional Partnerships enable us to keep developing our model of sustainable, open-access publishing, and empower us to continue creating peer-reviewed, multilingual lessons for digital humanists around the globe.
If you think that supporting Open Access initiatives may be among the strategic priorities of the university or library where you work, please let me know.
You can email me <admin [@] programminghistorian.org>, and I can send you an information pack to share with your colleagues. Alternatively, feel free to put me in touch with the person or department you think would be best-placed to discuss this opportunity.
Sincere thanks.
_Lesson title_ is published!
Congratulations @author / @translator!
Thank you **all** for your contributions
---
Our suggested citation for this lesson is:
>[CITATION], https://doi.org/10.XXXX/phxxXXXX.
We appreciate your help to circulate our social media announcements about this lesson among your networks:
Twitter/X: https://twitter.com/ProgHist/status/xxxx
Mastodon: https://hcommons.social/@proghist/xxxx
---
I'd be also grateful if you might consider supporting our efforts to grow _Programming Historian_'s [community of Institutional Partners](https://programminghistorian.org/fr/pi). This is a [network of organisations](https://programminghistorian.org/fr/nos-soutiens) across Europe, Canada, North America and Latin America who have invested in our success by contributing an annual membership fee in lieu of subscription.
Institutional Partnerships enable us to keep developing our model of sustainable, open-access publishing, and empower us to continue creating peer-reviewed, multilingual lessons for digital humanists around the globe.
If you think that supporting Open Access initiatives may be among the strategic priorities of the university or library where you work, please let me know.
You can email me <admin [@] programminghistorian.org>, and I can send you an information pack to share with your colleagues. Alternatively, feel free to put me in touch with the person or department you think would be best-placed to discuss this opportunity.
Sincere thanks.
_Lesson title_ is published!
Congratulations @author / @translator!
Thank you **all** for your contributions
---
Our suggested citation for this lesson is:
>[CITATION], https://doi.org/10.XXXX/phxxXXXX.
We appreciate your help to circulate our social media announcements about this lesson among your networks:
Twitter/X: https://twitter.com/ProgHist/status/xxxx
Mastodon: https://hcommons.social/@proghist/xxxx
---
I'd be also grateful if you might consider supporting our efforts to grow _Programming Historian_'s [community of Institutional Partners](https://programminghistorian.org/pt/ppi). This is a [network of organisations](https://programminghistorian.org/pt/apoiadores) across Europe, Canada, North America and Latin America who have invested in our success by contributing an annual membership fee in lieu of subscription.
Institutional Partnerships enable us to keep developing our model of sustainable, open-access publishing, and empower us to continue creating peer-reviewed, multilingual lessons for digital humanists around the globe.
If you think that supporting Open Access initiatives may be among the strategic priorities of the university or library where you work, please let me know.
You can email me <admin [@] programminghistorian.org>, and I can send you an information pack to share with your colleagues. Alternatively, feel free to put me in touch with the person or department you think would be best-placed to discuss this opportunity.
Sincere thanks.
- Copyediting
- Copyedit comments
- Typesetting
- Archival Hyperlinks
- Copyright
- DOI
- Gallery image
- Checklist comment
- Handover comment
- Closing comment
- Opening comment Phase 0
- Phase change comment 1 to 2
- Phase change comment 2 to 3
- Phase change comment 3 to 4
- Opening comment Phase 4
- Phase change comment 4 to 5
- Phase change comment 5 to 6
- Phase change comment 6 to 7
- Tracking lesson phase changes
- Organisational Structure
- Trustee Responsibilities
- Trustee and Staff Roles
- Services to Publications
- Funding
Training
- Onboarding-Process-for-New-Editors
- Leading-a-Shadowing-process
- Board-of-Director---Continuing-Development
The Ombudsperson Role
Technical Guidance
- Making Technical Contributions
- Creating Blog Posts
- Service Integrations
- Brand Guidelines
- French Translation Documentation
- Technical Tutorial on Translation Links
- Technical Tutorial on Setting Up a New Language
- Technical Tutorial on Search
- Twitter Bot
- Achieving-Accessibility-Alt-text-Colour-Contrast
- Achieving-Accessibility:-Training-Options
Editorial Guidance
- Achieving Sustainability: Copyediting, Typesetting, Archival Links, Copyright Agreements
- Achieving Sustainability: Lesson Maintenance Workflow
- Achieving Sustainability-Agreed-terminology-PH-em-português
- Training and Support for Editorial Work
- The-Programming-Historian-Digital-Object-Identifier-Policy-(April-2020)
- How to Request a New DOI
- Service-Agreement-Publisher-and-Publications
- ProgHist-services-to-Publications
- Technical Tutorial on Setting Up a New Language
- Editorial Recruitment
Social Guidance
Finances
- Project Costs
- Spending-Requests-and-Reimbursement
- Funding Opportunities
- Invoice Template
- Donations and Fundraising Policies
Human Resources
- Privileges-and-Responsibilities-of-Membership
- Admin-when-team-members-step-down
- Team-Leader-Selection-Process
- Managing-Editor-Handover
- Checklist-for-Sabbaticals
- New Publications Policy
- Parental-Leave-Policy
Project Management
Project Structure
Board of Trustees