If you are not sure if the website you would like to visit is secure, you can verify it here. Enter the website address of the page and see parts of its content and the thumbnail images on this site. None (if any) dangerous scripts on the referenced page will be executed. Additionally, if the selected site contains subpages, you can verify it (review) in batches containing 5 pages.
favicon.ico: web.archive.org/web/20230202224628/https://github.com/readme/guides/documentation-note-taking - Documenting knowledge: a guide.

site address: web.archive.org/web/20230202172734/https://github.com/readme/guides/documentation-note-taking redirected to: web.archive.org/web/20230202224628/https://github.com/readme/guides/documentation-note-taking

site title: Documenting knowledge: a guide to successful note-taking · GitHub

Our opinion (on Friday 25 September 2026 19:28:11 UTC):

GREEN status (no comments) - no comments
After content analysis of this website we propose the following hashtags:



Meta tags:
description=If your project teammate won the lottery and left tomorrow, where would all their knowledge go? @cassidoo suggests learning the art of note-taking:;

Headings (most frequently used words):

for, the, to, support, what, about, documenting, knowledge, guide, successful, note, taking, more, stories, product, platform, company, that, lottery, winner, case, remembering, sifting, through, find, important, para, method, moving, forward, scaling, mlops, education, middleware, web, applications, it, not, just, enterprises, in, scorecard, we, trust, readme, project, follow, us, nominate, developer, community, sign, up, newsletter,

