{"id":24097352,"url":"https://github.com/n8willis/git-with-type-design","last_synced_at":"2025-02-27T14:39:21.723Z","repository":{"id":203523034,"uuid":"709705698","full_name":"n8willis/git-with-type-design","owner":"n8willis","description":"Opinionated opinions on how git, GitHub, and related tools can fit into a typeface-design workflow","archived":false,"fork":false,"pushed_at":"2023-10-25T13:13:53.000Z","size":38,"stargazers_count":1,"open_issues_count":0,"forks_count":0,"subscribers_count":2,"default_branch":"draft","last_synced_at":"2025-01-10T13:48:37.464Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/n8willis.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null}},"created_at":"2023-10-25T08:28:52.000Z","updated_at":"2023-10-26T11:58:00.000Z","dependencies_parsed_at":null,"dependency_job_id":"3a957c74-5b75-4906-b0eb-ad03857062df","html_url":"https://github.com/n8willis/git-with-type-design","commit_stats":null,"previous_names":["n8willis/git-with-type-design"],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/n8willis%2Fgit-with-type-design","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/n8willis%2Fgit-with-type-design/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/n8willis%2Fgit-with-type-design/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/n8willis%2Fgit-with-type-design/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/n8willis","download_url":"https://codeload.github.com/n8willis/git-with-type-design/tar.gz/refs/heads/draft","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":241024615,"owners_count":19896270,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2025-01-10T13:44:00.067Z","updated_at":"2025-02-27T14:39:21.700Z","avatar_url":"https://github.com/n8willis.png","language":"Python","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Git with type design\n\n## Opinionated opinions on how git, GitHub, and related tools can fit into a typeface-design workflow\n   \nThis is a document written for people doing type design. It won't tell\nyou anything about how to do type design itself (or, at least, not at\na significant level), but it will explain what value things like git\nand GitHub can bring to a typeface project.\n\nI think it matters to discuss these things in the specific context of\na type-design project, because git and GitHub come from the world of\nprogramming -- and some pretty small niches _within_ programming, for\nthat matter -- which means that a lot of the generalized advice and\n\"howto\"-style material you find if you just search online is going to\nbe focused on programming projects, with little to say that applies to\ndesign projects and a lot that doesn't apply. Hence the choice of\ntitles: it's not \"type design with git\" because you're not using git\nto _do_ type design. You're _doing_ type design, and if git has\nsomething to help you get that done, great: let's see what that\nhelpful stuff is.\n\nI'm also serious about the \"opinionated opinions\" part: this is my\nperspective and I'm sure other people with experience would have\ndifferent things to say. But I think it makes for a more useful\ndocument for one person to write it, intentionally, and to explain the\n\"why\"s -- rather than trying to encapsulate every possible different\napproach and viewpoint, which tends to result in a generic and\nnoncommital list of ingredients. So I am trying to say why I believe\nsome things are more important than other things: others may disagree,\nand you might disagree, too, but at least I'll say why, and hopefully\nthat will connect the advice to the reasons and be more beneficial.\n\nThere are going to be four parts:\n\n- An [overview](overview.md) of what git and GitHub do and why they do\n  it that way. That's important because you only need to care about the parts of\n  these things that matter for your type-design project.\n- A walkthrough of how you use [git\n  itself](chapter-1-git/git-basics.md) in a type-design\n  workflow. That's important because all of the add-ons, GUIs, and web\n  services (including GitHub) are secretly running standard git under\n  the hood, so you'll be a lot better off using them once you know\n  what they're hooked up into themselves.\n- A walkthrough of how projects and repositories work on\n  GitHub. That's useful because there are a lot of features and norms\n  of GitHub that aren't really part of git and, here again, some of\n  them matter for your type-design project and some don't.\n- A walkthrough of the GUI app \"GitHub Desktop\" and some similar\n  graphical tools. I think all of these tools I've seen have awkward\n  UI and UX designs, so they are harder to get used to than they need\n  to be, but yet again, the main goal is to point out how to find and\n  use the parts of the programs that are valuable for your project.\n  \n(although, as I'm writing this, not all of those parts are done\nyet....)\n\nI suggest that you start at the overview page, even if you think it\nisn't something you're interested in. Some of the overview stuff is\ngoing to get referred to in the other parts, just to not repeat things\ntoo many times.\n\nI'm also adding some [resources](resources.md) made by other people, so you can get\nadditional perspectives and have some places to quickly go as you\ncontinue getting git and GitHub integrated into your processes.\n\nIt's also worth keeping in mind that I'm mainly writing this from the\nperspective of a type designer using a Mac, just because that's\nhelpful to the most people. Not much of it is specific to Macs or to a\nparticular font editor, but the examples and phrasing of terms leans\nthat way for convenience.\n\nSo that's it. Happy reading; please get in touch with me if you find a\ntypo or some other mistake, and please please even more get in touch\nwith me if you have a question that isn't covered. This document\nexists solely to be helpful, so let me know how to make it ... more of\nthat.\n\nNathan Willis\nn8willis\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fn8willis%2Fgit-with-type-design","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fn8willis%2Fgit-with-type-design","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fn8willis%2Fgit-with-type-design/lists"}