-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
390 lines (312 loc) · 26.8 KB
/
Copy pathindex.html
File metadata and controls
390 lines (312 loc) · 26.8 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="description" content="A plain-English guide to GitHub for non-programmers. Count the names after github.com to tell an organisation page from a repo. Look for Releases to find the download. If a project overwhelms you, check whether it has a normal website and use that instead.">
<meta property="og:title" content="GitHub without the panic">
<meta property="og:description" content="Why GitHub feels impossible when you are not a programmer, and the three things that fix it: identify the page type, find Releases, or go to the project's real website.">
<title>GitHub without the panic — v3.3</title>
<style>
:root{
--bg:#0f1115; --card:#171a21; --card2:#1d212a; --ink:#e8eaf0; --dim:#9aa1b0;
--line:#2a2f3a; --accent:#7dd3a0; --warn:#ffb454; --bad:#ff7b72; --link:#79b8ff;
}
*{box-sizing:border-box;min-width:0}
html,body{overflow-x:hidden;max-width:100%}
img,table,pre,.anat{max-width:100%}
html{scroll-behavior:smooth}
body{margin:0;background:var(--bg);color:var(--ink);
font:16px/1.65 -apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,sans-serif;
padding:0 0 60px}
.wrap{max-width:800px;margin:0 auto;padding:0 20px}
nav{position:sticky;top:0;z-index:9;background:rgba(15,17,21,.94);
backdrop-filter:blur(8px);border-bottom:1px solid var(--line);padding:9px 0}
nav .wrap{display:flex;gap:14px;flex-wrap:wrap;font-size:.82rem}
nav a{color:var(--dim);text-decoration:none;white-space:nowrap}
nav a:hover{color:var(--accent)}
header{padding:44px 0 26px;border-bottom:1px solid var(--line);margin-bottom:30px}
h1{font-size:1.9rem;line-height:1.25;margin:0 0 12px;letter-spacing:-.02em}
.sub{color:var(--dim);font-size:1.02rem;margin:0}
h2{font-size:1.32rem;margin:48px 0 14px;letter-spacing:-.01em;scroll-margin-top:56px}
h2 .n{color:var(--accent);font-variant-numeric:tabular-nums;margin-right:10px}
h3{font-size:1.02rem;margin:26px 0 8px;color:var(--accent)}
p{margin:0 0 14px}
.card{background:var(--card);border:1px solid var(--line);border-radius:12px;
padding:20px 22px;margin:18px 0}
.big{background:linear-gradient(180deg,#1b2a22,#171a21);border-color:#2f5a44}
.ex{background:linear-gradient(180deg,#1a2130,#171a21);border-color:#31435f}
.quiet{color:var(--dim);font-size:.94rem}
code{background:var(--card2);padding:2px 7px;border-radius:5px;font-size:.9em;
font-family:ui-monospace,SFMono-Regular,Menlo,monospace;color:#c8d3e8;
word-break:break-word}
.btn{display:inline-block;background:#238636;color:#fff;padding:3px 11px;
border-radius:6px;font-size:.85rem;font-weight:600}
.step{display:flex;gap:15px;margin:0 0 18px;align-items:flex-start}
.num{flex:0 0 29px;height:29px;border-radius:50%;background:var(--accent);color:#0f1115;
display:flex;align-items:center;justify-content:center;font-weight:700;font-size:.9rem}
.step > div:last-child{flex:1;padding-top:2px}
table{width:100%;border-collapse:collapse;margin:14px 0;font-size:.94rem}
th,td{text-align:left;padding:10px 12px;border-bottom:1px solid var(--line);vertical-align:top}
th{color:var(--dim);font-weight:600;font-size:.82rem;text-transform:uppercase;letter-spacing:.04em}
td:first-child{white-space:nowrap;font-family:ui-monospace,monospace;color:#c8d3e8}
.flag{border-left:3px solid var(--warn);padding-left:16px;margin:18px 0;color:#f0d9b5}
.stop{border-left:3px solid var(--bad);padding-left:16px;margin:18px 0;color:#ffc9c4}
.good{border-left:3px solid var(--accent);padding-left:16px;margin:18px 0;color:#c9e8d5}
.yes{color:var(--accent);font-weight:600}
.no{color:var(--bad);font-weight:600}
ul{margin:0 0 14px;padding-left:22px}
li{margin-bottom:7px}
.anat{background:var(--card2);border:1px solid var(--line);border-radius:10px;
padding:15px;font-family:ui-monospace,monospace;font-size:.8rem;line-height:1.85;
overflow-x:auto;white-space:pre;color:var(--dim)}
.anat b{color:var(--ink);font-weight:600}
.anat-m{display:none}
.anat-m li{margin-bottom:10px}
.anat .hl{color:var(--accent);font-weight:600}
footer{margin-top:52px;padding-top:22px;border-top:1px solid var(--line);
color:var(--dim);font-size:.88rem}
a{color:var(--link);overflow-wrap:anywhere;word-break:break-word}
.card p,.card{overflow-wrap:anywhere}
.ver{display:inline-block;font-size:.72rem;background:var(--card2);color:var(--dim);
padding:2px 9px;border-radius:20px;border:1px solid var(--line);margin-left:8px;
vertical-align:middle}
@media(max-width:560px){
h1{font-size:1.5rem}
.wrap{padding:0 15px}
.anat{font-size:.6rem;padding:10px}
nav .wrap{font-size:.76rem;gap:10px}
td:first-child{white-space:normal}
.anat{display:none}
.anat-m{display:block}
th,td{padding:9px 8px;font-size:.9rem}
.card{padding:16px 15px}
table{display:block;overflow-x:auto}
}
</style>
</head>
<body>
<nav><div class="wrap">
<a href="#s1">1 What is this</a>
<a href="#s2">2 Which page am I on</a>
<a href="#s3">3 Reading a repo</a>
<a href="#s4">4 What to click</a>
<a href="#s5">5 Which file</a>
<a href="#s6">6 Eg: a gist</a>
<a href="#s7">7 Eg: an org page</a>
<a href="#s8">8 Eg: no Releases</a>
<a href="#s9">9 No Releases?</a>
<a href="#s10">10 Safety</a>
<a href="#s11">11 Glossary</a>
<a href="#s12">12 Git itself</a>
</div></nav>
<div class="wrap">
<header>
<h1>GitHub without the panic <span class="ver">v3.3</span></h1>
<p class="sub">A short guide for people who keep landing on GitHub pages and quietly backing away. You are not missing a brain cell — the site is built for programmers and nobody bothered to make a version for everyone else.</p>
</header>
<div class="card big">
<p style="margin:0"><strong>The whole guide in one line:</strong> look for a section called <strong>Releases</strong> on the right-hand side. If it's there, that's your download. If it isn't, the page probably isn't meant for you, and that's fine.</p>
</div>
<div class="card">
<h3 style="margin-top:0">In short</h3>
<ol style="margin:0;padding-left:20px">
<li><strong>Work out which page you are on first.</strong> Count the names after github.com: one name is an organisation (a shelf of many projects, nothing to download), two names is a repo (one project, this is the useful page).</li>
<li><strong>On a repo, look for Releases</strong> in the right-hand column. That is where the finished, downloadable files live. The green Code button is not it.</li>
<li><strong>If the project has a real website, use that instead.</strong> Organisations link theirs at the top left. The website is the front door; GitHub is the workshop. This one habit solves most of it.</li>
<li><strong>No Releases section usually means it is not meant for you</strong> — and walking away is a perfectly good outcome.</li>
<li><strong>GitHub is not the App Store.</strong> Anyone can upload anything, there is no review. Check the star count and who published it before running a file.</li>
<li><strong>For a one-off job, skip GitHub entirely</strong> and ask an AI to do the task directly. GitHub is worth it when you need the same thing every week.</li>
</ol>
</div>
<h2 id="s1"><span class="n">1</span>What is this place?</h2>
<p>GitHub is where people keep the raw ingredients of software. Not the finished dish — the ingredients, plus the recipe, plus notes between the cooks.</p>
<p>That's why it feels wrong. You arrived expecting a shop, and you're standing in a kitchen. Nothing is labelled "buy" or "install" because most visitors are chefs who came for the ingredients.</p>
<p>Three words, then you can forget the rest:</p>
<ul>
<li><strong>Repo</strong> (repository) — one project. One folder of stuff. That's the page you land on.</li>
<li><strong>Gist</strong> — a single file or snippet. Simpler than a repo. No folders, no furniture.</li>
<li><strong>Release</strong> — a finished, packaged version someone made ready to use. <em>This is the bit you want.</em></li>
</ul>
<h2 id="s2"><span class="n">2</span>Which kind of page am I on?</h2>
<p>This is the step everyone skips, and it is the reason people give up. There are three different kinds of GitHub page and they look nothing alike. Before anything else, work out which one you have landed on.</p>
<p><strong>Count the names in the address after github.com.</strong> That is the whole test.</p>
<table>
<tr><th>Address looks like</th><th>You are on</th><th>What to do</th></tr>
<tr><td>github.com/<b>revanced</b></td><td><strong>Organisation</strong> — a shelf of many projects</td><td>Pick a project from the list. Nothing here is downloadable.</td></tr>
<tr><td>github.com/<b>revanced/revanced-manager</b></td><td><strong>Repo</strong> — one project</td><td>Look for Releases. This is the useful page.</td></tr>
<tr><td>gist.github.com/<b>someone/a1b2c3...</b></td><td><strong>Gist</strong> — a single file</td><td>Hit Raw and copy.</td></tr>
</table>
<div class="good">
One name after github.com = a shelf. Two names = a book. If you feel lost and there is only one name in the address, that is why — you are standing in front of a shelf looking for something to read.
</div>
<h2 id="s3"><span class="n">3</span>Reading a repo page</h2>
<p>Every repo has the same furniture. Once you can name four things, the panic mostly goes.</p>
<div class="anat">┌──────────────────────────────────────────────────────┐
│ <b>someone / project-name</b> ☆ <b>12.4k</b> stars │ <span class="hl">← 1</span>
├───────────────────────────────────┬──────────────────┤
│ │ │
│ a list of files and folders │ <b>About</b> │
│ (ignore this entirely) │ one-line summary│
│ │ │
│ ──────────────────────────── │ <b>Releases</b> <span class="hl">← 2</span> │
│ │ v3.1 Latest │
│ <b>README</b> <span class="hl">← 3</span> │ │
│ A big block of text. │ <b>Contributors</b> │
│ This is the instructions. │ │
│ Written by whoever made it. │ │
│ │ │
└───────────────────────────────────┴──────────────────┘</div>
<div class="anat-m">
<p class="quiet" style="margin:0 0 10px">Every repo page has these four things:</p>
<ol style="padding-left:20px;margin:0">
<li><strong>Top left:</strong> <code>whoever-made-it / project-name</code>, and a star count on the right.</li>
<li><strong>Right-hand column:</strong> About, then <strong>Releases</strong>. Releases is the one that matters.</li>
<li><strong>Middle:</strong> a list of files and folders. Ignore it completely.</li>
<li><strong>Below that:</strong> the <strong>README</strong> — a big block of text. These are the instructions.</li>
</ol>
</div>
<h3>1. The name and the stars</h3>
<p>Top left is <code>whoever-made-it / what-it-is</code>. Top right, a star count — rough popularity. 12,000 stars means many people use it and it probably works. 8 stars means someone's weekend project. Stars aren't a guarantee, but they're the fastest sanity check you have.</p>
<h3>2. Releases — the important one</h3>
<p>Right-hand column, usually a third of the way down. If it's there, click it. That page lists finished versions, each with real downloadable files at the bottom under a heading called <strong>Assets</strong>.</p>
<p class="quiet">Shortcut: add <code>/releases</code> to the end of any repo's address and press Enter.</p>
<h3>3. The README</h3>
<p>Scroll down the main page and there's a wall of text. That's the README — instructions written by whoever built the thing. It's the closest GitHub gets to a manual, and it usually says in the first paragraph whether this is for normal humans or for developers.</p>
<h3>4. The green Code button</h3>
<p><span class="btn">Code ▾</span> → <strong>Download ZIP</strong>. The button everyone hunts for, and the honest truth: <strong>it's almost never what you want.</strong> It downloads raw ingredients, not the finished thing. If you've got a ZIP full of files you don't recognise, you came this way by mistake.</p>
<h2 id="s4"><span class="n">4</span>What to actually click</h2>
<div class="step"><div class="num">1</div><div>
<strong>Look for Releases</strong> in the right column. Not there? Add <code>/releases</code> to the address bar. Still nothing? Section 9.
</div></div>
<div class="step"><div class="num">2</div><div>
<strong>Open the newest one</strong> — tagged <em>Latest</em>. Skip anything marked <em>pre-release</em> or <em>beta</em>; those are test versions.
</div></div>
<div class="step"><div class="num">3</div><div>
<strong>Scroll to Assets</strong> at the bottom and pick the file that matches your device.
</div></div>
<div class="step"><div class="num">4</div><div>
<strong>Read the release notes</strong> above the files. Two lines, usually. Often says exactly which file to pick.
</div></div>
<h2 id="s5"><span class="n">5</span>Which file is mine?</h2>
<table>
<tr><th>Ends in</th><th>What it is</th></tr>
<tr><td>.exe / .msi</td><td>Windows program. Double-click to install. <span class="yes">Usually what you want on a laptop.</span></td></tr>
<tr><td>.dmg / .pkg</td><td>Mac program. Same idea.</td></tr>
<tr><td>.bat</td><td>A Windows shortcut file. Double-click and it runs a sequence of steps for you. <span class="yes">Friendly sign</span> — it means the author was thinking of non-programmers.</td></tr>
<tr><td>.apk</td><td>Android app installed outside the Play Store. <span class="no">Read section 10 first.</span></td></tr>
<tr><td>.zip</td><td>A folder squashed into one file. Right-click → Extract All, then look inside.</td></tr>
<tr><td>Source code (zip)</td><td><span class="no">Not for you.</span> Raw ingredients. Appears on every release; skip it.</td></tr>
<tr><td>.py</td><td>A Python script. Needs Python installed. Section 9.</td></tr>
<tr><td>.md</td><td>Just a text document. Safe to open, it's only words.</td></tr>
</table>
<p class="quiet">If a release offers six files named <code>x64</code>, <code>arm64</code>, <code>win-setup</code> — on a normal Windows laptop you almost always want the one with <strong>x64</strong> and <strong>setup</strong> or <strong>installer</strong> in the name.</p>
<h2 id="s6"><span class="n">6</span>Worked example: a gist</h2>
<div class="card ex">
<p style="margin:0 0 10px"><strong>Try it:</strong> <a href="https://gist.github.com/iteachc/f61c9c1496fc04d39e9e8a34938a18c5">gist.github.com/iteachc/f61c9c14…</a></p>
<p class="quiet" style="margin:0">A guide to spotting fake profile photos on matrimonial sites.</p>
</div>
<p>Notice what <em>isn't</em> there. No file tree, no branches, no Releases, no green Code button. A gist is just <strong>one file with a nice address</strong>. Think of it as a public note rather than a project.</p>
<p>Things to try on it:</p>
<ul>
<li><strong>Raw</strong> (small button, top right of the file) — strips away all GitHub furniture and shows the plain text. This is the version to copy.</li>
<li><strong>Download ZIP</strong> is up there too, and here it's actually harmless, because a gist contains only the file itself.</li>
<li><strong>Revisions</strong> — every edit ever made, with dates. Nothing is lost when someone changes a gist. That's git quietly doing its thing underneath.</li>
</ul>
<div class="good">
<strong>The rule:</strong> gist = one note, copy it and go. Repo = a whole project, look for Releases. If you can tell those two apart on sight, you've solved most of GitHub.
</div>
<h2 id="s7"><span class="n">7</span>Worked example: an organisation page</h2>
<div class="card ex">
<p style="margin:0 0 10px"><strong>The classic trap:</strong> <a href="https://github.com/revanced">github.com/revanced</a></p>
<p class="quiet" style="margin:0">One name after github.com. So: a shelf, not a book.</p>
</div>
<p>This is where most people bounce, and it is not their fault. No README with instructions, no Releases box, no green Code button, no file list. Instead: a logo, a follower count, a wall of contributor avatars, donation buttons, and a long list of project names. Nothing says "start here".</p>
<p>What you are looking at is a <strong>group</strong> — the people behind a project — with 50 separate repositories underneath. The thing you actually want is one of those repositories.</p>
<h3>How to find the right one</h3>
<p>Look at the <strong>Pinned</strong> section near the top. Organisations pin the repos that matter, and each has a one-line description. Read the descriptions, not the names:</p>
<table>
<tr><td>revanced-manager</td><td>"Application to use ReVanced on <strong>Android</strong>" — 28.6k stars. <span class="yes">This is the app.</span></td></tr>
<tr><td>revanced-cli</td><td>"<strong>Command-line</strong> application" — for people who type commands.</td></tr>
<tr><td>revanced-patcher</td><td>"Patcher <strong>used to</strong> patch applications" — an engine other programs use.</td></tr>
<tr><td>revanced-patches</td><td>Ingredients, consumed by the tools above.</td></tr>
<tr><td>revanced-documentation</td><td>The written docs.</td></tr>
</table>
<div class="good">
<strong>Suffix decoder.</strong> Names ending in <code>-cli</code>, <code>-api</code>, <code>-library</code>, <code>-core</code>, <code>-patcher</code>, <code>-sdk</code> or <code>-template</code> are parts for builders. The one you want usually has a plain human name, the most stars, and a description containing a word like <em>app</em>, <em>application</em>, <em>manager</em> or <em>desktop</em>.
</div>
<h3>Try this before anything else: find the project's real website</h3>
<p><strong>The fastest fix for an overwhelming GitHub page is to leave it.</strong> Look at the top left of an organisation page: serious projects list a <strong>real website</strong> — for this one, <code>revanced.app</code>. There is usually also a <strong>Verified</strong> badge confirming the organisation genuinely controls that domain.</p>
<p><strong>Go to the website instead.</strong> It will have a normal download page written for normal people, with the right file for your device and instructions that assume nothing. The GitHub page is where the builders work; the website is the front door.</p>
<p class="quiet">This is the single most useful habit in this guide: when a GitHub page overwhelms you, check whether the project has an ordinary website, and use that.</p>
<div class="flag">
The verified badge and the follower count also tell you that you are on the real organisation and not a copycat — worth checking before downloading anything.
</div>
<h2 id="s8"><span class="n">8</span>Worked example: a repo with no Releases</h2>
<div class="card ex">
<p style="margin:0 0 10px"><strong>Try it:</strong> <a href="https://github.com/iteachc/Prabhupada-folio-search">github.com/iteachc/<wbr>Prabhupada-folio-search</a></p>
<p class="quiet" style="margin:0">An offline search tool for a personal library of texts.</p>
</div>
<p>Run the checklist on it and see what the page tells you:</p>
<table>
<tr><td>Stars</td><td><strong>0</strong> — brand new and personal, not famous and not necessarily bad. It just means popularity tells you nothing here, so your trust has to come from knowing who made it.</td></tr>
<tr><td>Releases</td><td><strong>Empty.</strong> Nobody has packaged this into a click-to-run app. Section 9 explains why, and it's a good reason.</td></tr>
<tr><td>README</td><td>Present, long, with a <em>Quick start</em> section. <span class="yes">This is the real instruction manual</span> — and on a repo like this, the README <em>is</em> the release.</td></tr>
<tr><td>File list</td><td>Some <code>.py</code> files, two <code>.bat</code> files, a <code>corpus</code> folder, a LICENSE.</td></tr>
</table>
<h3>What the file list is quietly telling you</h3>
<p>Those two <code>.bat</code> files — <code>Start Folio Search.bat</code> and <code>Build Semantic Index.bat</code> — are the tell. Someone deliberately made double-clickable shortcuts so you wouldn't have to type commands. That's an author thinking about non-programmers.</p>
<p>But the README also says <code>pip install fastembed numpy</code>, which means Python has to exist on the machine first. So the honest read of this page is: <strong>friendly, but it needs a one-time setup that assumes you'll follow written instructions.</strong> Not a double-click-and-go app.</p>
<div class="good">
<strong>The skill worth having</strong> isn't installing this. It's being able to look at a page for fifteen seconds and say "this needs Python, so it's a project-not-a-product" — and then decide whether you care enough. That judgement is the whole thing.
</div>
<h2 id="s9"><span class="n">9</span>When there's no Releases section</h2>
<p>It means nobody has packaged it. Sometimes that's laziness. Often it's because the thing <em>can't</em> be packaged — the search tool above needs your own texts and your own machine, so there's no single file anyone could hand you that would work.</p>
<p>Three options, and two are good:</p>
<ul>
<li><strong>Walk away.</strong> Genuinely fine. There's often a friendlier alternative one search away.</li>
<li><strong>Ask an AI to read it for you.</strong> Paste the link into ChatGPT or Claude: <em>"What does this do, is there a ready-made download, and is there an easier alternative for a non-programmer on Windows?"</em> It reads the README and answers in ten seconds. You can also ask it to walk you through the setup one step at a time and tell it when something doesn't look like the screenshot in your head.</li>
<li><strong>Do the setup.</strong> Worth it only if you specifically want this specific thing.</li>
</ul>
<div class="card">
<h3 style="margin-top:0">The shortcut nobody mentions</h3>
<p style="margin-bottom:0">If you're on GitHub hunting for a tool to do a <em>one-off job</em> — clean a messy spreadsheet, pull tables out of a PDF, rename 200 files, reconcile two lists — you're often on the wrong website entirely. Describe the job to Claude or ChatGPT and attach the file. For one-offs that's usually faster than finding, downloading, installing and learning somebody's tool. GitHub earns its keep when you need the same thing done every week, forever.</p>
</div>
<h2 id="s10"><span class="n">10</span>Before you run anything</h2>
<p>This matters more than the rest. Anyone can put anything on GitHub. No approval process, no review, no store policy. <strong>It is not the App Store.</strong></p>
<div class="flag">
<strong>Check you're on the real page.</strong> Popular projects get cloned by people who add nasty extras. Compare the star count against the project's official site or Wikipedia. Ten stars on a "famous" tool means you're on a fake.
</div>
<div class="flag">
<strong>Prefer Releases over random links.</strong> Files under the official Releases page were uploaded by the project owners. A download link buried in a comment thread was not.
</div>
<div class="stop">
<strong>Be careful with <code>.apk</code> files.</strong> Installing Android apps from outside the Play Store means switching off a safety feature and trusting the file completely. If your phone carries bank apps, client data, work email, or anything covered by a confidentiality obligation, this is the one category worth simply not doing — or doing on an old spare phone with nothing on it. Many such apps also break the terms of service of whatever they modify, which is a separate question from whether they're safe.
</div>
<div class="flag">
<strong>When in doubt, get it read first.</strong> Paste the link into an AI: <em>"is there anything here that looks unsafe, and who made it?"</em> Thirty seconds, and it beats the alternative.
</div>
<h2 id="s11"><span class="n">11</span>Words that stop mattering once you know them</h2>
<table>
<tr><td>repo</td><td>one project, one folder of stuff</td></tr>
<tr><td>gist</td><td>a single file — a public note</td></tr>
<tr><td>release</td><td>a packaged, ready-to-use version — your download</td></tr>
<tr><td>README</td><td>the instructions, written by the maker</td></tr>
<tr><td>assets</td><td>the actual downloadable files inside a release</td></tr>
<tr><td>issues</td><td>the complaints-and-bugs tab. Genuinely useful: it tells you whether the thing actually works for other people</td></tr>
<tr><td>commit</td><td>one saved snapshot, with a note about what changed</td></tr>
<tr><td>fork / clone / branch</td><td>developer things. You will never need them. Ignore.</td></tr>
</table>
<h2 id="s12"><span class="n">12</span>The other thing git does</h2>
<p>Underneath everything, GitHub runs on <strong>git</strong>, which is really just <em>save-history for a folder</em>. You take a snapshot whenever you like, and you can always go back to exactly how things were on any past date — every version kept, nothing overwritten, each with a note from you about what changed and why.</p>
<p>You saw it working in section 6: the <strong>Revisions</strong> tab on that gist is the same feature. Every edit, dated, recoverable.</p>
<p>People use it for code. It works just as well for documents, working papers, notes — any folder where "which version was this, and what changed since last month" is a question you'd rather not answer from memory. Nothing goes online unless you deliberately upload it; it can live entirely on your own laptop.</p>
<p class="quiet">Filed under "someday, maybe". You do not need it to download a file.</p>
<footer>
<strong>v3.3</strong> — mobile: horizontal scrolling disabled outright, and the ASCII layout diagram swapped for a reflowing list on small screens.<br><strong>v3.2</strong> — an "In short" summary block, meta description, and the website shortcut moved to the front of its section, so AI summarisers surface the points that matter.<br><strong>v3.1</strong> — mobile formatting: long links wrap, tables scroll instead of overflowing.<br><strong>v3</strong> — added organisation pages: the three page types, the name-count test, and the ReVanced example. This was the missing piece; most people give up on an org page without realising that is what they are looking at.<br><strong>v2</strong> — worked examples (a gist, a repo with no Releases), <code>.bat</code> files, jump menu.<br>
Written for someone smart who isn't a programmer, because the version that already existed assumed you were one.<br>
Copy it, change it, send it on.
</footer>
</div>
</body>
</html>