Support WDguide

ARC RAIDERS / GUIDE

How to create a guide

From a blank page to a useful, illustrated guide: choose blocks, write clearly, add images and @items, save privately and send a revision for review.

Editor reference

Start with one useful promise.

A good guide helps a specific reader complete a specific task.

  1. 01

    Choose the right game

    Sign in with Discord first to create or edit a guide or build. This reference is set to ARC RAIDERS. Start a new Guide opens a separate blank guide for this game. Your existing drafts stay intact. In Equipment, choose Use browser loadout to copy a kit saved in this game’s loadout tool into the current variant. The original browser kit stays separate. You can also choose Create a Community build in the loadout tool to start a private build with that kit already copied. Shared kit links open a summary first; Edit a private copy keeps your existing working kit in the browser library.

  2. 02

    Name the result

    For a build, use the Build details panel to add its title, description and group size; the save status appears in the same panel. Choose up to three Playstyle tags to help readers find it in Community. Tag choices are managed separately for each game. Use a clear title, such as “Prepare for your first run”. Add a short summary explaining who the guide is for and what they will learn. Keep advanced details for later sections.

  3. 03

    Plan a small outline

    Start with preparation, the main task and a final checklist. Add a section only when it helps the reader make a decision or take an action.

Choose the block that fits.

Choose + Add section. The small previews show how each layout will look.

Explainer cards

Use cards for related choices or comparisons. Give each card a short heading and one main idea. This section is a working example of explainer cards.

Numbered steps

Use steps when order matters: prepare, act, check. Start each step with an action and explain what success looks like.

Callout

Use a Note for context, a Tip for helpful advice and a Warning for a real risk. Keep callouts short so they stand out.

Text, tables and diagrams

Use Text for explanations, Table for comparable information and Flow diagram for connected stages. Avoid turning every paragraph into a different block.

Write, format and organise.

Click the text you want to change to open its writing panel.

  1. 01

    Make it easy to scan

    Use descriptive headings, short paragraphs and lists. Use bold for important actions or conditions rather than highlighting entire paragraphs. Ctrl/Cmd+B applies bold in the writing panel.

  2. 02

    Watch the save status

    The writing panel shows its save status and which card you are editing. Done editing closes it. Revert this edit restores the text you started that edit with. If saving fails, keep the panel open and retry before leaving.

  3. 03

    Put sections in a useful order

    Organise sections from Contents. Use the section and card controls to move content. Check that preparation comes before actions and the final checklist comes last. Undo can recover a recent change.

Use an image that explains the topic.

Choose a guide cover and add an Image section where a screenshot explains an action. Add a useful caption and adjust its position. This example game cover shows the game; use a task-specific screenshot for instructions.
Choose a guide cover and add an Image section where a screenshot explains an action. Add a useful caption and adjust its position. This example game cover shows the game; use a task-specific screenshot for instructions.

Link real items instead of repeating their details.

Type @ and part of an item name in the writing panel, then choose the matching suggestion. The reference opens the game catalogue entry. Use Popup card group when several related items deserve their own image and detail popup.

Keep the picture relevant.

Preview, save and submit.

Saving a draft and releasing a guide are separate actions.

  1. 01

    Read it as a player

    Choose Preview guide. Check the cover, headings, card order, images, @items and popups. Read the page on a phone too. Remove repeated text and explain any terms a new player may not know.

  2. 02

    Keep a device copy

    Browser autosave stays on this device. Use Save & share → Save on this device for an explicit save, and check for any save error. Signing in does not upload drafts automatically.

  3. 03

    Save across devices

    While signed in with Discord, choose Save & share → Save to account. Account copies are private. Opening an account creation in the editor makes a separate working draft; save your revision back to the account when ready.

  4. 04

    Ask for guide review

    Open My creations, find Your guide reviews, select a saved Guide and choose Submit for approval. Only WildWire can approve guides; builds use their separate publishing flow.

  5. 05

    Respond to feedback

    Open Feedback, edit & resubmit, read the feedback, edit a working copy and save it to your account. Select that saved revision and resubmit. The previous approved version stays readable until its replacement is approved.

Know what becomes visible.

Your final check.

  • The title promises one clear result.
  • Preparation, actions and checks are in a useful order.
  • Cards compare ideas; steps explain a sequence; callouts highlight something important.
  • Images match their topics, captions are helpful and @items open the correct catalogue entry.
  • Uncertain information is labelled; unsupported stats are removed.
  • The guide reads clearly on a phone.
  • The latest revision is saved to the account before submission.

Use this guide as a layout reference. Open reference in editor opens a local revision of this reference; it does not create your own new submission. Start your own blank guide when you are ready.