All guides
Admin

Documentation

Screen guide

Before you start

Use an administrator account with permission to manage this feature. The feature also needs to be enabled for this installation and plan.

Open this feature
  1. Open /docs on your site.

Steps

Use Save collection

  1. Open /docs on your application domain, using the administrator account for this task.
  2. Find the form containing Name, Product Logo, Order. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Save collection. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
NameEnter the name for this task, using the help or example shown by the form. The form’s example is Stackposts, Replix, Waziper.... Replace it with your own value.
Product LogoEnter the product logo for this task, using the help or example shown by the form. The form’s example is Logo URL or media path. Replace it with your own value.
OrderEnter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 0.
StatusChoose Public, Draft.
DescriptionEnter the description for this task, using the help or example shown by the form. The form’s example is Short summary. Replace it with your own value.

Use Save documentation

  1. Open /docs on your application domain, using the administrator account for this task.
  2. Find the form containing Untitled documentation, Add a short summary. This appears in cards and search results., Start writing your documentation.... Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Save documentation. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
Untitled documentationRequired. Enter the untitled documentation for this task, using the help or example shown by the form. The form’s example is Untitled documentation. Replace it with your own value.
Add a short summary. This appears in cards and search results.Enter the add a short summary. this appears in cards and search results. for this task, using the help or example shown by the form. The form’s example is Add a short summary. This appears in cards and search results.. Replace it with your own value.
Start writing your documentation...Enter the start writing your documentation... for this task, using the help or example shown by the form. The form’s example is Start writing your documentation.... Replace it with your own value.
StatusChoose Public, Draft.
CollectionRequired. Enter the collection for this task, using the help or example shown by the form.
OrderEnter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 0.

Fields and choices

Field descriptions appear beside each task above so that separate forms are not mixed together.

Check the result

  1. Stay in the same account/workspace and reopen the intended record or result screen.
  2. For saved settings, compare the displayed values with the choices you made. For filters and previews, check the current result scope.
  3. For queued or external work, inspect its status/history and provider result where applicable. A successful save does not by itself prove message delivery, publication, payment completion or provider approval.

Common problems

ProblemWhat to check
The screen or action is missingCheck the correct administrator account, role, enabled app and plan. A hidden action is not fixed by typing an internal endpoint.
A field is rejectedRead its validation message, choose from the offered options and check the relevant format or limit. Do not substitute a database ID for a displayed choice.
A list is emptyCheck the selected workspace, search text, date range and status filters. Clear one filter at a time before concluding that records are missing.
A request is still pendingCheck its status/history before repeating it. For messages, publishing, imports and payments, a submitted request can finish later or fail separately.

Technical reference

Role-scoped source references

Pinned commit: 275481cdd3c8519a24c5ecf5cac3e11ceb1708d8

Source-only route information
MethodSource-default route
GET/docs
GET/docs/{collectionSlug}
GET/docs/{collectionSlug}/{pageSlug}
RESOURCE/admin/documentation
POST/admin/documentation/list
GET/admin/documentation/create
GET/admin/documentation/edit/{id}
POST/admin/documentation/save
POST/admin/documentation/reorder
POST/admin/documentation/duplicate
POST/admin/documentation/status/{any}
POST/admin/documentation/destroy
GET/admin/documentation/collections
POST/admin/documentation/collections/save
POST/admin/documentation/collections/destroy
Unmapped fields — not user instructions

These fields belong to this role’s source handler, but their screen labels were not confirmed.

Source keyHandler
collection_idmodules/AdminDocumentation/app/Http/Controllers/AdminDocumentationController.php
titlemodules/AdminDocumentation/app/Http/Controllers/AdminDocumentationController.php
contentmodules/AdminDocumentation/app/Http/Controllers/AdminDocumentationController.php
statusmodules/AdminDocumentation/app/Http/Controllers/AdminDocumentationController.php
namemodules/AdminDocumentation/app/Http/Controllers/AdminDocumentationController.php
logomodules/AdminDocumentation/app/Http/Controllers/AdminDocumentationController.php
descriptionmodules/AdminDocumentation/app/Http/Controllers/AdminDocumentationController.php
sort_ordermodules/AdminDocumentation/app/Http/Controllers/AdminDocumentationController.php