-
Notifications
You must be signed in to change notification settings - Fork 228
Image Naming Convention
An image naming convention has been established for the following reasons:
- Images in ph-submissions Preview will always display
- Managing Editors will not be confused/make mistakes when they are identifying which images to move over to Jekyll
- Lesson Maintenance will be simpler because images will be named consistently
Here's an example for an original Spanish lesson:
es-or-lesson-image-name-01.png
es-or-lesson-image-name-02.png
es-or-lesson-image-name-03.png
es-or-lesson-image-name-04.png
And for a Portuguese translation of that lesson which uses all new images:
pt-tr-lesson-image-name-01.png
pt-tr-lesson-image-name-02.png
pt-tr-lesson-image-name-03.png
pt-tr-lesson-image-name-04.png
For a Portuguese translation which creates some new images but keeps others as original:
es-or-lesson-image-name-01.png
es-or-lesson-image-name-02.png
pt-tr-lesson-image-name-02.png
es-or-lesson-image-name-03.png
es-or-lesson-image-name-04.png
pt-tr-lesson-image-name-04.png
If you were the Portuguese Managing Editor preparing to move the files (above) over to Jekyll for publication, you would only need to move those with the pt-tr
prefix.
--
Here's an example of how that file list might look if the lesson is later translated into French. Again, this translation creates some new images but keeps others as they were in the Spanish original:
es-or-lesson-image-name-01.png
es-or-lesson-image-name-02.png
pt-tr-lesson-image-name-02.png
fr-tr-lesson-image-name-02.png
es-or-lesson-image-name-03.png
fr-tr-lesson-image-name-03.png
es-or-lesson-image-name-04.png
pt-tr-lesson-image-name-04.png
fr-tr-lesson-image-name-04.png
If you were the French Managing Editor preparing to move the files (above) over to Jekyll for publication, you would only need to move those with the fr-tr
prefix.
--
- 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