Text of the page (most frequently used words):
the (60), and (37), you (33), your (27), github (23), team (23), that (20), for (19), can (17), #knowledge (13), notes (13), readme (11), this (9), community (9), project (9), note (9), all (9), with (8), time (8), what (8), have (8), down (8), ideas (8), taking (8), about (7), open (7), source (7), want (7), information (7), system (7), out (6), developer (6), from (6), projects (6), they (6), more (6), things (6), writing (6), resources (5), stories (5), culture (5), manage (5), best (5), too (5), over (5), documentation (5), helpful (5), code (5), write (5), when (5), how (5), jump (5), 2022 (4), organization (4), new (4), sign (4), developers (4), need (4), but (4), teams (4), web (4), not (4), even (4), document (4), into (4), take (4), are (4), shared (4), them (4), something (4), would (4), search (4), signed (3), blog (3), support (3), security (3), product (3), every (3), articles (3), other (3), content (3), help (3), nominate (3), think (3), should (3), explore (3), world (3), activity (3), just (3), cassidy (3), through (3), building (3), making (3), has (3), sharing (3), everything (3), there (3), much (3), important (3), start (3), now (3), understanding (3), areas (3), which (3), don (3), together (3), work (3), well (3), paper (3), understand (3), good (3), could (3), will (3), lottery (3), documenting (3), guide (3), another (2), tab (2), window (2), refresh (2), session (2), reload (2), 2023 (2), skills (2), professional (2), pricing (2), customer (2), enterprise (2), features (2), podcast (2), around (2), newsletter (2), follow (2), ongoing (2), effort (2), voices (2), space (2), coding (2), maintainers (2), these (2), put (2), build (2), fix (2), issues (2), labs (2), education (2), thing (2), startups (2), check (2), was (2), learn (2), universe (2), easy (2), often (2), develop (2), forward (2), like (2), establish (2), own (2), practices (2), organizing (2), inactive (2), para (2), method (2), way (2), decides (2), everyone (2), same (2), people (2), easily (2), where (2), organize (2), predictable (2), collaborate (2), creative (2), being (2), thinking (2), searchable (2), capture (2), without (2), context (2), words (2), find (2), remember (2), concepts (2), create (2), teammates (2), day (2), meaningful (2), process (2), significant (2), case (2), responsibility (2), again (2), doesn (2), isn (2), able (2), who (2), someone (2), collective (2), devops (2), topics (2), guides (2), successful (2), packages (2), mar (2), perform, action, git, site, map, updated, privacy, terms, inc, tiktok, twitch, youtube, linkedin, facebook, twitter, shop, social, impact, inclusion, press, careers, company, contact, status, services, forum, docs, desktop, electron, partners, api, platform, roadmap, thank, subscribe, month, share, episodes, great, recognize, working, behind, scenes, get, inspiring, feature, part, amplify, evolving, engage, challenges, technology, surround, usually, seen, solitary, actually, largest, led, contributors, unsung, heroes, long, hours, software, field, questions, communities, naveen, srinivasan, brian, russell, openssf, scorecard, trust, amit, saha, middleware, applications, enterprises, noah, gift, pragmatic, scaling, mlops, based, chicago, love, jokes, mechanical, keyboards, favorite, others, pursue, teaching, demos, starter, speaking, live, streams, mentoring, advising, memes, most, here, been, blast, since, teenager, plans, stopping, anytime, soon, talk, either, under, because, simply, know, change, then, single, page, turns, deep, rabbit, hole, connecting, finding, balance, healthy, may, phrase, goes, yesterday, next, moving, following, enabling, strengths, particularly, base, yourselves, set, guidelines, completed, committed, anymore, longer, relevant, archives, items, three, categories, management, linting, teammate, topic, theme, interest, development, direct, reports, products, sphere, standard, maintained, app, mockups, specifications, posts, series, tasks, linked, goal, deadline, describes, universal, digital, four, principles, outlined, below, forte, silver, bullet, key, buy, uses, approach, try, templates, pull, scratch, pad, jot, quick, later, treat, permanent, precious, pieces, composed, moved, changed, evolved, spend, unnecessary, energy, trying, brainstorming, decisions, navigate, common, formatting, reflect, hypothesize, discuss, test, matters, principle, book, smart, sönke, ahrens, standardization, enables, creativity, said, bog, productive, fleeting, very, powerful, captured, dedicating, focus, versus, getting, mean, losing, solve, side, coin, challenge, searching, structure, rarely, lose, quickly, humans, hard, original, train, thought, exact, phrases, were, using, sifting, translate, snowball, knack, tracking, imagine, became, habit, interesting, meeting, minutes, conversations, happened, throughout, committing, pen, helps, solidify, our, minds, research, shown, hand, physical, stimulates, brain, associated, increased, retention, remembering, also, repeatedly, gets, shoulders, one, two, once, regular, taker, cover, suggest, developing, some, kind, rotation, ensure, responsible, maintaining, risk, means, person, lost, establishing, become, data, hoarders, regularly, auditing, documents, date, archivable, having, available, anyone, might, pay, dividends, maybe, less, exciting, pulls, away, switch, jobs, deserved, vacation, jeopardy, winner, video, standardize, gathering, quality, why, grow, does, built, challenging, reinventing, wheel, bring, members, add, pile, despite, difficulty, essential, turnover, lead, regression, comprehension, suddenly, won, chat, never, heard, first, trouble, their, door, sailed, off, sunset, see, featured, browse, story, type, close, menu, amplifies, whose, contributions, move, cto, contenda, williams, thoughtful, improve, artwork, kasia, bojanowska, message, suggested, results, collections, trending, repositories, fund, sponsors, studies, devsecops, automation, solution, solutions, outside, discussions, plan, track, changes, review, better, copilot, instant, dev, environments, codespaces, vulnerabilities, host, automate, any, workflow, actions, toggle, navigation, skip, wayback, machine, http, archive, org, 20230202224628, https, com, timestamps, fail, success, 2024, feb, jan, nov, 2026, 287, captures,


