Skip to content

Clarify Blog Articles content guidelines#2514

Merged
mishig25 merged 1 commit into
mainfrom
blog-articles-content-guidelines
Jun 1, 2026
Merged

Clarify Blog Articles content guidelines#2514
mishig25 merged 1 commit into
mainfrom
blog-articles-content-guidelines

Conversation

@mishig25

@mishig25 mishig25 commented Jun 1, 2026

Copy link
Copy Markdown
Collaborator

Adds a Content Guidelines section to the Blog Articles docs page describing the two categories a published article should fall into:

🤖 Generated with Claude Code


Note

Low Risk
Documentation-only change with no runtime, API, or security impact.

Overview
Adds a Content Guidelines section to docs/hub/blog-articles.md, placed after the creation flow and before Editing an Article. It states that published Hub blog posts should be either concept/engineering explorations or announcements of open-source models, datasets, or tools, with example links for each category.

Reviewed by Cursor Bugbot for commit 68258af. Bugbot is set up for automated code reviews on this repo. Configure here.

Add a Content Guidelines section to the Blog Articles page describing
the two expected article categories — exploring an AI science/engineering
concept, or announcing the release of an open source artifact — each
with example articles.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@mishig25
mishig25 requested a review from gary149 June 1, 2026 13:56
@HuggingFaceDocBuilderDev

Copy link
Copy Markdown

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@julien-c julien-c left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not

@mishig25
mishig25 merged commit 76ea1ae into main Jun 1, 2026
3 checks passed
@mishig25
mishig25 deleted the blog-articles-content-guidelines branch June 1, 2026 14:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants