Skip to content

Comments

Scheduling — USF-2178#715

Open
bdenham wants to merge 24 commits intodevelopfrom
usf-2178-scheduling
Open

Scheduling — USF-2178#715
bdenham wants to merge 24 commits intodevelopfrom
usf-2178-scheduling

Conversation

@bdenham
Copy link
Collaborator

@bdenham bdenham commented Feb 2, 2026

Purpose of this pull request

This PR rewrites the Scheduling topic to clarify the different scheduling options available for Edge Delivery Services storefronts. The original page only described one workflow (crontab-based scheduling, now deprecated) and caused significant customer confusion. This rewrite presents all available scheduling approaches as a decision guide with a comparison table, clear merchant vs developer responsibilities, migration guidance for deprecated crontab users, and a callout for customers migrating from Commerce Content Staging.

Associated JIRA ticket

USF-2178

Staging preview

https://commerce-docs.github.io/microsite-commerce-storefront/merchants/edge-delivery-services/scheduling/

Affected pages

Links to source code

What's New highlights

whatsnew
Added Scheduling options — a decision guide covering four scheduling approaches for EDS storefronts: snapshot scheduling, promotion schedules, AEM Sites scheduled publishing, and recurring tasks. Includes a comparison table, merchant vs developer responsibilities, crontab migration mapping, and a Content Staging migration callout.

bdenham and others added 7 commits February 2, 2026 11:24
- Move scheduling.mdx from content-customizations/ to edge-delivery-services/
- Create edge-delivery-services/index.mdx overview page
- Fix broken link hash in boilerplate/getting-started.mdx
- Remove howitallworks.mdx (not in sidebar)

Co-authored-by: Cursor <cursoragent@cursor.com>
The custom LinkCard component uses 'link' not 'href' for internal links.

Co-authored-by: Cursor <cursoragent@cursor.com>
- Reduce scheduling content to brief intro with link to guide
- Use custom LinkCard component instead of Starlight's for proper base path handling

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
- Add use cases (product launches, promotions, coordinated releases)
- Explain the 4-step workflow
- List prerequisites for administrators

Co-authored-by: Cursor <cursoragent@cursor.com>
- Use active voice throughout
- Omit needless words ("exactly", "as usual")
- End complete sentences with periods in Steps list
- Use consistent list item structure
- Use "1." for all Steps items per markdown convention

Co-authored-by: Cursor <cursoragent@cursor.com>
@bdenham bdenham requested review from keharper and meker12 February 2, 2026 22:04
@bdenham bdenham self-assigned this Feb 2, 2026
@bdenham bdenham added the new-topic A major update published as an entirely new document label Feb 2, 2026
<Steps>
1. **Register your site**. A one-time setup enables scheduling for your organization and site.
1. **Create content**. Author your pages in Document Authoring (da.live) or your preferred tool.
1. **Schedule publishing**. Select the pages you want to publish together and set a future date and time.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
1. **Schedule publishing**. Select the pages you want to publish together and set a future date and time.
1. **Schedule publishing**. Select the pages you want to publish together and specify when they'll be published.

1. **Register your site**. A one-time setup enables scheduling for your organization and site.
1. **Create content**. Author your pages in Document Authoring (da.live) or your preferred tool.
1. **Schedule publishing**. Select the pages you want to publish together and set a future date and time.
1. **Automatic publishing**. Your content goes live at the scheduled time with no manual intervention.
Copy link
Contributor

Choose a reason for hiding this comment

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

This isn't really a step. Combine with the previous line.

@bdenham bdenham requested a review from keharper February 10, 2026 16:59
@bdenham
Copy link
Collaborator Author

bdenham commented Feb 10, 2026

Old content

@bdenham
Copy link
Collaborator Author

bdenham commented Feb 10, 2026

@keharper Thanks. Better now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new-topic A major update published as an entirely new document

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants