Addition: Canva processes page

[kierisi]

I've created a section on pyOpenSci's use of Canva as a graphics platform, outlining what it's used for, and the processes surrounding Canva. I chose to place this section under the Organization heading, as it feels process-based, but could also see it going under community, or potentially a new "pyOpenSci Brand" section. Let me know if you'd like me to change the location, and if there is any information related to Canva that I've missed!

[kierisi]

pre-commit.ci autofix

[lwasser]

@kierisi i think this page needs a bit more love

1. let's pull our branding stuff and just focus on using canva

• pyos has a non profit pro plan for canva...

• canva is an online platform that.... what is provides

• something about how canva handles copyright and that we can use all graphics under their copy right.

• most assets in the pyOS ecosystem are created and stored in canva including our brand content

• section about the brand content in canva and what we store there.

• section about organization, folders and sharing folders with the pyos canva team

• note: about stacking too many images in a single file -- hard to find

then finally permissions

• SECTION: who has access to canva
• process for adding someone to canva (and who we add)
• what happens when someone leaves (remove them from canva, etc)

notice that none of the above has anything to do with branding - it is all about how we use canva, what canva is, who has access, how we organize things,

[lwasser]

Suggested change

	pyOpenSci has a Pro subscription to [Canva](https://www.canva.com/), and uses the platform for:
	pyOpenSci has a non-profit Pro subscription to [Canva](https://www.canva.com/), and uses the platform for:

[lwasser]

This paragraph feels like it belongs to a branding page, not a canva processes page.

here we want to describe the process we use in canva for brand. content and to store graphics.

1. we use the brand "section" of canva to store logos, graphics fonts and other content.
2. anything else...

(this statement is true regardless of where our final brand stands!)

[lwasser]

Suggested change

	In addition, all assets should be shared with the pyOpenSci team within Canva. This is accomplished by clicking “Share” in the top right of the screen, then selecting the pyopensci-canva-team and “Can edit” from beneath the collaboration link header.
	All graphics and assets created for pyOpenSci activities and publications should be
	1. stored in a project folder related to the event or theme which the graphic was created.
	Make sure that if you create a new folder, that it is
	shared with the pyOpenSci Canva team.
	To share a folder with the team:
	* click “Share” in the top right of the screen,
	* select the pyopensci-canva-team and
	* select the permissions “Can edit” from beneath the collaboration link header.

A screenshot would be helpful here.

[lwasser]

I think we should have a section here that is about using canva, storing graphics, organizing folders and sharing .

and then a separate section that is about graphic and branding approval. approval is a totally different topic that is not necessarily related to canva explicitly.

For the folder organization - we haven't come up wtih a structure but i've been doing this

1. folders for meeting / presentation graphics (i often take a thematic graphic and customize it for a specific talk)
2. thematic folders associated with programs - peer review, packaging, etc
3. however you've been storing social assets.

I think one of the key pieces to note here is that it's really hard to find nested graphics - so if there are 5 peer review graphics and they are all nested within a single canva graphic that is hard for someone else to find. so we need some language around finding things and organization.

[kierisi]

@lwasser I've made updates based on your feedback. since this page was essentially a re-write, I incorporated your suggestions beyond the initial bulleted list, but rolled them into entirely new text.

[kierisi]

pre-commit.ci autofix

[lwasser]

ok, @kierisi, I made some inline edits to the page.

I:

• removed my name and called out the ED as owner and admin, but any changes or questions about folder structure should be a team discussion in Slack. I like to write all docs as generic "this is how we operate" with a focus on roles not names. The only exception is our code of conduct team, which needs to specify people.
• clarified a few things
• added a TODO about adding a link to the off-boarding page once we have that in place.

please

• give this one last read,
• make suggestions as you see fit

I'll then approve, run the pre-commit bot, and merge.

[lwasser]

one last review requested by you @kierisi and then i'll merge

[kierisi]

pre-commit.ci autofix

[kierisi]

looks good to me!

apologies for running the pre-commit bot. I didn't see that in your message until after I had run it. I had assumed I had forgotten to do it when I saw that it hadn't passed the check.

[lwasser]

looks good to me!

Apologies for running the pre-commit bot. I didn't see that in your message until after I had run it. I had assumed I had forgotten to do it when I saw that it hadn't passed the check.

Thanks, @kierisi. Don't apologize! I only mentioned that because if we had more edits, we'd need to run it again anyway. but since you are good with it - you saved me from calling the bot again! I'll merge this now.