Text of the page (random words):
documenting knowledge a guide to successful note taking github 287 captures 15 nov 2022 22 mar 2026 jan feb mar 02 2022 2023 2024 success fail about this capture timestamps the wayback machine http web archive org web 20230202224628 https github com readme guides documentation note taking skip to content toggle navigation sign up product actions automate any workflow packages host and manage packages security find and fix vulnerabilities codespaces instant dev environments copilot write better code with ai code review manage code changes issues plan and track work discussions collaborate outside of code explore all features documentation github skills blog solutions for enterprise teams startups education by solution ci cd automation devops devsecops case studies customer stories resources open source github sponsors fund open source developers the readme project github community articles repositories topics trending collections pricing search all github jump to no suggested jump to results search all github jump to search all github jump to search all github jump to sign in sign up message artwork kasia bojanowska documenting knowledge a guide to successful note taking how building a team culture around thoughtful note taking can improve collective understanding cassidy williams cto contenda the readme project amplifies the voices of the open source community the maintainers developers and teams whose contributions move the world forward every day the readme project menu close browse by story type featured articles developer stories guides the readme podcast explore topics see all open source culture security devops nominate a developer support the community what if someone on your team suddenly won the lottery what if they signed out of the team chat and you never heard from them again well first of all good for them but would your team be in trouble would all of their knowledge go out the door as they sailed off into the sunset as your teams grow so does the collective knowledge you ve built together it can be challenging to manage that knowledge document it all create new ideas without reinventing the wheel and bring new team members into your space to add even more knowledge to the pile despite this difficulty it is essential that turnover doesn t lead to a significant regression in team comprehension in this guide you will learn why documenting knowledge is a meaningful process best practices for quality note taking how to standardize information gathering team knowledge sharing universe 2022 video what about that lottery winner if it isn t the lottery maybe it s something less exciting that pulls your teammates away if and when someone decides to switch jobs work on something new or even go on a well deserved vacation would your projects be in jeopardy would your team be able to manage the risk of not writing things down in a searchable way means that a person s knowledge could be lost establishing a culture of documentation in which your team has a shared system of how and where they should write can help this now you don t want to become data hoarders regularly auditing notes and documents as being out of date or archivable is a good thing but having the context available to anyone who might need it will pay dividends over time also it s important to understand that note taking is a team responsibility too often this responsibility repeatedly gets put on the shoulders of the same one or two people and once again everything about team notes should be shared if a regular note taker doesn t take notes or isn t able to who will cover for them i suggest developing some kind of rotation system to ensure that everyone is responsible for maintaining team knowledge a case for remembering writing down interesting ideas meeting minutes or even notes about conversations with teammates can be helpful to remember what happened throughout your day committing pen to paper is a meaningful process that helps to solidify concepts in our minds research has shown that writing by hand on physical paper stimulates significant brain activity which could be associated with increased information retention when you want to remember something you have to write it down when you want to understand something you have to translate ideas into your own words ideas and creative concepts snowball the more you write things down the more you start to develop a good knack for thinking up and tracking your ideas now imagine if writing things down became a habit for your team think of what you could create together sifting through to find what s important on the other side of the note taking coin is the challenge of searching through your team s notes and documentation without structure knowledge sharing is rarely helpful we lose context quickly as humans and it can be hard to follow your original train of thought or understand the exact words or phrases you were using that being said thinking too much about making your team s notes searchable can bog you down when writing them and is not productive ideas are fleeting and can be very powerful over time if captured well dedicating too much of your focus to content organization versus getting ideas down on paper can mean losing what you want to capture to solve this you need to have a predictable system for your notes there s a helpful principle from the book how to take smart notes by sönke ahrens standardization enables creativity you don t want to spend unnecessary energy trying to organize your notes as you re brainstorming with your team and making decisions you want to have an easy to navigate predictable system for note taking when you have common formatting organization and a shared understanding of how to document things your team can think reflect hypothesize discuss test and collaborate more easily this is the creative work that matters there s no silver bullet system for notes the way your team decides to take notes is up to your team the key is to have a shared buy in in which everyone uses the same approach you can try to build templates that people can easily pull from or have scratch pad areas where you can jot down quick ideas that you ll organize later you don t need to treat notes as if they re permanent precious pieces of information notes can be composed together moved changed and evolved over time just like the code you write the para method the forte labs organization describes the para method a universal system for organizing digital information the system s four principles are outlined below projects a series of tasks linked to a goal with a deadline ex app mockups product specifications blog posts areas a sphere of activity with a standard to be maintained over time ex professional development direct reports products writing resources a topic or theme of ongoing interest ex project management linting teammate information archives inactive items from the other three categories ex projects that are completed or inactive areas you re not committed to anymore resources that are no longer relevant following a set of guidelines like this can be helpful for your team as you establish your own best practices enabling your team s strengths in organizing and understanding information is particularly helpful as you establish a knowledge base for yourselves moving forward it s easy to either under document everything because there s simply too much to know and things change too often or over document everything and then every single page turns into a deep rabbit hole of connecting information finding that balance is important a culture of healthy documentation may take time to develop but as the phrase goes the best time to start was yesterday and the next best time to start is now want to learn more check out cassidy s talk on team knowledge sharing at github universe hi i m cassidy i m based in chicago and i love coding jokes and mechanical keyboards ️ my favorite thing to do is help others to be the best that they can be and i pursue that through teaching building demos and starter projects on my github speaking my newsletter my live streams mentoring advising startups and even just by making memes you can check out most of these things here building for the web has been a blast for me since i was a teenager and i have no plans of stopping anytime soon more stories scaling mlops education noah gift pragmatic ai labs middleware for web applications it s not just for enterprises amit saha in scorecard we trust naveen srinivasan brian russell openssf about the readme project coding is usually seen as a solitary activity but it s actually the world s largest community effort led by open source maintainers contributors and teams these unsung heroes put in long hours to build software fix issues field questions and manage communities the readme project is part of github s ongoing effort to amplify the voices of the developer community it s an evolving space to engage with the community and explore the stories challenges technology and culture that surround the world of open source follow us nominate a developer nominate inspiring developers and projects you think we should feature in the readme project support the community recognize developers working behind the scenes and help open source projects get the resources they need sign up for newsletter every month we ll share new articles from the readme project episodes of the readme podcast and other great developer content from around the community subscribe thank you product features security team enterprise customer stories the readme project pricing resources roadmap platform developer api partners electron github desktop support docs community forum professional services skills status contact github company about blog careers press inclusion social impact shop github on twitter github on facebook github on linkedin github on youtube github on twitch github on tiktok github s organization on github 2023 github inc terms privacy updated 08 2022 site map what is git you can t perform that action at this time you signed in with another tab or window reload to refresh your session you signed out in another tab or window reload to refresh your session
Thumbnail images (randomly selected): * Images may be subject to copyright.GREEN status (no comments)
  • loading
  • Cassidy Williams
  • Photo of Cassidy Williams
  • Photo of Noah Gift
  • Photo of Amit Saha
  • Photo of Naveen Srinivasa...
  • Twitter icon
  • Facebook icon
  • Linkedin icon
  • YouTube icon
  • Twitch icon
  • TikTok icon
  • GitHub mark

