> ## Documentation Index
> Fetch the complete documentation index at: https://help.peernotes.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Articles: publish polished notes to your PeerNotes workspace

> Articles are polished notes published to your whole PeerNotes workspace — the moment private thinking becomes shared knowledge your team can read.

An **Article** is a note that graduated: refined, given a final read, and published for every member of your workspace. Articles are the output of the PeerNotes pipeline — the shared knowledge your team's private thinking was building toward all along.

Where thoughts are fast and messy and notes are working drafts, articles are deliberate. Publishing one says: *this is worth your time to read.*

## Publish an article

Any note can become an article when it's ready:

<Steps>
  <Step title="Open the note and select Publish">
    The publish dialog previews exactly how your article will appear — title, excerpt, and estimated reading time.
  </Step>

  <Step title="Decide whether the note stays visible">
    Choose whether readers can see the working note behind the article, or only the finished piece. Keeping the note visible lets teammates trace how the thinking developed; hiding it keeps the focus on the result.
  </Step>

  <Step title="Publish to your workspace">
    The article appears in the workspace's Articles feed, where every member can read it.
  </Step>
</Steps>

<Info>
  Articles stay connected to their notes. If the thinking evolves after publication, update the note and **republish** — the article updates in place rather than creating a duplicate.
</Info>

## Reading articles

The **Articles** feed is your workspace's library of finished thinking. Articles are tagged with [topics](/core-concepts/topics), so you can browse everything the team has published on a theme. Each article shows its author, reading time, and topic tags — enough to decide what to read next.

## Why publishing matters

It would be easy to leave everything as notes. The publish step exists on purpose:

* **It creates a quality bar.** Knowing an article goes to the whole workspace makes you tighten the argument one more time.
* **It separates signal from noise.** Teammates can follow the Articles feed alone and trust that what appears there is worth reading.
* **It makes knowledge durable.** Articles are the record a new teammate can read six months from now to understand how the team thinks.

<Card title="See the full pipeline" icon="diagram-project" href="/introduction">
  Sources → Thoughts → Notes → Articles: how the whole PeerNotes flow fits together.
</Card>