theabbie.github.io

Growth on social media means building an audience that returns, trusts, and acts—not just accumulating followers. The practical path is consistent publishing, brand-focused storytelling, and reading the signals that show whether people actually engage. This explainer is for creators, marketers, and small brands who want durable audience growth rather than short-lived spikes from trend-chasing.

What "Growth" Actually Means

Follower count is the most visible number and the least useful on its own. A large audience that ignores your posts is worth less than a small one that reads, replies, and shares. Treat growth as a set of layered outcomes:

• Reach: how many people see a post.
• Resonance: how many stop, read, watch, or react.
• Retention: how many come back for the next one.
• Trust: how many act on what you say—click, subscribe, buy, recommend.

The Monday Growing newsletter frames this well: its case studies look at how brands turn habits, time, and small details into loyalty rather than chasing a single viral moment. Examples from its archive include Nintendo turning childhood habits into lifelong brand loyalty, LEGO treating unfinished play as imagination in progress, and Spotify turning a single UI detail into an emotional ritual. Each is a story about resonance and retention, not reach alone.

Content Habits That Build Lasting Trust

Publish on a rhythm you can sustain

Consistency beats intensity. A weekly post you can keep up for a year outperforms a daily sprint that dies in three weeks. Pick a cadence, then protect it.

Lead with a point of view, not a trend

Trends borrow attention; a point of view earns it. The brands in the Monday Growing archive—Aesop, Adidas, H&M, American Express—each anchor their content in a specific idea (craft, time, durability, what stays with you after payment) rather than whatever is trending that week.

Make the brand the throughline

Every post should be recognizably yours in tone, format, or subject. If a post could have been published by anyone, it does not build your audience—it builds the platform's.

Write for the reader who skips

The archive entry "Read What Others Skip" makes the point directly: treat copy as a product feature. Assume your audience is skimming, and give them a reason to stop.

A Repeatable Publishing Loop

1. Choose one idea per post. State it in the first line or first three seconds.
2. Match format to idea. A quick observation suits a short text post; a process suits a carousel or short video.
3. Publish on schedule. Same day, same time where possible—this trains both you and your audience.
4. Read the response within 48 hours. Note which posts got saves, replies, and shares, not just likes.
5. Repeat what resonated. Reuse the topic, angle, or format in a new post. Drop what did not.

The loop matters more than any single post. Growth compounds through repetition, not through one lucky hit.

Signals That Matter vs. Vanity Metrics

Track two or three of these per post, not all of them. A simple spreadsheet with date, topic, format, and one engagement signal is enough to spot patterns within a month.

Common Traps

• Chasing every trend. You compete with everyone and sound like no one.
• Posting without a point. Volume without a message trains people to scroll past.
• Judging a post in the first hour. Some content compounds over days; check again at 48 hours.
• Copying a bigger account's format. Their audience came for them, not the format.
• Quitting at week six. Most accounts that "failed" stopped before the loop had time to work.

Where to Go Deeper

The Monday Growing newsletter publishes weekly case studies on how brands grow through storytelling and consistency rather than hype. Its archive covers Nintendo, LEGO, Spotify, Aesop, Adidas, H&M, American Express, and others, each as a short, specific example you can adapt to your own content. A subscribe link is available on the site if you want the weekly edition.

Growth on social media is a habit, not a hack: pick a cadence, publish a clear point of view, watch what people save and share, and do more of that.

Contact Improvisation (CI) is a movement form built around two or more bodies sharing weight, momentum, and balance in real time. In Nicole Bindler's practice, it functions less as a fixed technique than as a research method: a way to study how a body listens, responds, and organizes itself in relation to another body. Her work sits at the intersection of CI, new dance, dance-theater, Butoh, and Body-Mind Centering (BMC), and she treats these as interwoven rather than separate disciplines.

The Core Principles of Contact Improvisation

CI emerged as a dance form in which the point is not to execute set steps but to follow the physical facts of the moment. A few principles define it:

• Shared weight. Dancers give and receive weight, using contact points (back, shoulder, hip, hand) as pivots rather than grips.
• Momentum over muscle. Movement is generated by falling, rolling, and redirecting mass, not by lifting or holding.
• Continuous listening. Each dancer tracks pressure, direction, and speed through touch, adjusting before a shape is consciously chosen.
• No fixed roles. Leading and following shift constantly; neither partner owns the movement.

Because there is no choreography to memorize, the form depends on attention. That is why CI is often described as an improvisational practice rather than a style.

