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

Document opening the add page data form with defaults (?parentPage, ?parentPageData, ?template)

Open Beginner friendly
#230 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
70/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

The payload names no file, so start by finding the docs page that covers the admin add page data form, and check whether it already mentions query parameters. Document ?parentPage, ?parentPageData and ?template, and call out that template is not page (which is the list pagination parameter) and that the route is set on the Routes tab after saving. Done when a reader can pre-fill the add form from a link and knows these parameters are ignored when editing an existing page data.

Written by the indexing model from the issue text.

Description

documentation

From cwa-nuxt-module #390 (066433f6, unreleased after 2.0.0-alpha.14).

An app can link editors to the admin's add page data form with fields filled in:

  • ?parentPage=<page iri> or ?parentPageData=<page data iri>: the parent
  • ?template=<template page iri>: the template (the form's page field)

Example: an "Add a training module" button on a module page links to the add form for that page data type with ?parentPage=<module page iri>&template=<module template iri>.

Notes for the docs:

  • It's template, never page: ?page= is the admin list's page number.
  • The route path isn't a page data field, so it can't be pre-filled. The route is added on the Routes tab after saving.
  • Only applies when adding; an existing page data ignores them.
Dominant language
Vue
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: 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.