Verified site has: 82 subpage(s). Do you want to verify them? Verify pages:

1-5 6-10 11-15 16-20 21-25 26-30 31-35 36-40 41-45 46-50
51-55 56-60 61-65 66-70 71-75 76-80 81-82


The site also has references to the 2 subdomain(s)

  archive.org  Verify   help.archive.org  Verify


Top 50 hastags from of all verified websites.

Supplementary Information (add-on for SEO geeks)*- See more on header.verify-www.com

Header

HTTP/1.1 302 FOUND
Server nginx
Date Fri, 25 Sep 2026 19:28:10 GMT
Content-Type text/plain; charset=utf-8
Content-Length 0
Connection close
x-archive-redirect-reason found capture at 20230202224628
location htt???/web.archive.org/web/20230202224628/htt????/github.com/readme/guides/documentation-note-taking
server-timing captures_list;dur=0.618211, exclusion.robots;dur=0.076188, exclusion.robots.policy;dur=0.065376, esindex;dur=0.007758, cdx.remote;dur=110.836055, LoadShardBlock;dur=433.050904, PetaboxLoader3.datanode;dur=177.642980, PetaboxLoader3.resolve;dur=232.744910
x-app-server wwwb-app249-dc8
x-ts 302
x-tr 656
server-timing TR;dur=0,Tw;dur=0,Tc;dur=1
set-cookie wb-p-SERVER=wwwb-app249; path=/
X-location All
X-AS 16276
X-RL 0
X-NA 0
X-Page-Cache MISS
Server-Timing MISS
X-NID OVH SAS
Referrer-Policy no-referrer-when-downgrade
Permissions-Policy interest-cohort=()
X-sd 0
HTTP/1.1 200 OK
Server nginx
Date Fri, 25 Sep 2026 19:28:11 GMT
Content-Type text/html; charset=utf-8
Transfer-Encoding chunked
Connection close
x-archive-orig-server GitHub.com
x-archive-orig-date Thu, 02 Feb 2023 22:46:28 GMT
x-archive-orig-vary X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, Accept-Encoding, Accept, X-Requested-With
x-archive-orig-etag W/ 490afde5a02946dedb94af6176d0c6a7
x-archive-orig-cache-control max-age=0, private, must-revalidate
x-archive-orig-strict-transport-security max-age=31536000; includeSubdomains; preload
x-archive-orig-x-frame-options deny
x-archive-orig-x-content-type-options nosniff
x-archive-orig-x-xss-protection 0
x-archive-orig-referrer-policy origin-when-cross-origin, strict-origin-when-cross-origin
x-archive-orig-content-security-policy default-src none ; base-uri self ; block-all-mixed-content; child-src github.com/assets-cdn/worker/ gist.github.com/assets-cdn/worker/; connect-src self uploads.github.com objects-origin.githubusercontent.com www.githubstatus.com collector.github.com raw.githubusercontent.com api.github.com github-cloud.s3.amazonaws.com github-production-repository-file-5c1aeb.s3.amazonaws.com github-production-upload-manifest-file-7fdce7.s3.amazonaws.com github-production-user-asset-6210df.s3.amazonaws.com cdn.optimizely.com logx.optimizely.com/v1/events *.actions.githubusercontent.com wss://*.actions.githubusercontent.com online.visualstudio.com/api/v1/locations github-production-repository-image-32fea6.s3.amazonaws.com github-production-release-asset-2e65be.s3.amazonaws.com insights.github.com wss://alive.github.com; font-src github.githubassets.com; form-action self github.com gist.github.com objects-origin.githubusercontent.com; frame-ancestors none ; frame-src viewscreen.githubusercontent.com notebooks.githubusercontent.com www.youtube.com player.vimeo.com; img-src self data: github.githubassets.com media.githubusercontent.com camo.githubusercontent.com identicons.github.com avatars.githubusercontent.com github-cloud.s3.amazonaws.com objects.githubusercontent.com objects-origin.githubusercontent.com secured-user-images.githubusercontent.com/ opengraph.githubassets.com github-production-user-asset-6210df.s3.amazonaws.com customer-stories-feed.github.com spotlights-feed.github.com *.githubusercontent.com images.ctfassets.net/s5uo95nf6njh/ assets.ctfassets.net/s5uo95nf6njh/ downloads.ctfassets.net/s5uo95nf6njh/; manifest-src self ; media-src github.com user-images.githubusercontent.com/ secured-user-images.githubusercontent.com/ github.githubassets.com downloads.ctfassets.net/s5uo95nf6njh/; script-src github.githubassets.com; style-src unsafe-inline github.githubassets.com; worker-src github.com/assets-cdn/worker/ gist.github.com/assets-cdn/worker/
x-archive-orig-accept-ranges bytes
x-archive-orig-x-github-request-id 8F6C:8BB8:55B322:7F6935:63DC3D44
x-archive-orig-connection close
x-archive-guessed-content-type text/html
x-archive-guessed-charset utf-8
memento-datetime Thu, 02 Feb 2023 22:46:28 GMT
link <htt????/github.com/readme/guides/documentation-note-taking>; rel= original , <htt???/web.archive.org/web/timemap/link/htt????/github.com/readme/guides/documentation-note-taking>; rel= timemap ; type= application/link-format , <htt???/web.archive.org/web/htt????/github.com/readme/guides/documentation-note-taking>; rel= timegate , <htt???/web.archive.org/web/20221115114616/htt????/github.com/readme/guides/documentation-note-taking>; rel= first memento ; datetime= Tue, 15 Nov 2022 11:46:16 GMT , <htt???/web.archive.org/web/20230201215249/htt????/github.com/readme/guides/documentation-note-taking>; rel= prev memento ; datetime= Wed, 01 Feb 2023 21:52:49 GMT , <htt???/web.archive.org/web/20230202224628/htt????/github.com/readme/guides/documentation-note-taking>; rel= memento ; datetime= Thu, 02 Feb 2023 22:46:28 GMT , <htt???/web.archive.org/web/20230203232228/htt????/github.com/readme/guides/documentation-note-taking>; rel= next memento ; datetime= Fri, 03 Feb 2023 23:22:28 GMT , <htt???/web.archive.org/web/20260322041524/htt????/github.com/readme/guides/documentation-note-taking>; rel= last memento ; datetime= Sun, 22 Mar 2026 04:15:24 GMT
content-security-policy default-src self unsafe-eval unsafe-inline data: blob: archive.org web.archive.org web-static.archive.org wayback-api.archive.org athena.archive.org analytics.archive.org pragma.archivelab.org wwwb-events.archive.org
x-archive-src github.com-20230202-103537/IA-FOC-github.com-20230202220308-00000.warc.gz
server-timing captures_list;dur=0.487888, exclusion.robots;dur=0.068622, exclusion.robots.policy;dur=0.059818, esindex;dur=0.009786, cdx.remote;dur=6.606437, LoadShardBlock;dur=283.055007, PetaboxLoader3.datanode;dur=42.645411, PetaboxLoader3.resolve;dur=270.184129, load_resource;dur=73.501561, nav;dur=0.131381
x-app-server wwwb-app267-dc8
x-ts 200
x-tr 447
server-timing TR;dur=0,Tw;dur=0,Tc;dur=1
set-cookie wb-p-SERVER=wwwb-app267; path=/
X-location All
X-AS 16276
X-RL 0
X-NA 0
X-Page-Cache MISS
Server-Timing MISS
X-NID OVH SAS
Referrer-Policy no-referrer-when-downgrade
Permissions-Policy interest-cohort=()
X-sd 0
Content-Encoding gzip