How Nicole Bindler Approaches the Form

Bindler is a body-based performing artist whose training spans new dance, dance-theater, Contact Improvisation, Butoh, and BMC. In her practice, CI is not isolated from those other trainings — it is a meeting point for them.

BMC and the "Body as Material"

Body-Mind Centering contributes a detailed map of bodily systems: skeletal, organ, fluid, endocrine, and developmental movement patterns. In a CI context, this means a dancer might track, for example, how weight travels through bone versus how it moves through fluid, and let that distinction change the quality of the contact. The result is a CI that is informed by anatomy rather than only by shape.

Butoh and Slowness

Butoh's influence shows up in tempo and image. Where CI can become fast and athletic, a Butoh-informed approach may slow the same movement down until the internal image — not the external form — becomes the visible content. For Bindler, this expands what counts as "contact": contact with an image, a memory, or a state of body can be as consequential as contact with a partner.

Improvisation as Composition

Her background in experimental and contemporary dance means improvisation is treated as a compositional act, not a warm-up. A duet can be read as a piece, with its own logic of tension, repetition, and resolution.

Why This Matters for Viewers and Students

If you are watching or studying this kind of work, the useful question is not "what steps are they doing" but "what are they tracking." Some practical entry points:

• As an audience member: watch the points of contact and the direction of weight. Notice when a shape is chosen versus when it arrives on its own.
• As a mover: practice with a single intention — for example, "follow the fall" — rather than trying to perform.
• As a researcher: pair studio time with somatic study (BMC, developmental movement) so the vocabulary of sensation has somewhere to land.

Where to Find Her Work and Thinking

Bindler's own site points to several accessible sources:

• Forthcoming publications: essays on embodied embryology and Palestinian dance are slated for the Embryo Book Project, co-edited by Kim Sargent-Wishart, Amy Matthews, and Rebecca Haseltine; and Gathering Sparks: Jewish Arts and Somatics, co-edited by Nicole Bindler, Kristen Smiarowski, and Ben Spatz, to be published by punctum books.
• Interviews: conversations about her perspectives on performance and improvisation appear via thINKingDANCE, the ACT/RE/ACT Podcast, and Cannoncast.

These are the most direct routes into how she frames CI in relation to somatics, performance, and politics. For anyone trying to understand the practice rather than just the label, the interviews are the fastest starting point; the publications go deeper into the somatic and cultural questions that shape her teaching.

A portfolio is a curated collection of work samples that demonstrates what you can do, rather than describing what you have done. It differs from a personal blog, which is a running record of thoughts and updates, and from a resume, which is a chronological list of roles and skills. If your goal is to prove capability to a client, employer, or collaborator, a portfolio is the right format; if your goal is to share ongoing ideas or apply for a job through a formal hiring pipeline, a blog or resume may serve that purpose better.

The core purpose of a portfolio

A portfolio answers one question: can this person actually do the work? Everything in it should support that answer.

• It shows, not tells. Instead of "skilled in JavaScript," a portfolio shows a working project.
• It is selective. A portfolio with three strong projects beats one with twenty weak ones.
• It is audience-facing. You choose what to include based on who will look at it.

This is why portfolios are common among software developers, designers, photographers, writers, and freelancers — roles where the quality of output matters more than a job title.

Portfolio vs. personal blog

These two often live on the same website, which is why they get confused. The difference is in intent and structure.

A blog can feed a portfolio — a post explaining how you built a project can link to the project itself. But a blog post is not a portfolio entry unless it demonstrates a concrete result.

Take Humnom.net, the personal site of software developer Yuri Sizov. Its description pairs "his portfolio and blog" as two distinct sections. That split is typical: the portfolio holds the work, the blog holds the writing. Keeping them separate helps a visitor who only wants to evaluate your work skip past the commentary.

Portfolio vs. resume

A resume is a summary; a portfolio is evidence. They are not substitutes.

• A resume lists. "Developed a REST API for internal tooling, 2022–2023."
• A portfolio demonstrates. A link to the API, a description of the problem, the constraints, and what changed as a result.

Use a resume when a formal process requires a standardized document — most job applications. Use a portfolio when you have room to show depth, such as a freelance pitch, a portfolio review, or the "website" field on an application.

A practical pattern: the resume states the claim, the portfolio backs it up. If a resume line says "built a game in Godot," the portfolio entry shows the game, the mechanics, and what you learned building it.

What a portfolio usually contains

