Skip to content

Adds fonts folder & Work Sans#5

Open
Shrinks99 wants to merge 2 commits intomasterfrom
fonts-folder
Open

Adds fonts folder & Work Sans#5
Shrinks99 wants to merge 2 commits intomasterfrom
fonts-folder

Conversation

@Shrinks99
Copy link
Copy Markdown
Member

Fonts are important! This folder gives org members a place to go to get all open source / free fonts that we use.

Work Sans is licensed under the SIL Open Font License and as such they are cool with us redistributing it. The readme has been updated with information regarding fonts in this repo.

Fonts are important to design!  This folder gives org members a place to go to get all open source / free fonts that we use.

Work Sans is licensed under the SIL Open Font License and as such they are cool with us redistributing it.  Licenses should be included in their respective font folder.
Also a few punctuation fixes and inclusion of Work Sans in the credits.
@Shrinks99 Shrinks99 added the Approval Requested Request for approval, otherwise ready to go label Dec 15, 2018
Copy link
Copy Markdown
Member

@garrying garrying left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤔Stray thought: Might be helpful to describe how a project folder could be structured—having a /fonts folder per-project might be helpful for projects that use other fonts.

@Shrinks99
Copy link
Copy Markdown
Member Author

That's not a bad idea @garrying, my thought with a single folder is that it would reduce the duplication of files. Having a way to reference what fonts are needed in a given project is valuable though, perhaps a readme?

@dcwalk
Copy link
Copy Markdown
Contributor

dcwalk commented Dec 21, 2018

My two cents: I agree about a per-folder fonts subfolder... often preferred to have all needed files contained within a project folder to minimize not realizing there is a missing vendor/src file

@benhylau
Copy link
Copy Markdown
Member

Agree with @dcwalk about depending on things only inside a folder if possible. Once you start depending on ../ it is harder to remix things modularly.

This of course has issue of duplication which usually has two drawbacks:

  1. Total file size becomes larger
  2. If we update a version of the asset it needs to be updated in multiple places

This is a design repo, I don't really care about 1. As for 2, we actually want updates to apply modularly, instead of having to update all assets together. So given context, I think per-folder fonts is a better choice here.

Copy link
Copy Markdown
Member

@benhylau benhylau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please do per-folder fonts. I think it's important we start that structure before it gets out of control :)

@Shrinks99
Copy link
Copy Markdown
Member Author

General consensus seems to be per-folder fonts. I'll make the changes!

@dcwalk dcwalk removed their request for review February 3, 2021 17:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Approval Requested Request for approval, otherwise ready to go

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants