Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Scheduling a component publish from the Publish tab

Open Beginner friendly
#99 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Domain
documentation

Research direction

Start with the admin Publish tab workflow described in the issue and the existing publishing documentation. Document scheduling alongside immediate publishing, including the editor time zone and UTC behavior; done means the scheduling, cancellation, override, and timing behavior are clear to admins.

Written by the indexing model from the issue text.

Description

documentation

Source: components-web-app/cwa-nuxt-module#320 (step 1).

What changed

The admin Publish tab can schedule a draft to go live later.

  • For a draft, a Publish at field (date and time) and a Schedule button. The field doesn't offer past times. A time that has already passed when saved publishes immediately, the same as the Publish button.
  • Times are entered in the editor's computer time zone, which is shown under the field, and saved as UTC.
  • A scheduled draft shows Scheduled for <date> and a Cancel schedule button, which clears the date so it stays a draft.
  • The Publish button still publishes immediately, overriding a schedule.
  • Live pages switch at the scheduled time (the API limits cache lifetimes to it). An admin who already has the page open sees the change on their next load.

To document

The scheduling workflow alongside publishing, and the time zone behaviour. A dedicated date picker replacing the browser's own control follows in step 2 of #320.

Dominant language
Vue
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from components-web-app/docs

All issues in components-web-app/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.