Corporate Engineering Blog

A Byline implementation for a company engineering blog with official announcements and staff posts, all with proper affiliation disclosures.

What This Demonstrates

• Company organization element
• Team account as author ("The Acme Team")
• Individual employee authors
• Affiliation disclosures with job titles
• Different perspectives (announcement vs tutorial)

Transparency

Corporate blogs should always include affiliation information. Readers deserve to know when content comes from someone employed by a company discussing that company's products.

Full Example

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:byline="https://bylinespec.org/1.0">
  <channel>
    <title>Acme Engineering Blog</title>
    <link>https://engineering.acme.example.com</link>
    <description>Engineering insights from Acme Inc.</description>

    <byline:organizations>
      <byline:org id="acme">
        <byline:name>Acme Inc.</byline:name>
        <byline:url>https://acme.example.com</byline:url>
        <byline:type>company</byline:type>
        <byline:theme color="#6366F1" accent="#22D3EE" style="auto"/>
      </byline:org>
    </byline:organizations>

    <byline:contributors>
      <byline:person id="jamie">
        <byline:name>Jamie Rodriguez</byline:name>
        <byline:context>Principal Engineer at Acme. Working on distributed systems.</byline:context>
        <byline:url>https://engineering.acme.example.com/team/jamie</byline:url>
        <byline:avatar>https://engineering.acme.example.com/avatars/jamie.jpg</byline:avatar>
      </byline:person>

      <byline:person id="acme-team">
        <byline:name>The Acme Team</byline:name>
        <byline:context>Official posts from Acme Inc.</byline:context>
        <byline:url>https://acme.example.com</byline:url>
      </byline:person>
    </byline:contributors>

    <item>
      <title>Announcing AcmeDB 3.0</title>
      <link>https://engineering.acme.example.com/acmedb-3</link>
      <guid>https://engineering.acme.example.com/acmedb-3</guid>
      <pubDate>Wed, 15 Jan 2026 10:00:00 GMT</pubDate>
      <description>Today we're releasing AcmeDB 3.0...</description>

      <byline:author ref="acme-team"/>
      <byline:role>staff</byline:role>
      <byline:perspective>announcement</byline:perspective>
      <byline:affiliation>
        <byline:org-ref ref="acme"/>
        <byline:relationship>employed</byline:relationship>
      </byline:affiliation>
    </item>

    <item>
      <title>How we scaled to 10 million requests per second</title>
      <link>https://engineering.acme.example.com/scaling-10m</link>
      <guid>https://engineering.acme.example.com/scaling-10m</guid>
      <pubDate>Fri, 10 Jan 2026 10:00:00 GMT</pubDate>
      <description>Last quarter, we hit a milestone...</description>

      <byline:author ref="jamie"/>
      <byline:role>staff</byline:role>
      <byline:perspective>tutorial</byline:perspective>
      <byline:affiliation>
        <byline:org-ref ref="acme"/>
        <byline:relationship>employed</byline:relationship>
        <byline:title>Principal Engineer</byline:title>
      </byline:affiliation>
    </item>
  </channel>
</rss>

Key Elements

Team Author

Organizations can have a "team" author for official announcements. Create a person with a team name and make the relationship clear in the context.

Affiliation

Every post includes an affiliation element that references the organization and specifies the employed relationship. Individual posts can also include job titles.

Announcement Perspective

Product launches and official releases use the announcement perspective, while technical deep-dives use tutorial.