Day 1 as a Web Designer and Developer Advocate At...  🔗 **Source:** [Day 1 as a Web Designer and Developer Advocate At...](https://twitter.com/courtneyr_dev/status/1399818510100992000/?rw_tt_thread=True) > [!note]+ Document Notes > tags: [developer-advocacy, godaddy, wordpress-training, career-transitions, devrel-identity] > author: "@courtneyr_dev 🌻" > source: Twitter/X (three-tweet thread) > reference: https://courtneyengle.com/2021/06/01/web-designer-and-developer-advocate/ > date created: 2026-09-25 > > > [!info] Generated analysis — not the author's words. Sections below are machine-written > > from the captured source. Only text inside `> [!quote]` blocks is verbatim from the author. > > Do not quote or attribute any other line to the named author. > <!-- deep-read:sections start --> ## 🏷️ Title **"Day 1 as a Web Designer and Developer Advocate at @GoDaddyPro"** — a three-tweet announcement thread by @courtneyr_dev, dated by its linked blog post to June 1, 2021. Two of the three tweets carried video that did not survive capture. ## 🧭 Table of Contents 1. [References (in-page)](#-references-in-page) 2. [Summary](#-summary) 3. [Main Content](#-main-content) → [Notes](#️-notes) 4. [References](#-references) 5. [Paraphrase](#️-paraphrase) 6. [Newsletter](#-newsletter) 7. [Action Items](#-action-items) 8. [Hypotheses](#-hypotheses) 9. [Methodology](#-methodology) 10. [Questions](#-questions) 11. [Future Research](#-future-research) 12. [Implications](#-implications) 13. [Learning Styles Assessment](#-learning-styles-assessment) 14. [Accessibility Assessment](#-accessibility-assessment) 15. [DEIB Assessment](#-deib-assessment) 16. [Logical Validity](#-logical-validity) 17. [DARVO Analysis](#️-darvo-analysis) 18. [Conclusion](#-conclusion) 19. [Refactor Appendix](#-refactor-appendix) ## 🔗 References (in-page) Five links, enumerated from the captured markdown: 1. [@GoDaddyPro](https://twitter.com/GoDaddyPro) — the employer account, at the point of the role claim. 2. [@wpmodder](https://twitter.com/wpmodder) — named teammate (Adam W. Warner). 3. [@sunsanddesign](https://twitter.com/sunsanddesign) — named teammate. 4. `@Maja20072230` — named as plain text, **not linked**. The only unlinked mention in the thread. 5. [courtneyengle.com/2021/06/01/web-designer-and-developer-advocate/](https://courtneyengle.com/2021/06/01/web-designer-and-developer-advocate/) — the one outbound link, to the author's own long-form post on the same subject. Two `Your browser does not support the video tag.` fallbacks appear where video was embedded — tweets 1 and 3. That text is Reader's capture artifact, not the author's prose, and the video content itself is lost. ## 📝 Summary **What happened.** On what the linked post dates as June 1, 2021, Courtney Robertson announced her first day as a Web Designer and Developer Advocate at GoDaddy Pro, in a three-tweet thread. Tweet one names the role and three teammates and links a fuller blog post. Tweet two commits to continued involvement in WordPress training and reports feeling supported in the new role's opportunities. Tweet three reframes the job itself: the work is caring for others, with technology as a bonus. **Why it matters.** This is the origin document for a professional identity that recurs across the rest of the corpus. Nearly everything else saved under DevRel, OSPO, and WordPress training traces back to the role that starts here. It also contains an unusually explicit statement of what the author thinks developer advocacy *is* — a people-care role that happens to be technical — which is a position, not merely an announcement. **Stakeholders.** Courtney Robertson; GoDaddy Pro and the named team (Adam W. Warner, @sunsanddesign, Maja); the WordPress training and Learn WordPress community named as a continuing commitment; the wider DevRel field, for whom the third tweet is a stance worth arguing about. **Risks.** The capture is lossy — two videos are gone and one teammate's handle is unlinked, so the artifact is thinner than the original post. The content itself is five years stale as of this analysis and must never be read as current employment. And the third tweet's framing, taken without qualification, is the kind of claim that can be used to justify unbounded emotional labour in a role with no formal support structure for it. **Bottom line.** Short, dated, and foundational. Its value is as the anchor for a role identity, plus one genuinely arguable claim about the nature of advocacy work. ## 📖 Main Content The thread does three distinct things across three tweets, and they are not redundant with one another. **Tweet one is the announcement proper.** It states the role title exactly — "Web Designer and Developer Advocate" — and the employer, then immediately pivots from the role to the people: three named colleagues and "the rest of the GoDaddy Pro team," with the phrase "I feel right at home." The link out to courtneyengle.com signals that the real content lives elsewhere; the tweet is a pointer, not the substance. A video accompanied it and is not in the capture. **Tweet two is the continuity commitment.** It answers the question a role change raises for a community: does this person disappear into a company job? The answer given is no — continued involvement in WordPress-related training — and the reason given is institutional: feeling "incredibly supported in so many opportunities within this new role." This is a claim about the employer as much as about the author. It asserts that the company's support is what makes the community work possible, which is the standard shape of the sponsored-contributor arrangement in WordPress. **Tweet three is the thesis.** It is the only tweet that makes a general claim rather than reporting a fact: the job is really to care for others, and the technology is the bonus. That inverts the usual ordering of a technical role, where the domain is the substance and the people skills are the soft supplement. It is also the only sentence in the thread that would still be interesting if the date and employer were stripped away. The arc is announcement → reassurance → redefinition. That is a deliberate structure, and it is worth noting that the redefinition comes last, where a thread's least-read position is. ### 🗒️ Notes - **The role title is a compound.** "Web Designer *and* Developer Advocate" is two jobs joined, not one. That compound is itself a small piece of evidence about how hosting companies scoped DevRel work in 2021. - **The naming pattern is the point of tweet one.** Three individuals before "the rest of the team." Belonging is asserted through specific people, not through the organisation. - **"I feel right at home" is a day-one claim.** It is a statement of expectation, not of experience; nothing is being reported about the job yet because the job has not happened. - **Tweet two's causal claim.** "Feel incredibly supported" is offered as the reason continued training involvement is possible. That makes the community contribution contingent on employer support — a dependency worth marking, because it is the load-bearing assumption in every sponsored-contributor arrangement. - **Tweet three contains a typo in the original.** "It still amazes my that my job…" — preserved verbatim in the quote blocks below rather than silently corrected, because the atoms must match the source. - **Two videos are missing.** Reader captured the `Your browser does not support the video tag.` fallback twice. Whatever was said on camera — likely the substance of the announcement — is not recoverable from this document. - **One handle is unlinked.** `@Maja20072230` appears as plain text while the other two handles are linked. Most likely a Twitter mention-rendering artifact rather than an authorial choice, but it means the third teammate is harder to resolve to a person than the other two. - **The date comes from the URL, not the capture.** The blog permalink contains `/2021/06/01/`, which is the only date evidence in the document. The thread itself carries no timestamp, unlike the sibling document saved in the same batch. ## 📚 References **Primary (authored by the subject, same event):** - [Web Designer and Developer Advocate — courtneyengle.com, 2021-06-01](https://courtneyengle.com/2021/06/01/web-designer-and-developer-advocate/) — the long-form version of this announcement, and the only outbound link in the thread. Anyone working from this document should read that post instead; this thread is its trailer. **People named:** - [@wpmodder](https://twitter.com/wpmodder) — Adam W. Warner. Corroborated as a GoDaddy Pro colleague by the sibling document in this batch, where he is identified as Courtney's manager as of Nov 2024. - [@sunsanddesign](https://twitter.com/sunsanddesign) - `@Maja20072230` — unlinked in the source. **Organisation:** - [@GoDaddyPro](https://twitter.com/GoDaddyPro) **Sourcing assessment.** The thread cites exactly one outbound source, and it is the author's own post about the same event — appropriate for a first-person announcement, where the author is the primary source. There is nothing here that requires external citation and nothing that lacks it. ## 🗣️ Paraphrase *The following restates the thread's content in the analyst's words. None of it is the author's phrasing.* **Tweet one, restated.** Today is the first day in a new job that combines web design with developer advocacy, at GoDaddy Pro. The team already feels familiar — three colleagues are named specifically, and the rest of the group is included by reference. A longer written account is available on the author's own site. **Tweet two, restated.** The move into this role does not end the author's participation in WordPress training work. On the contrary, the new position is described as actively supportive of that participation, opening rather than closing opportunities. **Tweet three, restated.** The author reflects that what the job fundamentally consists of is looking after other people. That the work also involves technology, and specifically the technology she cares most about, is treated as an additional piece of good fortune rather than as the core of the role. ## 📰 Newsletter **From the archive: the day the job description got rewritten** File this one under origin stories. Five years ago — June 1, 2021, if we trust the permalink, and permalinks are more honest than memory — a three-tweet thread announced a first day at [GoDaddy Pro](https://twitter.com/GoDaddyPro) in a role with an ambitiously hyphenated title: Web Designer *and* Developer Advocate. Two jobs, one paycheck, which was very much the shape of WordPress DevRel in 2021 and, let's be honest, is still the shape of it in a good many places. The first tweet does the polite thing and names the team. The second does the necessary thing and reassures the community that [#WordPress](https://wordpress.org/) training involvement is not about to vanish into a corporate calendar — a real concern, and one the sponsored-contributor model lives or dies by. But it's the third tweet that earns its keep, and it's the one nobody scrolls far enough to read: > It still amazes my that my job is really to care for others. It's a bonus that it involves technology and areas I am most passionate about. Typo and all. That's a job description most DevRel postings would never dare write down, because HR would ask what the deliverable is. And yet anyone who has watched a Learn WordPress session land, or sat with a new contributor through their first Trac ticket, knows the sentence is simply accurate. The technology is the medium. The care is the work. Worth noting what the archive lost: two videos, gone to the great link-rot beyond, leaving only `Your browser does not support the video tag.` where a face used to be. A reminder that the platform you announce your career on is not a platform that keeps it. The long version, [still live on courtneyengle.com](https://courtneyengle.com/2021/06/01/web-designer-and-developer-advocate/), outlasted the videos. Owned domains usually do. ## ✅ Action Items **DevRel** - Treat tweet three as a usable articulation of role purpose. "The job is to care for others; the technology is the bonus" is a one-line answer to "what does a developer advocate actually do" that survives being quoted in a hiring conversation. - Note the compound title as evidence when arguing about DevRel scope creep: design *and* advocacy in one role is a resourcing decision with predictable consequences. **OSPO** - The dependency in tweet two — community training participation made possible by employer support — is the sponsored-contributor bargain stated plainly by a participant. Keep it as a citation for any Five for the Future or sponsorship-policy discussion. **Community** - The pattern of naming specific colleagues before the organisation is a small, replicable onboarding-welcome practice. Worth noting for contributor-mentorship guidance. **Training** - The continuity commitment here is the origin point of a long run of WordPress training work. If a Learn WordPress contributor timeline exists, June 2021 belongs on it as the start of the sponsored phase. **Marketing** - The video loss is the actionable part: announcement content that lives only as a platform-native video is unrecoverable within five years. Any announcement worth keeping needs a copy on an owned domain — which this one had, and which is why anything survives. **FAIR / The WPOCC** - No action. This predates both and touches neither. **All other subteams** (Core, Core Performance, Core AI, Core Program Team, Mobile, Playground, Support, Design, Documentation, Photos, TV, Polyglots, Accessibility, Meta, CLI, Hosting, Tide, Openverse, Themes, Plugins) - No action. A personal role announcement generates no work for code, design, or infrastructure teams. ## 🧪 Hypotheses 1. **The care-first framing predicts the shape of the subsequent work.** If tweet three is a genuine operating principle rather than a day-one sentiment, then the author's output over the following years should skew toward enablement artifacts — training, onboarding, mentorship, documentation — over artifacts that primarily demonstrate technical output. *Testable:* classify the corpus of work published 2021–2026 into enablement vs. demonstration and check the ratio. 2. **Compound DevRel titles correlate with role instability.** A role scoped as two jobs is more likely to be re-scoped, split, or eliminated within three years than a singular one. *Testable:* sample hosting-company DevRel job postings from 2020–2022, classify titles as compound or singular, and track the incumbent's tenure and subsequent title. 3. **Employer support is the binding constraint on sponsored community contribution, not individual motivation.** Tweet two attributes continued training work to institutional support. *Testable:* track WordPress training contribution volume for sponsored contributors across a sponsorship change; if motivation binds, volume holds, if support binds, volume drops. 4. **Platform-native announcement media has a half-life under five years; owned-domain copies do not.** Two of two videos here are unrecoverable while the linked blog post remains live. *Testable:* sample 50 role-announcement threads from 2021, measure survival of embedded media versus survival of linked owned-domain posts. 5. **Threads bury their strongest claim.** The only generalisable statement in this thread is in its last and least-read position. *Testable:* across a sample of announcement threads, code each tweet for claim generality and check whether generality correlates negatively with position. ## 📊 Methodology **The source's method.** None. This is a first-person announcement; there is no research design, no evidence gathering, and no claim requiring one. The author is the primary source for every factual assertion in it, and those assertions — a start date, a title, an employer, colleagues, an intention — are exactly the kind that a first-person account is authoritative about. **This analysis's method.** The captured markdown was read in full and its links enumerated before any claim about sourcing was made: five link positions, of which one is outbound and four are platform-internal or unlinked. The date was derived from the blog permalink path, which is the only date evidence in the document; it is a reasonable inference, not a certainty, since a permalink date reflects publication of the post rather than the tweet. Two `Your browser does not support the video tag.` markers were identified as capture artifacts and excluded from any count of authorial content. The teammate identification for @wpmodder was corroborated against the sibling document saved in the same batch rather than asserted from this document alone. **Limits.** The missing videos mean the thread's substantive content may be materially larger than what is analysed here, and nothing in this analysis can speak to it. ## ❓ Questions - What was in the two videos? If they contained the actual announcement content, this document is a shell and the blog post is the only surviving record. - Did the compound Web Designer / Developer Advocate title persist, or did it resolve into one of the two over time? - Who is @Maja20072230, and is the unlinked handle a rendering artifact or a deactivated account at capture time? - Why was this five-year-old thread saved into Reader on 2026-09-23, alongside the Warner anniversary tweet? A deliberate archival sweep of career-milestone posts is the obvious reading, but the pairing is the only evidence. - Does the care-first framing still hold for the author five years on, and if it has changed, what changed it? ## 🔮 Future Research - **Trace the role's evolution.** Compare this June 2021 title against the same person's title in later documents in the corpus. The sibling tweet places her at GoDaddy in Nov 2024 under Warner's management; the path between is worth reconstructing from the corpus itself. - **Build the sponsored-contributor dependency map.** Tweet two is one data point in a larger pattern about who funds WordPress community work and what happens when that funding moves. The corpus likely holds more. - **Test the care-first thesis against the DevRel literature.** The claim that advocacy is fundamentally care work with a technical medium has a small but real literature behind it; placing this first-person statement against it would make it citable rather than merely personal. - **Audit the archive for media loss.** If this thread lost two videos, other saved social documents in the corpus have likely lost media too, silently. A count would establish whether the capture pipeline needs a media-loss warning. ## 💡 Implications **Practice.** The care-first definition of advocacy is directly usable: in role scoping, in hiring conversations, and in defending DevRel headcount to people who want a deliverable count. It reframes the output question from "what did you ship" to "who can now do what they could not before." **Policy.** Tweet two makes the sponsored-contributor dependency explicit from the inside. Any policy discussion about corporate sponsorship of WordPress contribution should reckon with the fact that participants themselves describe their community work as enabled by employer support — which is both an argument for sponsorship and a description of its fragility. **Security.** Not applicable to this source. A personal role announcement raises no security consideration beyond the ordinary: it publicly associates a named individual with an employer, which is standard for the genre and already public via the linked post. **Education.** The continuity commitment in tweet two is, in retrospect, the start of a sustained run of WordPress training work. For anyone studying how open-source education programmes get staffed, this is the moment an individual contributor became a sponsored one — a transition that determines what such programmes can attempt. **Funding.** The implicit model here is that a hosting company funds community training work as part of a DevRel role. That is neither a grant nor a volunteer arrangement, and it has different failure modes than both: it is stable while the company's strategy holds and disappears with a reorganisation, without any of the notice a grant cycle provides. ## 🧠 Learning Styles Assessment - **Visual.** Originally strong, now absent. Two videos were the visual core of the announcement and did not survive capture. What remains is text-only, so the visual learner gets nothing from this document that they would have got from the original. - **Aural.** Same story — whatever was spoken on the videos is gone. Zero aural content in the captured artifact. - **Verbal.** The surviving strength. Three short, plainly written sentences with one memorable reframing. Well suited to verbal learners. - **Kinesthetic.** Nothing to do. No exercise, no walkthrough, no hands-on element. - **Logical.** Minimal. The thread contains one causal claim (support enables continued training work) and one definitional inversion (care is the job, technology is the bonus). A logical learner can work with the second; there is no argument chain to follow. - **Social.** The strongest dimension. The thread is fundamentally about belonging to a named group, and it models a social practice — naming individuals to signal welcome. - **Solitary.** Adequate. It reads fine alone in seconds and demands no discussion, though it also rewards none. - **Naturalistic.** Not applicable to this source. No environmental, ecological, or systems-in-nature content. **Reading level.** Roughly US grade 8. Short declarative sentences, common vocabulary, one compound job title as the only specialist term. The uncorrected "amazes my" typo does not impede comprehension. Accessible to anyone reading English at secondary level. ## 📊 Accessibility Assessment Mapped to WCAG 2.2 AA, assessed against the captured artifact. 1. **Text alternatives (1.1.1 Non-text Content).** Fails in the capture. Two videos are represented only by `Your browser does not support the video tag.` — a browser fallback string, not a text alternative. No description of the video content exists anywhere in the document. 2. **Time-based media (1.2.1–1.2.5 Captions, Audio Description).** Cannot be verified and presumed failing. Twitter auto-captions were inconsistent in 2021, and the captured artifact retains no caption track, transcript, or audio description for either video. 3. **Adaptable / structure (1.3.1 Info and Relationships).** Passes in the captured markdown. Tweet boundaries are marked with `---` rules, giving a machine-readable thread structure. The original platform rendering communicated thread order visually and through DOM order, which assistive technology handles adequately. 4. **Distinguishable (1.4.3 Contrast, 1.4.4 Resize Text).** Not determinable from the capture and inherited from the platform. Twitter's default theme met AA contrast in 2021; the markdown carries no styling of its own. 5. **Keyboard and navigation (2.1.1, 2.4.4 Link Purpose).** Partially failing. Four of five link targets are bare handles or a truncated URL — `courtneyengle.com/2021/06/01/web…` with an ellipsis — which does not convey link purpose out of context. A screen-reader user tabbing through links hears truncated hostnames, not destinations. 6. **Readable and predictable (3.1.1 Language of Page, 3.1.5 Reading Level).** Passes. English throughout, grade-8 reading level, no jargon requiring a glossary. The `#WordPress` hashtag is camel-free but single-word, so it reads correctly aloud. 7. **Robust / parsing and name-role-value (4.1.2).** Partially failing. `@Maja20072230` is a mention rendered as plain text while its siblings are links — an inconsistent name-role-value presentation that gives one named person less affordance than the others. Additionally, the video fallback text is exposed to assistive technology as content when it is in fact an error state, which is actively misleading. **Overall.** The prose is accessible; the media is not, and the capture makes that worse rather than better. The single most valuable remediation — a text description of what the videos contained — is now impossible. ## 🌍 DEIB Assessment **Cultural breadth.** Narrow, appropriately so. The frame of reference is US corporate tech and the WordPress project; no attempt is made at broader cultural reach, and none is called for in a personal announcement. Worth noting that "I feel right at home" is an idiom that does not translate cleanly and may read oddly to non-native English speakers in a global project. **Inclusive language.** Clean. No gendered collective nouns, no ableist idiom, no exclusionary jargon. "The rest of the GoDaddy Pro team" explicitly includes the unnamed, which is a small but real inclusive choice — the alternative, naming three people and stopping, would have drawn a line around a subset. **Neurodiversity support.** Good, incidentally. Very short units of text, one idea per tweet, explicit separators between them, no requirement to hold context across units. Low working-memory demand. The absent video captions cut the other way for anyone who processes text better than speech — but since the videos are gone entirely, the surviving artifact is text-only and therefore more accessible than the original. **Representation.** A woman announcing a developer advocacy role at a major hosting company, naming a mixed group of colleagues including at least two apparently women by handle and name. In a field where DevRel and especially web-design-adjacent roles are frequently coded as lower-status than engineering, an explicit, proud claim on the title is itself representational work. No self-deprecation, no hedging on the technical half of the role. **Psychological safety.** Actively models it. The thread's content is almost entirely about feeling safe — "right at home," "incredibly supported" — and it attributes that safety to specific named people rather than to abstract culture. The third tweet goes further by naming care as legitimate work, which lowers the cost for others of admitting that the people part of their job is the actual job. The one caution stands: framing care as the core of a role without a corresponding framing of its limits is how care work becomes unbounded, and nothing in the thread sets a boundary. ## ✅ Logical Validity **Strong reasoning.** The thread makes few claims and is careful about the ones it makes. Tweet one's assertions are all first-person facts the author is authoritative about. Tweet three is clearly flagged as reflection — "It still amazes my that…" — which correctly marks it as personal observation rather than a general truth about the profession, and that hedge is what keeps it valid. The link to the long-form post is the right move for a format that cannot carry the argument: it points to the evidence rather than pretending to contain it. **Fallacies.** *Hasty generalisation — potential, and avoided by hedging.* **Located** in tweet three: "my job is really to care for others." A claim about the essential nature of a role, drawn from day-one experience of it. **Why it is not fatal:** the sentence is scoped to "my job" and framed as personal amazement, not as a definition of developer advocacy generally. Read as written it is a valid first-person report. It becomes a hasty generalisation only when extracted and quoted as a definition of the field — which is exactly what this analysis was tempted to do in the Action Items above. **The fix:** any citation of this line must carry its scope, e.g. "one practitioner's description of her own role on her first day," not "developer advocacy is care work." *Appeal to novelty — latent.* **Located** in tweet two: "feel incredibly supported in so many opportunities within this new role." **Why it is weak evidence:** this is a day-one assessment of institutional support, made before any test of it. Day-one optimism is the least reliable moment to evaluate an employer. **The fix:** treat it as a statement of expectation, not of the employer's actual record. It would take a comparable statement at the two-year mark to carry evidentiary weight. No other fallacies located. There is no straw man, no false dilemma, no appeal to authority — the thread simply does not argue against anyone. **Tone of voice.** Warm, direct, unguarded. First person throughout, present tense, short sentences. Gratitude-forward without performing humility: the role title is stated plainly and claimed, not minimised. An uncorrected typo left standing signals a post written quickly and sincerely rather than drafted and reviewed — which for this genre is a credibility asset rather than a defect. ## 🛡️ DARVO Analysis **Deny.** Nothing denied. No accusation, allegation, or criticism is present or implied anywhere in the thread; there is nothing to deny. **Attack.** Nothing attacked. No person, organisation, or position is criticised. The only other parties mentioned are named positively as colleagues. **Reverse victim and offender.** No reversal. There is no conflict, no grievance, no claim of harm, and no assignment of blame in either direction. **Assessment.** Not applicable to this source. DARVO is a pattern of defensive rhetoric under accusation, and this document contains no accusation, no defence, and no adversarial content of any kind. The section is retained per the template with this explanation rather than dropped. ## 🎯 Conclusion **Bottom line.** A three-tweet role announcement from June 2021 that is thinner than it looks in two directions: two videos are lost to the capture, and the surviving text is mostly ceremonial. What justifies keeping it is the last tweet, which states a position on what developer advocacy fundamentally is — care work with a technical medium — and the second, which states plainly that community training participation runs on employer support. The first is quotable; the second is structurally important. Both are five years old and must be read with their date attached. **Next steps.** File as the origin marker for the DevRel role identity in the vault. Quote the care-first line only with its first-person scope intact. Treat the media loss as a signal worth checking across other saved social documents — if two videos vanished silently here, the pipeline is not reporting media loss anywhere. ## 🔄 Refactor Appendix ### 📚 Literature Atoms #### [H1] Advocacy is care work with technology as bonus > [!quote] > It still amazes my that my job is really to care for others. It's a bonus that it involves technology and areas I am most passionate about. **Context & use** - The strongest claim in the thread and the only generalisable one; note it sits in the last, least-read position. - Inverts the conventional ordering of a technical role: people are the substance, domain is the supplement. - Cite only with its first-person scope — "one practitioner on her first day," never "developer advocacy is care work." The hedge "It still amazes my that" is what keeps the claim valid. - Typo preserved verbatim from the source. **Tags:** #devrel-identity #care-work #role-definition <!-- atomicity: 1 idea ✓ --> #### [H2] Employer support enables continued community training work > [!quote] > I will continue to be involved in #WordPress related training and feel incredibly supported in so many opportunities within this new role. **Context & use** - The sponsored-contributor bargain stated from the inside: community participation described as enabled by institutional support. - Load-bearing for any Five for the Future or sponsorship-policy argument — it is a participant's own account, not an employer's claim. - Weak as evidence about the employer, being a day-one assessment; strong as evidence about how participants understand the arrangement. **Tags:** #sponsored-contribution #wordpress-training #ospo <!-- atomicity: 1 idea ✓ --> #### [H3] Belonging is asserted by naming individuals, not organisations > [!quote] > I feel right at home with [@wpmodder](https://twitter.com/wpmodder) [@sunsanddesign](https://twitter.com/sunsanddesign) @Maja20072230 and the rest of the GoDaddy Pro team. **Context & use** - Three named people precede the collective; the organisation is reached through individuals rather than the other way round. - "And the rest of the team" closes the set inclusively rather than leaving a line drawn around three. - A small replicable practice for contributor welcome and onboarding guidance. **Tags:** #belonging #onboarding #community-practice <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates #### [P1] care-framing-without-boundary-becomes-unbounded-labour **Claim.** Defining a role as fundamentally caring for others is legitimising and load-bearing, but without an accompanying statement of limits it licenses unbounded emotional labour — because care has no natural completion condition the way a shipped feature does. **Evidence pointer.** [H1] — the claim that the job is "really to care for others" appears with no corresponding statement of scope, capacity, or stopping point anywhere in the thread. **Scope & conditions.** Applies to DevRel, community, training, and support roles where the deliverable is another person's capability rather than an artifact. Does not apply where care is one named responsibility among several scoped ones. The risk is proportional to how much the framing is embraced by the individual rather than imposed by the employer — self-imposed unbounded care is the harder case, because there is no one to negotiate with. **Links.** - Pairs with [H2]: if employer support is what enables the work, then the boundary on the work is set by the employer's capacity, not the individual's — which is precisely the negotiation the care framing makes awkward to open. - Connects to the standing enforcement-over-instruction thread in the system audit: a role definition is an instruction; a capacity limit would be an enforcement. This thread has the first and not the second, which is the same structural gap the audit keeps finding elsewhere. - Connects to any Five for the Future hours discussion, where the sponsored hours are the only hard boundary that exists. #### [P2] platform-native-media-does-not-survive-the-archive **Claim.** Announcement content embedded as platform-native media is effectively unrecoverable within five years, while the same content on an owned domain persists; a capture pipeline that does not warn about lost media silently produces documents that look complete and are not. **Evidence pointer.** Two `Your browser does not support the video tag.` fallbacks in this capture, against one outbound blog link that remains live and carries the same announcement. **Scope & conditions.** Applies to any read-later or archival pipeline ingesting social platform content. Does not apply where the pipeline captures media separately or flags its absence. The failure is specifically silent: the artifact reads as a complete three-tweet thread, and nothing in it announces that a third to a half of the original content is missing. **Links.** - Connects directly to the vault mirror step: a mirrored note inherits the loss without inheriting any warning about it. - Connects to the enforcement thesis — a check that counts video-fallback strings in captured bodies and flags the document would catch this deterministically, where an instruction to "note missing media" would not. - Connects to [P1] in the sibling document on dated social claims: both are cases where the artifact survives its own context. ### ✏️ Fleeting Queue - Does the deep-read pipeline have any check for `Your browser does not support the video tag.` and similar capture-failure strings? If not, that is a cheap, deterministic addition — count them, report them in the notes, and the document stops lying about its own completeness. - Two career-milestone posts from 2021 and 2024 saved into Reader within milliseconds of each other on 2026-09-23. Deliberate archival sweep, or a bulk import? Worth knowing, because it changes how the rest of that batch should be read. - The care-first line wants a companion note on where the boundary goes. The claim is good; it is half a thought. - Does the person-note for @Maja20072230 exist at all? The unlinked handle makes this the one teammate the document cannot resolve. ### → Things 3 - [ ] Add a capture-failure string check to the deep-read validation script — flag any document whose body contains a video or media fallback marker, so lost media is reported rather than silently absorbed. - [ ] Write the boundary companion to the care-first note: if advocacy is care work, what is the stopping condition? <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Tweets/Day 1 as a Web Designer and Developer Advocate At....md|Day 1 as a Web Designer and Developer Advocate At... by @courtneyr_dev 🌻]] ## Highlights - and the rest of the GoDaddy Pro team. ([View Highlight](https://read.readwise.io/read/01m3bbdj22s0z2h615n4v5kve1)) - Note: H3 — Three colleagues named individually, then the collective closed inclusively. Belonging asserted through people rather than organisation; a replicable welcome practice. - Tags: atom/fleeting/f1, atom/literature/h3 - I will continue to be involved in #WordPress related training and feel incredibly supported in so many opportunities within this new role. ([View Highlight](https://read.readwise.io/read/01m3bbdg1rfpx7jbhn4hjc9srg)) - Note: H2 — The sponsored-contributor bargain stated from the inside: community training participation described as enabled by employer support. Fallacy (appeal to novelty, latent): a day-one assessment of institutional support, made before any test of it. Fix — read as expectation, not as the employer's record. - Tags: atom/literature/h2, fallacy/appeal-to-novelty, action/h2 - It still amazes my that my job is really to care for others. It's a bonus that it involves technology and areas I am most passionate about. ([View Highlight](https://read.readwise.io/read/01m3bbddh6zqkykxyy6wy4sdsm)) - Note: H1 / Z1 — Advocacy reframed as care work with technology as the medium; the thread's only generalisable claim, sitting in its least-read position. Fallacy (hasty generalisation, latent): a role's essential nature inferred from day one. The hedge "It still amazes my that" scopes it to first person and keeps it valid — fix is to cite it only with that scope, never as "developer advocacy is care work." Typo verbatim from source. - Tags: atom/literature/h1, action/h1, atom/zettel/z1, fallacy/hasty-generalization