Meta Tags

title="Documenting knowledge: a guide to successful note-taking · GitHub"
charset="utf-8"
name="request-id" content="8F6C:8BB8:55B322:7F6935:63DC3D44" data-pjax-transient="true"
name="html-safe-nonce" content="d82eabaa87b09e6772dbc8b8eba04485c94802f29b2c591d5e7cd76eeb1ee73c" data-pjax-transient="true"
name="visitor-payload" content="eyJyZWZlcnJlciI6Imh0dHBzOi8vZ2l0aHViLmNvbS9yZWFkbWUiLCJyZXF1ZXN0X2lkIjoiOEY2Qzo4QkI4OjU1QjMyMjo3RjY5MzU6NjNEQzNENDQiLCJ2aXNpdG9yX2lkIjoiOTEwMDY4NDA2NDMzNjkxNzI4MCIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9" data-pjax-transient="true"
name="visitor-hmac" content="88a24ec913bb1482d79eec4bd4412713d582c953b60c25b67e19996aacf7159f" data-pjax-transient="true"
name="github-keyboard-shortcuts" content="" data-turbo-transient="true"
name="selected-link" value="/readme/guides/documentation-note-taking" data-turbo-transient
name="google-site-verification" content="c1kuD-K2HIVF635lypcsWPoD4kilo5-jA_wBFyT4uMY"
name="google-site-verification" content="KT5gs8h0wvaagLKAVWq8bbeNwnZZK1r1XQysX3xurLU"
name="google-site-verification" content="ZzhVyEFwb7w3e0-uOTltm8Jsck2F5StVihD0exw2fsA"
name="google-site-verification" content="GXs5KoUUkNCoaAZn7wPN-t01Pywp9M3sEjnt_3_ZWPc"
name="google-site-verification" content="Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I"
name="octolytics-url" content="htt????/collector.github.com/github/collect"
name="user-login" content=""
name="viewport" content="width=device-width"
name="description" content="If your project teammate won the lottery and left tomorrow, where would all their knowledge go? @cassidoo suggests learning the art of note-taking:"
property="fb:app_id" content="1401488693436528"
name="apple-itunes-app" content="app-id=1477376905"
name="twitter:image:src" content="htt????/images.ctfassets.net/s5uo95nf6njh/2rfXSFuUGFGZNcILObc0E9/82e116aee81079a6aca09966030d2b62/1200x628-ReadMe-Twitter_LI_Post-Cassidy_Williams.jpg"
name="twitter:site" content="@github"
name="twitter:card" content="summary_large_image"
name="twitter:title" content="Documenting knowledge: a guide to successful note-taking"
name="twitter:description" content="If your project teammate won the lottery and left tomorrow, where would all their knowledge go? @cassidoo suggests learning the art of note-taking:"
property="og:image" content="htt???/web.archive.org/web/20230202224628im_/htt????/images.ctfassets.net/s5uo95nf6njh/2rfXSFuUGFGZNcILObc0E9/82e116aee81079a6aca09966030d2b62/1200x628-ReadMe-Twitter_LI_Post-Cassidy_Williams.jpg"
property="og:image:alt" content="If your project teammate won the lottery and left tomorrow, where would all their knowledge go? @cassidoo suggests learning the art of note-taking:"
property="og:site_name" content="GitHub"
property="og:type" content="object"
property="og:title" content="Documenting knowledge: a guide to successful note-taking"
property="og:url" content="htt???/web.archive.org/web/20230202224628/htt????/github.com/readme/guides/documentation-note-taking"
property="og:description" content="If your project teammate won the lottery and left tomorrow, where would all their knowledge go? @cassidoo suggests learning the art of note-taking:"
name="hostname" content="github.com"
name="expected-hostname" content="github.com"
name="enabled-features" content="TURBO_EXPERIMENT_RISKY,IMAGE_METRIC_TRACKING,GEOJSON_AZURE_MAPS"
http-equiv="x-pjax-version" content="7aac0fb7da04cf9b0f78e9504d0c61edf066a3946e015bad713e08a451e565d4" data-turbo-track="reload"
http-equiv="x-pjax-csp-version" content="1bf4ef0078b3fc7b1c4e0e31f9c1bd9b1f47da20092c1adf9765af8b5d8a097f" data-turbo-track="reload"
http-equiv="x-pjax-css-version" content="cd753f253ddc9585038376b112bb27a033ce85a91d16b2f73ed8700e7f404269" data-turbo-track="reload"
http-equiv="x-pjax-js-version" content="3670defaf0d45be1df11b585a7bd3fc44fb813030227133e6be11e086e754b41" data-turbo-track="reload"
name="turbo-cache-control" content="no-preview" data-turbo-transient=""
name="readme-story-name" content="Cassidy Williams"
name="is_logged_out_page" content="true"
name="turbo-body-classes" content="logged-out env-production page-responsive readme-project header-overlay"
name="browser-stats-url" content="htt????/api.github.com/_private/browser/stats"
name="browser-errors-url" content="htt????/api.github.com/_private/browser/errors"
name="browser-optimizely-client-errors-url" content="htt????/api.github.com/_private/browser/optimizely_client/errors"
name="theme-color" content="#1e2327"

Load Info

page size42018
load time (s)1.980668
redirect count1
speed download21221
server IP 207.241.237.3
* all occurrences of the string "http://" have been changed to "htt???/"