Create or revise
Open Articles and its submission page. To revise a public article, use its reading page’s revision action and compare with the current public version. Articles share the entry body editor, but articles do not create GitHub PRs. The site shows cloud drafts, proposals, and public versions as distinct states.
The article reader shows its revision action only to people with edit permission. Other readers see Write an article, which starts a new submission and does not change the article being read.
Complete and save a draft
Choose a title, content language, category, and body. Summary and linked entries are optional. An article may stand alone or explicitly link to several entries. Select the correct stable IDs for links; a WikiLink or ordinary body link does not automatically create a related-article relationship. Use formatting tools or source mode and preview the title, body, image URLs, and outline. Article images currently use existing URLs; entry attachments are not an article upload feature.
The current browser retains local editing state. After signing in, use Save draft to store a cloud draft. Read the save indicator before leaving: a local change is not automatically synchronized. Title and body must be ready before submission. Follow validation errors to the affected field or section.
Submit and follow review
Use Submit for review, wait for the receipt, then open the record in Creator Center. A pending or returned revision does not replace the existing public article. Publication follows maintainer approval in the article’s content language. If returned, read the note, edit, and resubmit. On a version conflict, compare your draft with the newer public version instead of silently overwriting another approved revision.
Worked editing example
For a standalone research article, choose its actual writing language and category, enter title, summary, and body, and leave linked entries empty. If the article discusses two tracks, explicitly select both stable IDs in Properties. A [[WikiLink]] in the body gives readers a link but does not put the article in either track’s related-articles list. Save a draft, refresh, confirm the cloud version in Creator Center, and then submit.
The article and entry share the visual body editor. Title and category live in Properties; article source mode handles the body only. Use the outline to move around long text and preview headings, links, and images. Article images currently use directly accessible URLs. Neither gallery uploads nor entry GitHub attachments attach a file to an article automatically. Never save a local blob: preview URL as article content.
Revising a public article
A revision starts from the approved version. Pending changes are visible to the author and reviewer; readers continue to see the old public version. If another revision is approved first, compare against the newer version and resubmit instead of overwriting it. Read a return note on the existing record and correct that document rather than creating a duplicate title.
Before publication
Check title, body, category, summary, image URLs and grounds for use, and all selected entry IDs. Follow the receipt to the review record. Publication is complete only when the new version opens in the public reader.