Most effective portfolios include the same basic elements, regardless of field:

1. A short introduction — who you are and what kind of work you take on.
2. Project entries — each with a title, the problem or goal, your role, the process, and the outcome.
3. Visual or interactive evidence — screenshots, live demos, repositories, or published pieces.
4. Context on constraints — timeline, team size, tools, or client requirements, so the work is judged fairly.
5. Contact information — how to reach you, stated plainly.

For a developer, an entry might link to a repository and a live demo. For a designer, it might show before-and-after states. For a writer, it might include published clips with links to the original outlet.

Choosing the right format for your situation

The right combination depends on what you need the reader to do.

• Software developer applying to jobs: resume for the application, portfolio site for depth, blog optional. Link the portfolio from the resume.
• Freelancer or contractor: portfolio first, since clients evaluate output directly. A blog can build trust but is secondary.
• Designer or creative: portfolio is essential; a resume alone rarely conveys visual or craft quality.
• Someone building an audience: blog first, with a portfolio page for finished work you want to highlight.

If you are unsure, start with a single page that lists three projects with links and a short paragraph each. That is a functioning portfolio. You can add a blog later if you find you have things to write about regularly.

Common mistakes to avoid

• Treating the portfolio as an archive. Not everything belongs. Curate.
• Describing the project without showing it. A paragraph about a game is weaker than a paragraph plus a playable link or screenshots.
• Mixing blog and portfolio so thoroughly that neither is clear. Separate sections, or at least clear labels, help visitors find what they came for.
• Leaving out the outcome. State what the work achieved or what you learned, not just what you did.

A portfolio is not a diary and not a CV. It is a focused argument, made with work, that you can do the thing you say you can do.

Stuff (stuff.co.nz) is a New Zealand news site covering national and world breaking news, video, audio, podcasts, sport, rugby, politics, business, entertainment, lifestyle, travel, and property. Use it when you want NZ-focused reporting in one place; go straight to its section pages or search if you already know the topic, and use the homepage when you want to scan what's breaking.

Getting to the site and reading the homepage

Open stuff.co.nz. The homepage is built for scanning rather than reading top to bottom:

• Lead stories and breaking news sit at the top, so the most recent or most important items are visible first.
• Video and audio/podcast content is surfaced alongside written stories rather than hidden in a separate app.
• Section links let you jump from general news into a specific topic without scrolling the whole page.

If you arrive for a specific reason (a sport result, a political story), skip the homepage and go directly to that section.

Finding the main sections

Stuff organizes coverage into clearly named verticals. The ones named in the site's own description are:

Use the section navigation to move between these. Each section behaves like its own feed, so once you're inside Sport or Politics you can keep scanning that topic without returning to the homepage.

Locating a specific story

When you know what you're looking for, two tools do most of the work:

1. Search — enter a keyword, name, or place to pull matching stories. This is the fastest route when you remember a headline or subject but not its section.
2. Navigation menus and filters — use the section menus to narrow by topic, and region or topic filters where they're offered to cut a national feed down to what's relevant to you.

A practical sequence: search first for a known story; if you're browsing rather than hunting, pick the section, then apply a region or topic filter to reduce noise.

Video, audio, and podcasts

Stuff treats video and audio as first-class content, not add-ons. They appear within the site's coverage and have their own organization, so you can:

• Watch video clips attached to news stories or collected under video.
• Listen to podcasts and audio content grouped together rather than scattered.

If you prefer listening or watching over reading, start from the video or audio/podcast areas instead of the text homepage.

Free news vs. anything gated

The site's description presents Stuff as a general news destination covering all the sections above. The available information does not specify any subscription tier, paywall, or login requirement for Stuff content, and no pricing signals are given. That means:

• Treat the news, video, audio, and podcasts described here as the site's standard offering.
• Don't assume a paid tier exists, and don't assume everything is unrestricted either — the source material simply doesn't state access terms.
• If you hit a prompt asking you to sign in or subscribe, follow that on-screen instruction; it's the only reliable signal of what's gated at that moment.

For free news, the section pages and homepage are the natural starting points, since that's where the site's described coverage lives.

A quick workflow

• Just want today's news: open the homepage and scan the top.
• Following one topic: go straight to that section (Sport, Politics, Business, etc.).
• Looking for something specific: use search, then refine with region or topic filters.
• Prefer watching or listening: head to the video or audio/podcast areas.
• Checking access: if a login or subscription prompt appears, respond to it there — the site's public description doesn't define a paywall.