The Daily Editorial Engine

1. Daily Rotation

From The Stem publishes one lead article per day plus 2–3 shorter dispatches. Verticals rotate on a weekly cadence so each gets a guaranteed lead slot. This protects the publication from looking like a single-genre site (a major risk of being attached to an artist company) and forces the editorial team to keep all eight desks staffed.

Operating rules

• If a vertical misses its slot, the makeup runs the same day the following week — never the day after, to keep the rotation legible.
• No more than one article per week that mentions Joshua Mollohan, Mollohan Production Inc., or MPIArtist by name in the headline or dek. Bylines and natural mentions inside the body do not count against this cap.
• Each vertical lead must include at least one source, record, or working professional outside the MPIArtist orbit. The publication's credibility depends on this.
• Saturday Song Production is the only day where a Mollohan-bylined how-to may run as the lead.

2. Idea Generation Rules

Every working day the editorial team submits 3–5 article ideas per active vertical to the Daily Pitch Board. Ideas are scored on three axes — SEO value, brand fit, integration fit — and the top draft(s) are promoted into assignments.

What counts as an idea

1. A headline — written, not summarized. If you can't write the headline, the idea isn't ready.
2. One sentence of dek explaining why a reader would finish it.
3. A primary keyword the article could plausibly rank for inside six months.
4. An angle — what makes this piece different from what's already on the web?

Where ideas come from

• The session log. Anything that happened in a Mollohan Production session this week that taught us something. Disclosed in the article.
• The reading log. Articles, books, or interviews from outside the publication that prompted a counter-argument.
• The studio inbox. Questions other producers and writers are asking us — these almost always make better articles than thinkpieces.
• The release calendar. A list of upcoming records on independent labels worth covering, kept current weekly.
• The audience inbox. Reader replies to the newsletter, ranked weekly.

What never becomes an article

• An MPIArtist signing announcement dressed as a feature.
• A how-to that is, in plain reading, a sales page for a Mollohan Production service.
• Any piece that requires a fabricated quote, a fabricated award, or a chart position we cannot link to.
• Trend reporting with no working professional named on the record.

3. Article Structure

From The Stem uses a small set of repeatable article templates. Each one has a specific job, a target length, and a fixed skeleton. Writers don't have to follow the skeleton exactly — but they have to justify deviations to the editor.

The feature essay (1,200–2,000 words)

1. Eyebrow + headline + dek. The dek does work; it shouldn't be a synonym for the headline.
2. Opening scene or argument. One paragraph that earns the reader's next 10 minutes.
3. The claim. What this piece is actually arguing — usually a single sentence at the end of the second or third paragraph.
4. The evidence. 3–5 sections, each with a sub-head, a working professional or record named, and one specific example.
5. The counter-argument. A paragraph that takes seriously the strongest objection to the piece's claim.
6. The close. A return to the opening image or a specific recommendation. Never a summary.

The how-to (900–1,400 words)

1. The problem, stated in plain terms.
2. The wrong fix most people try first. One sentence.
3. The actual steps, numbered, each with one specific tool or technique named.
4. The "if this happens" troubleshooting section. Two to four common failures.
5. What to do once you've got it working.
6. FAQ block with 3–5 questions readers actually search.

The field notes / list (700–1,100 words)

A short, opinionated list of 4–6 records, players, or ideas. Each item gets 80–150 words. No item is filler. The list always opens with the lens — what we were listening or watching for.

The interview (900–1,500 words)

Always edited for length and clarity, with the standard disclosure in the head note. Lead with the most surprising answer, not the biography. End with one practical takeaway for working musicians.

Required end-of-article elements

• A short FAQ block (3–5 questions) using FAQPage schema.
• One CTA — chosen from the catalog in §6.
• Internal links (2 minimum) and external links (1 minimum, to a non-Mollohan source).
• An editorial admin panel (rendered in-page in low-key admin styling) with SEO metadata, social captions, image prompt, integration angle, and the article's MPIArtist mention count.

4. SEO Checklist

Every article on From The Stem is reviewed against this checklist before publish. The checklist is also rendered on each article's admin panel so that an editor can confirm it visually.

