AWS Builder Article

AWS Builder Center Article Publishing Guidelines

This page defines article publishing requirements and content standards for AWS Builder Center submissions to ensure consistent, educational, and compliant AWS learning content.

Guideline Article Series

English 繁體中文 简体中文
  • Article 1: AWS Builder Center Article Publishing Guidelines

Purpose

This document defines the publishing requirements and content standards for articles submitted to AWS Builder Center. Authors should follow these rules for consistency, educational value, and platform compliance.

Publishing Requirements

1. Do Not Use AWS Logo Banners

Banner and header artwork should not use official AWS logos or modified AWS branding. Use neutral visuals such as architecture illustrations or compliant custom graphics.

2. Canonical URL Must Not Point To Personal Websites

Canonical URLs must not redirect to personal blogs or private domains. AWS Builder Center should remain the authoritative publication source.

3. Article Titles Must Include An AWS Service Name

Each title should explicitly mention at least one AWS service central to the article topic.

4. Titles Must Focus On Use Cases

Titles should present practical implementation scenarios and learning outcomes, not claims of official best-practice guidance.

5. Descriptions Must Highlight AWS Service Benefits

Article summaries should describe learner-facing value such as scalability, reliability, automation, performance, or operational efficiency.

6. Include An Educational Disclaimer

Articles should clearly state that content is for learning purposes and may require adaptation before production use.

7. Include Technical Demonstrations

Include at least three technical demonstrations, such as code snippets, architecture workflows, or configuration examples.

8. Do Not Use AI-Generated Images

Use self-created diagrams, screenshots, or manually produced visuals rather than fully AI-generated images.

9. Avoid Finance And Trading Terminology

Keep content focused on cloud education and avoid finance-market vocabulary.

10. Do Not Display Demo Environment Images

Do not include screenshots of demo business outputs. Visuals should emphasize AWS architecture and service configuration learning.

11. Do Not Provide Demo Links

Do not publish links to hosted demos, public endpoints, or operational proof-of-concept systems.

12. Do Not Explain Demo Business Details

Keep discussion focused on AWS services and technical concepts, not commercial business logic behind demonstrations.

13. Self-Identify As An AWS Builder

Author identity should be AWS Builder, cloud practitioner, developer, or learner.

14. Publish Only One Language Version

Publish one language version per article to avoid duplicate multilingual submissions.

15. Do Not Use "Workshop" In Titles

Titles should focus on services and use cases without including the word "Workshop".

16. Do Not Include Workshop Timelines

Avoid timeline-based training agenda content; keep material self-paced and technical.

17. Publish No More Than One Article Per Day

Limit publication frequency to maintain quality and support review workflows.

Content Writing Standards

18. Position Content As AWS Service Learning Material

Write content as educational AWS service learning material with practical implementation context.

19. Maintain Beginner-Friendly Guidance

Use clear language, step-by-step flow, and simplified explanations while preserving technical correctness.

20. Encourage Exploration Of New AWS Services

Help readers understand emerging AWS services and motivate further hands-on learning.

Compliance Checklist

  • No AWS logo banners are used.
  • Canonical URLs do not point to personal websites.
  • Title includes at least one AWS service name.
  • Title focuses on a practical use case.
  • Description highlights AWS service benefits.
  • Educational disclaimer is included.
  • At least three technical demonstrations are provided.
  • No AI-generated images are used.
  • No finance or trading terminology appears.
  • No demo screenshots are included.
  • No demo links are provided.
  • No demo business details are explained.
  • Author identity is presented as AWS Builder.
  • Only one language version is published.
  • Title does not include the word "Workshop".
  • No workshop timeline information is included.
  • No more than one article is published per day.
  • Content remains educational and AWS-focused.
  • Content remains beginner-friendly.
  • Content encourages AWS service learning.

Version: 1.0

Purpose: Standardized publishing and content quality guidance.