Features
WebsitesPortfolioMediaConservationClient deliveryCoursesCommerceTeam
FoundationSolutionsPricing
DocumentationDeveloper APISoftwareGuides
About
AboutCommitmentNewsroom
Sign In
ArtInStack

The creative operating system

Product

  • Features overview
  • Websites
  • Portfolio
  • Media
  • Conservation
  • Client delivery
  • Courses
  • Commerce
  • Team
  • Solutions

Resources

  • Guides
  • Software
  • Documentation
  • Developer API
  • Platform foundation
  • Pricing
  • Changelog
  • Roadmap

About

  • About
  • Commitment
  • Newsroom
  • Status
  • Talk to us

Customer login

© 2026 ArtInStack. All rights reserved.

Privacy policyTerms of service
All documentation

Discovery and distribution

  • How visitors discover your work
  • Publish an RSS feed for your blog
  • Preview your links when shared
  • Let visitors share on social networks
  • Reach Mastodon and the open web
  • Turn on Open Web Distribution
  • Choose what to share to the open web
Blog and Content MarketingNext: Email marketing
Documentation/Discovery and distribution

Choose what to share to the open web

Build a selective Open Web syndication strategy—what to share or skip, photos vs posts, captions for strangers, link destinations, cadence, and why automatic “share everything” is the wrong default.

After Turn on Open Web Distribution, you choose each post or photo. There is no library-wide “share everything.” That is intentional.

Use the Share control on the post editor or portfolio media item. The rest of this page is about what to choose and why.

What should be syndicated

  • Flagship portfolio frames that represent how you want to be found.
  • Stories with a clear home on your site (series page, blog post, booking).
  • Teaching or conservation posts you want strangers to finish on your domain.
  • Work you are willing to see cached on remote servers.

What should not

  • Client-confidential, embargoed, or unreleased commissions.
  • Vault-only or confidential portfolio work.
  • Vulnerable locations or private moments you would not put on a postcard.
  • Near-duplicates that dilute the feed.
  • Anything you are not ready to explain to a stranger with no studio context.

Photos vs posts

PhotosBlog posts
StrengthImmediate visual followDepth, SEO, longer stay
NeedsStrong frame + captionTitle + excerpt + public publish
Link homePhoto detail / seriesPost URL
Cadence tipFewer, stronger framesAlign with RSS writing rhythm

A healthy mix often works: photos attract follows; posts teach and convert.

Portfolio work that benefits from discovery

Public showcase collections with photo pages on, not hidden from search, and not confidential. Resource-only or private delivery collections are the wrong surface.

Choosing strong representative images

  • One readable subject at small size.
  • Consistent with the landing page the link opens.
  • Rights cleared (models, property, partners).

Writing captions and descriptions for outside your site

Assume the reader has never heard of you:

  1. Caption — the first line in Mastodon-style apps; story over filename.
  2. Description — optional context, series, or careful place names.
  3. Title — human label for the link home (avoid _DSC3084 when you can).

Linking back to the right destination

Prefer the URL that continues the story: photo detail with prints/contact, or the full post—not a generic homepage if a deeper page exists. Open-web links include UTM tags so your analytics can attribute fediverse traffic when configured.

How frequently to publish

  • Quality over volume.
  • A short series over thirty unrelated drops.
  • Pause when you have nothing worth caching remotely.

Why selective beats automatic everything

Automatic syndication trains remotes to ignore you and raises rights risk. Selective distribution keeps the follow worth something and matches the product philosophy: travel without surrendering the business to another platform’s content firehose.

Edits and removal

  • Edit caption/description → update when delivery succeeds.
  • Share off → deletion signal; caches not guaranteed.
  • Share on again after tombstone → new public object.

Checklist before Share on

  • Workspace Open Web Distribution is on; handle resolves in Mastodon search
  • Item is public the way you intend
  • Caption (and description if used) ready to be quoted elsewhere
  • Destination link is the right home on your site
  • You accept remote caching limits

Related documentation

  • Reach Mastodon and the open web
  • Turn on Open Web Distribution
  • How visitors discover your work
  • Publish and update blog posts
  • Photo detail pages