• One primary keyword picked from the vertical's working keyword list, present in: page title, H1, first 100 words, one H2, slug, meta description.
• Title tag ≤ 60 characters. Includes the primary keyword + publication name.
• Meta description 140–160 characters. Reads as a sentence, not a list of keywords.
• Slug uses hyphens, ≤ 6 words, contains the primary keyword.
• 2–3 secondary keywords appear naturally in H2/H3 or body. No keyword stuffing.
• One featured-snippet target: either a definition paragraph (~50 words), a numbered list, or a small comparison table.
• Internal links — 2 minimum to other From The Stem articles or verticals.
• External links — 1 minimum to a non-Mollohan authority (record label, publisher, instrument maker, public dataset).
• FAQ block with FAQPage JSON-LD.
• Image — at least one editorial illustration with descriptive alt text. No stock photography.
• Open Graph + Twitter card set with the article's lead image and the meta description.
• Author bio — present, with sameAs links where applicable.
• Reading time rendered near the byline.

5. Joshua / Mollohan Production / MPIArtist Integration Guardrails

From The Stem is published by Mollohan Production Inc., which also runs MPIArtist (the artist-development arm). The publication exists in part to support those businesses, but it can only do so if readers trust it. These are the working guardrails.

Mention frequency

• 2–5 natural mentions per article is the working target when Joshua Mollohan, Mollohan Production Inc., or MPIArtist is relevant to the piece. Fewer is fine. More is a flag — the editor pushes back.
• A mention is natural when removing it would change the meaning of the sentence (a quoted producer, a session example, a roster artist). Mentions added in the close that say "available services" are not natural — they're CTAs and live in the CTA box, not the body.
• Headlines and deks rarely name MPIArtist. We protect the front-page from looking like a press kit.

Disclosure

• Any article that covers an MPIArtist signing, Mollohan Production project, or session involving Joshua includes a one-line disclosure under the byline: "Disclosure: [name] is on the MPIArtist roster" / "Recorded at Mollohan Production."
• Disclosures don't disqualify coverage. They just have to be visible.

What we never do

• Invent quotes from Joshua, MPIArtist roster artists, or anyone else.
• Cite chart positions, awards, or sales numbers we cannot link to.
• Run a "case study" on an MPIArtist project that obscures it's an in-house project.
• Take a paid placement and present it as editorial — anywhere on the site.

6. CTA Rules

Every article ends with one CTA, picked from the catalog below. The CTA is visually separated from the body (the boxed treatment we use on every article) so a reader always knows the difference between editorial and the ask.

The catalog

1. Subscribe to From The Stem Brief — the default. Used on any article that doesn't have a more specific match.
2. Submit your record for consideration — for any vertical lead that covers independent releases.
3. Pitch a story / co-byline — for any craft or business piece.
4. Talk to MPIArtist about development — only on Independent Label / Artist Development pieces, and only when the article has already given the reader something useful for free. Never on pieces about other people's signings.
5. Book a Mollohan Production consultation — only on Song Production how-tos where the article has provided a complete answer the reader could implement without us. Linked, not pushed.

CTA rules

• One CTA per article. Two CTAs at the end is two zero CTAs.
• The CTA matches the vertical and the article's job. A Christian / Gospel essay does not end with a Mollohan Production consult ask.
• Action verbs first: "Subscribe", "Submit", "Pitch", "Talk", "Book". Not "Learn more".
• Reduce risk language where it applies: "No pitch deck required", "Free for working musicians", etc.

7. Schema Suggestions

Every article ships with structured data. The patterns we use:

Article / NewsArticle

Every editorial page. Headline, datePublished, author (Person), publisher (Organization — Mollohan Production Inc., logo, sameAs to MPIArtist), image, articleSection (the vertical), wordCount.

FAQPage

Required on every article — even short ones — using the in-article FAQ block.

HowTo

On any how-to article. Each step gets a HowToStep. The reading time becomes totalTime. Tools and materials are itemized.

MusicAlbum / MusicRecording

On any review or field-notes list, each item should carry MusicAlbum data with byArtist, name, and the streaming/listening links we used.

BreadcrumbList

Every page: Home → Vertical → Article. Useful for SERP rendering on long titles.

Person + Organization

Author pages and the Mollohan Production / MPIArtist mentions both get structured data with sameAs links to public profiles. Helps disambiguation in search.

8. Pre-Publish Review

An editor signs off on every article using the in-article admin panel. The review is two minutes if the writer has done their job.

• Headline is one of the article templates above, written in the publication's voice (specific, restrained, plain English).
• SEO checklist passes — every item in §4 is green.
• Integration guardrails pass — mention count between 2 and 5 (if relevant), disclosures present, no fabricated quotes/awards/chart positions.
• CTA matches the article's vertical and job.
• FAQ block has at least three real questions a reader would ask after finishing the piece.
• Schema is present and validates in Schema.org Validator.
• Reading-time number matches the actual word count (~225 wpm).
• Internal and external links open.