## Problem/Motivation Webshare's platform list (the `webshare_platforms` database table — the social/share buttons like Facebook, LinkedIn, X) can only be managed by hand through the admin form at `/admin/config/services/webshare/platforms`. A Drupal recipe has no way to add, edit or reorder a platform declaratively: the table isn't a config object, so none of core's existing config actions (`simpleConfigUpdate`, `createIfNotExists`, etc.) can reach it. A site template that needs to add a platform (e.g. a network with no share-intent URL, only a fixed profile link) or reorder the share button list has no way to do it from `recipe.yml`. ## Proposed resolution Add a new `savePlatform` config action plugin, going through a new shared service so it behaves exactly like a site builder using the form, not a separate bypass path: - A new `webshare.platform_manager` service (`Drupal\webshare\PlatformManager`) with `savePlatform(array $values): void` (add or edit; editing only touches the keys given, so reordering one platform only needs `platform_id` + `weight`) and `loadPlatform(string $platformId): ?object`. - A new `#[ConfigAction(id: 'savePlatform')]` plugin (`Drupal\webshare\Plugin\ConfigAction\SavePlatform`) that accepts either one platform-values array or a list of them (needed because a recipe's config actions can only list one `savePlatform` key per config name, so a recipe touching several platforms in one action — e.g. setting a whole Share list's order — passes a list). - The existing admin form (`PlatformForm`) is refactored to call the same `PlatformManager::savePlatform()` instead of its own inline database calls, so the form and the config action share one save path with no logic drift. - Also relaxes the URL template validation (form + service): it previously required the template to contain the `[url]` placeholder, which incorrectly rejected a platform whose share action is a fixed link rather than a per-page share URL (e.g. a network with no share-intent URL, only a profile link). The placeholder substitution is a no-op on a template that doesn't use it, so allowing it is safe. Only the safe-scheme check (https://, http://, mailto:) is still enforced. ## Remaining tasks - [x] File an issue - [x] Addition/Change/Update/Fix — proposed above - [x] Testing to ensure no regression - [ ] Automated unit testing coverage - [ ] Automated functional testing coverage - [ ] UX/UI designer responsibilities - [ ] Readability - [ ] Accessibility - [ ] Performance - [ ] Security - [ ] Developer Documentation - [ ] User Guide Documentation - [x] Reviewed by human - [x] Code review by maintainers - [ ] Full testing and approval - [ ] Credit contributors - [ ] Review with the product owner - [x] Release notes snippet - [x] Release — [webshare 2.0.0-beta2](https://www.drupal.org/project/webshare/releases/2.0.0-beta2) ## API changes - New service: `webshare.platform_manager` (`Drupal\webshare\PlatformManager`). - New config action plugin: `savePlatform` (`Drupal\webshare\Plugin\ConfigAction\SavePlatform`). ## Data model changes None — reuses the existing `webshare_platforms` table through the new service instead of a new schema. ## Release notes snippet Adds a `savePlatform` config action so recipes can add, edit and reorder Webshare platforms declaratively. --- AI-Generated: Yes