Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Docs update: Ultimate Multisite v2.17.0

Offen
  • Stimmt etwas nicht?
#188 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
68/100
Issue-Typ
Dokumentation
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
php, wordpress
Bereich
documentation

Rechercherichtung

Read the four listed guides first, preserving their frontmatter and style. Compare each statement with the merged plugin implementation, the referenced PRs, and the final readme.txt 2.17.0 changelog, then run the documentation repository's build and link checks from its package manifest. Done means verified user-facing behavior is accurately documented without speculative claims, credentials, or private paths.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

auto-dispatch documentation needs-update origin:interactive priority:medium status:available tier:standard

Release context

Prepare manual documentation updates for Ultimate Multisite 2.17.0. Publication is authorized but still pending; do not describe the release as published until its GitHub/WordPress.org deployment is verified. The release aggregates already-merged changes since 2.16.1 and the checkout validation fix in Ultimate-Multisite/ultimate-multisite#1898.

Required updates

  • docs/user-guide/host-integrations/gridpane.md: verify and update setup for the current bearer-token API. Reference inc/integrations/providers/gridpane/class-gridpane-integration.php in the plugin repo: WU_GRIDPANE_API_TOKEN (legacy WU_GRIDPANE_API_KEY alias), optional site/server ID discovery during connection testing, legacy app-ID alias, optional DNS integration selection/ID, encrypted token storage and SSL/domain synchronization behavior. Do not request or embed actual credentials.
  • docs/user-guide/configuration/checkout-forms.md: explain that existing WordPress accounts must authenticate before checkout links/logs in as that account; describe the multiple-memberships policy using the actual setting label/default from the plugin. Reference checkout ownership PR #1891 and membership policy PR #1880 in the plugin repo.
  • docs/user-guide/administration/managing-memberships.md: update the relationship between repeat signup and the configured multiple-memberships policy. Clarify that restoring no-card trials preserves trial timing and applicable setup fees rather than immediately replacing the existing subscription.
  • docs/user-guide/configuration/site-templates.md: assess whether template preparation/cloning guidance needs changes for plugin-owned initialization, duplicate-table handling and explicit clone failure reporting. Reference merged cloning changes and PR #1888 in the plugin repo. Add guidance only for verified user-facing behavior; do not invent new settings.

Reference pattern and verification

  • These paths were verified in the current docs repository tree. Read each page first and preserve its existing frontmatter/style.
  • Compare each statement with the merged plugin implementation and final readme.txt 2.17.0 changelog. Use the published tag once available, not an unmerged feature branch.
  • Check existing coverage before adding prose; skip a page with a brief explanation if it already accurately documents the behavior.
  • Do not hand-edit generated hook references or addon changelog pages. Pure placeholder-formatting/internal test fixes do not require new manual guides.
  • Run the docs repository's existing build/link checks using the commands declared by its own package manifest. Verify links and avoid retaining local/private paths or credentials.

Acceptance

Relevant guides accurately explain 2.17.0 behavior, with no speculative feature/configuration claims, and applicable docs validation passes. This documentation follow-up does not block shipping the already-tested customer-facing fixes.

aidevops.sh v3.34.13 plugin for OpenCode v1.18.31 with gpt-6.1-sol spent 1d 1h and 3,734,799 tokens on this with the user in an interactive session.

Vorherrschende Sprache
MDX
Sterne
0
Forks
0
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus Ultimate-Multisite/docs

Alle Issues in Ultimate-Multisite/docs

Ähnliche Issues

Weitere Issues zu Documentation

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.