Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Docs update: Ultimate Multisite v2.17.0

Ouverte
#188 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
68/100
Type d'issue
Documentation
Clarté
Clairement spécifiée
Activité
Active
Stack technique
php, wordpress
Domaine
documentation

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
MDX
Étoiles
0
Forks
0
Métriques de merge des PR
Aucune PR mergée en 30 j

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de Ultimate-Multisite/docs

Toutes les issues de Ultimate-Multisite/docs

Issues similaires

Plus d'issues Documentation

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.