PT technical onboarding

mdlincoln commented 4 years ago

This is a tracking ticket for technical tasks related to starting the PT team.

[x] Create new defaults in _config.yml
[x] Add new language line to all snippets
[x] Copy core pages to the new language directory
[x] Push core pages to gh-pages branch so language team can begin translation
[x] Create language logo and set theme color (#1822)
[x] Add the new language to the RSS feed XML
[x] Enable full text search stemming support
[x] Add the new team to this loop once editors have been added to the team's data files.
[x] Make pages public

acrymble commented 4 years ago

In case it helps the brand guidelines on the wiki give the logo fonts (https://github.com/programminghistorian/jekyll/wiki/Brand-Guidelines). I believe I used a colour-palatte generater in the past to get colours that worked well together, but I can't remember which one.

amsichani commented 4 years ago

Thanks for this @mdlincoln! I think its handy to have the technical tasks related to start a new language publication as a distinct wiki page -- we will link to this tutorial from the main wiki page .

JoshuaGOB commented 4 years ago

Thank you @mdlincoln I really needed to see this and the technical tutorial to get a sense of what was going on behind the scenes.

jenniferisasi commented 4 years ago

@ZoeLeBlanc I think Matt missed a step in this guide. We have to manually add the chunk about the editorial team in Portuguese in this loop right? https://github.com/programminghistorian/jekyll/blob/gh-pages/_includes/project-team-loop.html

acrymble commented 4 years ago

Yes @jenniferisasi that can just be cut and pasted and amended in place.

walshbr commented 4 years ago

I added that to the wiki template for this issue @jenniferisasi and updated Matt's checklist above.

acrymble commented 4 years ago

@ZoeLeBlanc I most recently worked on the /project-team page so I think I can do the changes to add the Portuguese team without screwing anything up. Would you like me to do that or will that get in the way of your processes? We already have Daniel in there so there is content that would and should appear.

ZoeLeBlanc commented 4 years ago

Go ahead and make the changes to project-team page @acrymble and I'll take a look at what's left to be done once you do your PR. Thanks!

Seems like it's just the full-text and making pages public though according to the to-do list, which should be easy.

drjwbaker commented 4 years ago

Per https://github.com/programminghistorian/project-and-business-archive/blob/master/project/2020/2020-04_Sussex-DOI-MOU/2020-05-18_ProgHist%20MOU%20w%20University%20of%20Sussex.docx we need to ask our DOI provider if they are happy to provide DOIs for a new publication, in this case the PT edition.

Has this happened? If not, two actions:

@programminghistorian/technical-team please update https://github.com/programminghistorian/jekyll/wiki/Technical-Tutorial-on-Setting-Up-a-New-Language to include this task as part of the technical process for creating a new language publication.
@JoshuaGOB @acrymble @DanielAlvesLABDH I'm out of the loop in the status of the PT work (I think you are the main people involved), but - when you are ready - someone needs to ask me to ask Sussex re providing DOIs for the PT publication.

DanielAlvesLABDH commented 4 years ago

@drjwbaker we are still in the process of translating the platform to Portuguese. I guess the DOI will apply only to the lessons, correct?

walshbr commented 4 years ago

@drjwbaker I can add that to the Wiki checklist, but I don't exactly know what the language would entail. As far as I know that hasn't happened. Something like…

"Get @drjwbaker to check with the DOI provider that they are happy provide DOIs for a new publication." Or is that meant to be @ZoeLeBlanc as technical lead? And what happens if they say no? Could you offer some language for what that checklist item should be? I haven't been involved with the DOI process so I wouldn't know what needs to happen at that stage.

drjwbaker commented 4 years ago

That is fine. I have at the relationship. Though technically, I'm working on behalf of the Ltd (DOIs is a service the Ltd provides to the publications https://github.com/programminghistorian/jekyll/wiki/ProgHist-services-to-Publications#services-provided-in-kind)

If they say no, the new publication runs without DOIs until the Ltd finds a solution.

walshbr commented 4 years ago

Cool. Added it to the wiki @drjwbaker

drjwbaker commented 4 years ago

@drjwbaker we are still in the process of translating the platform to Portuguese. I guess the DOI will apply only to the lessons, correct?

@DanielAlvesLABDH Correct. Perhaps once we have an ISSN for the PT publication (https://github.com/programminghistorian/jekyll/commit/8a7b7fe2381c8adf7cf1591ff1e1de79b7369197#commitcomment-42033910) contact me and I will speak to our DOI provider?

DanielAlvesLABDH commented 4 years ago

Will do that @drjwbaker

ZoeLeBlanc commented 4 years ago

Full text search stemming is now live. Nothing to see until we make the pages public, which I think is waiting on more translations and merging of ph_authors.yml

JoshuaGOB commented 3 years ago

@drjwbaker we are still in the process of translating the platform to Portuguese. I guess the DOI will apply only to the lessons, correct?

@DanielAlvesLABDH Correct. Perhaps once we have an ISSN for the PT publication (8a7b7fe#commitcomment-42033910) contact me and I will speak to our DOI provider?

Hi @drjwbaker This has come up again and I think the question is about when the DOI request should happen. Would this be once we have a firm deadline for publication or after a set of lessons are in review? Are there any other factors?