-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
added: branding content #95
Open
kierisi
wants to merge
7
commits into
pyOpenSci:main
Choose a base branch
from
kierisi:branding-content
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 5 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
93d2ce1
logos, colors, and fonts
kierisi dbdb465
DEIA language added
kierisi 9add983
updated index
kierisi 8b6693a
'[pre-commit.ci 🤖] Apply code format tools to PR'
pre-commit-ci[bot] b2ccb78
corrected email address
kierisi 3900c68
incorporated review feedback
kierisi 7fc9008
'[pre-commit.ci 🤖] Apply code format tools to PR'
pre-commit-ci[bot] File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
# The pyOpenSci brand | ||
|
||
The pyOpenSci brand is playful, curious, and integrates a calm color palette with illustrations and abstract primary shapes that are soft, round, and flowing. | ||
|
||
## Logos, colors, and fonts | ||
|
||
pyOpenSci stores its logos, brand colors, and font information in [Canva](https://www.pyopensci.org/handbook/organization/canva.html). We also store logos in a [publicly-shared Drive folder](https://drive.google.com/drive/folders/1m4cG3JLonP0mQ8y3pBaULMulpja-As0l?usp=drive_link). | ||
|
||
### pyOpenSci logos | ||
|
||
pyOpenSci uses three variations on a floral logo: | ||
* pyOpenSci written horizontally, with a flower "blooming" over the "O" in pyOpenSci | ||
* a four- or five-petaled flower with pyOpenSci abbreviated as pyOS | ||
* a five-petaled flower icon | ||
|
||
```{figure} /images/canva-images/pyos-flowers.png | ||
:alt: A series of four purple flower logos on grey backgrounds arranged in a single row. At the top of the collection is the text 'Logos', and underneath it is the text 'Assets(4).' From left to right, the logos include a dark purple logo with three petals above the word pyOpenSci. The 'O' in pyOpenSci is the center of the flower. The second image from the left is a four-petaled flower, with the text py and then an S in the shape of a snake inside an O. The text comes in from the left. The flower petals surround the O. The next image is identical to the second from the left, but is in a lighter shade of purple. The final image is the pyOpenSci flower, which has five petals and an open center. This logo is in light purple. | ||
|
||
A screenshot of the pyOpenSci flower logos in Canva. | ||
``` | ||
|
||
### pyOpenSci color palette | ||
|
||
pyOpenSci's main color is purple, with the additional pink, green, and cream colors to be used as accents. | ||
|
||
```{figure} /images/canva-images/pyos-color-palette.png | ||
:alt: This is a series of color samples comprising the pyOpenSci color palette, which includes six equally-sized circles arranged in a single row. At the top of the image is the text 'Color palette.' The circles contain the following colors, with the corresponding hex code written beneath them: dark purple #33205C, medium purple #735FAB, light purple #BAB3D4, cream #F6F0DC, pink #BB92B0, and green #81C0AA. | ||
|
||
A screenshot of the pyOpenSci color palette in Canva. | ||
``` | ||
|
||
### pyOpenSci fonts | ||
|
||
pyOpenSci uses [Itim](https://fonts.google.com/specimen/Itim) and [Poppins](https://fonts.google.com/specimen/Poppins?query=poppins) as its fonts. Itim is most commonly used as a header, while Poppins is used for the body of a text. Poppins is available in multiple weights, and at this time pyOpenSci uses the most appropriate weight for accessibility and readability, which varies by use case. Both of these fonts are available via [Google Fonts](https://fonts.google.com/). | ||
|
||
## Diversity, Equity, Inclusion, and Accessibility | ||
|
||
pyOpenSci builds diverse community that supports free and open Python tools for processing scientific data. pyOpenSci accomplishes this through a combination of community building, mentorship, peer review of software and education and outreach. We are building the pyOpenSci community in a way that promotes fairness and justice for all, with a particular focus on supporting those from traditionally marginalized / underrepresented groups. We want every member of our community to thrive; we want to make a positive impact on our community members’ work and on the work of others. You can learn more about how this is put into action by reading through our [Code of Conduct](https://www.pyopensci.org/handbook/CODE_OF_CONDUCT.html). | ||
|
||
### DEIA in [Peer Review](https://www.pyopensci.org/about-peer-review/index.html) | ||
|
||
pyOpenSci recruits and supports editors and reviewers from different backgrounds and gender-identities in each review that we perform. | ||
|
||
To break this down into concrete actions: | ||
* We actively recruit individuals from underrepresented backgrounds | ||
* We support people through individualized mentorship | ||
* When possible, we elevate people into leadership roles | ||
|
||
If you have any questions about pyOpenSci's DEIA efforts, please email us at: [[email protected]](mailto:[email protected]). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kierisi Before I review this in its entirety, I'm curious—why is DEIA on a branding page? I could definitely see accessibility fitting in here as a statement that links to DEIA in our organizational values. I think you have some nice content here, but I don't think that the full DEIA statement belongs here. Rather, I'd put it in our org values and make a focused statement here around accessibility as it relates to font and alt tags. I haven't looked at the guidebook as a whole in a while, but I'm curious what your thoughts are on where this belongs in the handbook.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lwasser this is where it was listed in the google doc version of the handbook. happy to move it to organizational values if you'd prefer!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kierisi i do understand that. That is an old document and things have been moved around a lot. It would be nice for you to consider where content belongs as you work on this as a part of this task. Please answer my question above.
Do you think it makes sense in that section? If you don't, I'd greatly appreciate your considering the content relevance on this page and suggesting it go somewhere else as a part of the task of creating this handbook section. I do think a note on accessibility makes sense here. Do you agree?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it makes sense to me that DEIA language would go into branding, because it is a core component of our brand identity, which is why I didn't make suggestions for it to go elsewhere.
I do think it makes sense to add more context on accessibility as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is reasonable. Please add more details about accessibility and how our brand addresses that
some examples: alt tags, responsive design, colors, fonts etc etc. Link out to other relevant sections as it makes sense - for example alt tags could link to the website section on adding figures that you worked on.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
addressed in latest commit!