Routing decision

這不是單篇 blog request，而是內容營運系統。Idea backlog 同時包含技術與商業 reader value，因此每筆資料各自記錄 channel：技術實作型 article 預設 Ghost + Hashnode，商業／策略型 editorial 預設 Ghost + LinkedIn，PDF／worksheet 則進入 Resource Hub + ABM nurture。沒有執行任何外部發佈。

為什麼不是只有 300 個標題

每筆 idea 都綁定：

• 一個 ICP segment 與 persona。
• TOFU/MOFU/BOFU 及 Discover、Explore、Validate、Select、Scale 五階段。
• Content pillar、asset type、format group、delivery 與 ABM motion。
• Business problem、內容切角、primary query、CTA 與 conversion event。
• Required evidence、proof state、effort 與四因子 priority score。
• 完整英文與繁體中文標題、問題、切角、keyword 與 CTA。

這讓 dashboard 能回答「下一個應該做什麼、為誰做、為何現在做、缺什麼證據」，而不只是儲存靈感。

Priority model

Priority score = Customer impact × 40% + Content-market fit × 30% + Search potential × 20% + Resource feasibility × 10%

每項先評 0–10，再轉為 0–100。這是 backlog prioritization，不是預測流量、pipeline 或 revenue。缺 internal benchmark、customer authorization 或 partner validation 的 idea 仍可保持高策略價值，但不能因此跳過 evidence gate。

ABM stage model

Journey stage	Buyer question	Default next action
Discover	Why does this production problem exist?	Read the Architecture Checklist
Explore	Which architecture path fits?	Check Source Compatibility
Validate	How can the path be tested?	Request Compatibility Validation
Select	Who should own the design-in risk?	Request an Architecture Review
Scale	How will the design survive production changes?	Plan a Design-In Review

Salesforce's ABM guidance emphasizes account selection, personalized content, channels and measurement; Demandbase frames stages around the buyer journey; 6sense maps useful content to buyer stage. The implemented fields translate those principles into YUAN's design-in motion.

Programmatic and AI-search guardrail

300 ideas are not 300 approved URLs. Google explicitly warns against scaled pages that add little value, regardless of whether AI generated them. An idea becomes publishable only after it adds a distinct method, diagram, evidence set, decision tool or authorized story and passes the bilingual review checklist.

For Google AI features, the strategy follows normal people-first SEO. Extractable tables, direct answers and evidence help clarity, but no special “AI-only” copy or markup is assumed.

Bilingual decision

The internal dashboard uses an English／繁中 segmented control and preserves the active filters, sort and page when language changes. It switches all dashboard labels and localized idea fields.

If content is later published publicly, use separate locale URLs and reciprocal hreflang; do not use the internal toggle as the public SEO architecture.

Primary references

• Salesforce ABM strategy: https://trailhead.salesforce.com/content/learn/modules/einstein-account-based-marketing/build-your-einstein-account-based-marketing-strategy — accessed 2026-08-25.
• Demandbase journey stages: https://www.demandbase.com/resources/roi-cookbook/recipe-journey-stages/ — accessed 2026-08-25.
• 6sense buyer-stage content: https://6sense.com/blog/creating-content-for-each-stage-of-the-buyers-journey/ — accessed 2026-08-25.
• Google people-first content: https://developers.google.com/search/docs/fundamentals/creating-helpful-content — accessed 2026-08-25.
• Google scaled-content policy: https://developers.google.com/search/docs/essentials/spam-policies — accessed 2026-08-25.
• Google multilingual guidance: https://developers.google.com/search/docs/advanced/crawling/managing-multi-regional-sites — accessed 2026-08-25.