decidim-toggle 0.1.3

data/website/docs/developer/_category_.json

@@ -0,0 +1,8 @@
+{
+  "label": "Contribute",
+  "position": 3,
+  "link": {
+    "type": "generated-index",
+    "description": "Code of conduct, contribution guide, and gem internals."
+  }
+}

data/website/docs/developer/code-of-conduct.md

@@ -0,0 +1,99 @@
+---
+sidebar_position: 1
+slug: /code-of-conduct
+title: Code of Conduct
+description: Rules for contributing to decidim-toggle
+---
+
+# Contributor Covenant 3.0 Code of Conduct
+
+## Our Pledge
+
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
+
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
+
+1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our community**.
+
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
+
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
+
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
+
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. To report a possible violation, **[NOTE: describe your means of reporting here.]**
+
+Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
+
+
+## Addressing and Repairing Harm
+
+**[NOTE: The remedies and repairs outlined below are suggestions based on best practices in code of conduct enforcement. If your community has its own established enforcement process, be sure to edit this section to describe your own policies.]**
+
+If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
+
+1) Warning
+   1) Event: A violation involving a single incident or series of incidents.
+   2) Consequence: A private, written warning from the Community Moderators.
+   3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
+2) Temporarily Limited Activities
+   1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
+   2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
+   3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
+3) Temporary Suspension
+   1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
+   2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
+   3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
+4) Permanent Ban
+   1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
+   2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
+   3) Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
+
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
+
+Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
+
+For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).
+

data/website/docs/developer/contribute.md

@@ -0,0 +1,50 @@
+---
+sidebar_position: 2
+slug: /contributing
+title: Contribute
+description: Who maintains decidim-toggle and where to send issues and merge requests
+---
+
+# Contribute
+
+**decidim-toggle** is maintained by [Voca](https://voca.city), a project from [Octree](https://octree.ch).
+
+Issues and merge requests are welcome on GitLab:
+
+- [Repository](https://git.octree.ch/decidim/vocacity/decidim-modules/decidim-toggle)
+- [Issues](https://git.octree.ch/decidim/vocacity/decidim-modules/decidim-toggle/-/issues)
+- [Merge requests](https://git.octree.ch/decidim/vocacity/decidim-modules/decidim-toggle/-/merge_requests)
+
+Read the [Code of conduct](/code-of-conduct) before participating.
+
+Module developers adding a tab to their own gem: [Integrate](../integrate/index.md).
+
+## Before you push
+
+```bash
+docker compose up -d
+docker compose exec toggle bash -lc 'cd /home/module && bundle install -j$(nproc) && ./bin/check'
+cd website && yarn build
+```
+
+| Check | Command |
+|-------|---------|
+| All | `./bin/check` (RuboCop, erblint, RSpec) |
+| RSpec | `unset DATABASE_URL && RAILS_ENV=test bundle exec rspec` |
+| Docs | `cd website && yarn build` |
+
+## Deep dives
+
+| Topic | Page |
+|-------|------|
+| Registry and `add_tab` internals | [Tab registry](./tab-registry.md) |
+| Gem-owned views and layouts | [View customization](./view-customization.md) |
+| Invalid form replay and redirects | [Error handling](./error-handling.md) |
+| Deface overrides (`window.DecidimToggle`) | [Deface usage](./deface-usage.md) |
+| Editing this documentation site | [Documentation website](./documentation.md) |
+
+## See also
+
+- [Code of conduct](/code-of-conduct)
+- [Integrate](../integrate/index.md)
+- [Overview](../index.md)

data/website/docs/developer/deface-usage.md

@@ -0,0 +1,37 @@
+---
+sidebar_position: 6
+title: Deface usage
+description: JavaScript config injection overrides
+---
+
+# Deface usage
+
+Deface injects `window.DecidimToggle` into participant and admin layouts without forking decidim-core. Overrides live in `app/overrides/` and are **ignored by Zeitwerk** — Deface loads them at boot.
+
+## Public site
+
+| File | Virtual path | Inserts |
+|------|--------------|---------|
+| `add_toggle_javascript_public.rb` | `layouts/decidim/_decidim_javascript` | `layouts/decidim/toggle/javascript_config` after `js_configuration` |
+
+## Admin
+
+| File | Virtual path | Inserts |
+|------|--------------|---------|
+| `add_toggle_javascript_admin.rb` | `layouts/decidim/admin/_header` | same partial after admin stylesheet pack tag |
+
+## Partial
+
+`app/views/layouts/decidim/toggle/_javascript_config.html.erb` — sets `window.DecidimToggle` from `Decidim::Toggle.javascript_config_for(current_organization)`.
+
+Forms opt in with `Decidim::Toggle::ExposeAttributesToJs` and `expose_to_javascript` — see [JavaScript](../integrate/javascript.md).
+
+## Drift check
+
+When upgrading decidim-core, diff upstream layout templates against the `original:` strings in override files. System specs in `spec/system/decidim_toggle/javascript_config_spec.rb` assert injection end-to-end.
+
+## See also
+
+- [JavaScript](../integrate/javascript.md)
+- [Contribute](./contribute.md)
+- [Documentation website](./documentation.md)

data/website/docs/developer/documentation.md

@@ -0,0 +1,58 @@
+---
+sidebar_position: 7
+title: Documentation website
+description: Edit and build the Docusaurus site
+---
+
+# Documentation website
+
+[Docusaurus 3](https://docusaurus.io/) site with docs at the site root (`routeBasePath: /`). Published at [octree-gva.github.io/decidim-toggle](https://octree-gva.github.io/decidim-toggle/).
+
+## Site layout
+
+```text
+website/docs/
+  index.md              # Homepage
+  integrate/            # Module developers
+  developer/            # Gem contributors
+```
+
+Sidebar is autogenerated from the folder tree (`sidebars.ts`).
+
+## Page structure
+
+Every content page follows the same shape:
+
+1. **Front matter** — `title`, `description`, `sidebar_position`
+2. **H1** — matches the page title
+3. **Metadata** — `Who reads this`, `Prerequisite` (when applicable), `Next` (reading-order hint)
+4. **Intro** — one short paragraph
+5. **Body** — `##` sections with steps, tables, or code
+6. **See also** — links back to the section index, siblings, and cross-section pages
+
+Homepage (`index.md`) uses the same metadata block; **See also** is a table of entry points.
+
+## Edit locally
+
+```bash
+cd website
+yarn
+yarn start
+```
+
+## Build before merge
+
+```bash
+cd website && yarn build
+```
+
+`onBrokenLinks: 'throw'` — fix broken links before merging. GitLab job `node::docs` runs the same build on MRs and `main`.
+
+## Images
+
+Static assets: `website/static/img/`. Reference from markdown as `/img/filename.png`.
+
+## See also
+
+- [Contribute](./contribute.md)
+- [Overview](../index.md)

data/website/docs/developer/error-handling.md

@@ -0,0 +1,51 @@
+---
+sidebar_position: 5
+title: Error handling
+description: Invalid tab saves, flash replay, and redirect anchors
+---
+
+# Error handling
+
+Each tab PATCH is independent. Validation failures must re-open the same tab with errors — without a full page POST/redirect cycle per field.
+
+## Happy path
+
+`SettingsTabController#update` runs the tab command. On `:ok`:
+
+- `flash[:notice]` — success copy
+- Redirect to `decidim_system.edit_organization_path(organization)` with optional `anchor: "panel-toggle-<tab_id>"` when `decidim_toggle_active_tab` matches a registered tab
+
+## Invalid form
+
+On `:invalid`, the controller stores a payload in `flash[:decidim_toggle_invalid_settings_tab]`:
+
+```ruby
+{
+  organization_id:,
+  tab_id:,
+  params: { ... submitted organization params ... },
+  errors: { "attribute" => ["message", ...] }
+}
+```
+
+Redirect to the organization edit page (same anchor rules).
+
+## Replay on re-render
+
+`decidim_toggle_settings_tab_form` checks that flash key. When `organization_id` and `tab_id` match the current tab:
+
+1. Rebuilds the form from stored params (not the DB model)
+2. Re-applies error messages on the form object
+3. Renders the tab with `form-error` markup
+
+Custom `form_layout_partial:` tabs must use `tf.object` (or fields through `tf`) inside `decidim_toggle_settings_tab_form` so replayed errors bind to inputs — see `tabs/_language_tab.html.erb`.
+
+## Unknown tab
+
+`PATCH …/settings_tab/<unknown>` → `404`.
+
+## See also
+
+- [Tab registry](./tab-registry.md)
+- [View customization](./view-customization.md)
+- [Contribute](./contribute.md)

data/website/docs/developer/tab-registry.md

@@ -0,0 +1,51 @@
+---
+sidebar_position: 3
+title: Tab registry
+description: SettingsTabRegistry, add_tab, and boot-time registration
+---
+
+# Tab registry
+
+Extensions register tabs at boot; the System UI reads the registry to render panels and route PATCH requests.
+
+## Boot flow
+
+```text
+Engine initializer decidim_toggle.organization_settings_tabs
+  └── OrganizationSettingsTabs.register!
+Your engine initializer
+  └── Decidim::Toggle.settings_tabs(:organization_settings) { |tabs| tabs.add_tab ... }
+        └── SettingsTabRegistry.register_form_tab(identifier, form, command, module_name:)
+```
+
+## Key files
+
+```text
+lib/decidim/toggle/settings_tabs.rb           # add_tab / remove_tab DSL
+lib/decidim/toggle/settings_tab_registry.rb   # form + command map per tab id
+lib/decidim/toggle/settings_tab_item.rb       # tab metadata (position, partials, if:)
+lib/decidim/toggle/organization_settings_tabs.rb
+app/controllers/decidim_toggle/system/settings_tab_controller.rb
+```
+
+## `add_tab` contract
+
+One tab = one `Decidim::Form` subclass + one `Decidim::Command`.
+
+- `identifier` — URL segment and DOM id (`panel-toggle-<identifier>`)
+- `module_name:` — optional; links tab to JSON config row (`ModuleConfigForm` path)
+- `remove_tab(id)` — drop a built-in tab before registering a replacement
+
+Duplicate registration: last `add_tab` wins. In development/test, same id with a **different** form/command raises `DuplicateTabRegistrationError`.
+
+## Save endpoint
+
+`PATCH /decidim_toggle/system/organizations/:organization_id/settings_tab/:tab_id`
+
+Controller resolves `registry.form_tab(tab_id)`, builds the form from params, runs the command.
+
+## See also
+
+- [Contribute](./contribute.md)
+- [Error handling](./error-handling.md)
+- [Add a settings tab](../integrate/quickstart.md) — integrator walkthrough

data/website/docs/developer/view-customization.md

@@ -0,0 +1,49 @@
+---
+sidebar_position: 4
+title: View customization
+description: Internal views that render the tabbed organization settings UI
+---
+
+# View customization
+
+Internal templates for decidim-toggle. Integrators customize **their** tab via `form_layout_partial:` — see [Customize views](../integrate/customize-views.md).
+
+## Override entry point
+
+`app/views/decidim/system/organizations/edit.html.erb` — replaces the flat org edit form with `settings_tabs` partial.
+
+## Tab shell
+
+| Partial | Role |
+|---------|------|
+| `_settings_tabs.html.erb` | Tab nav + panels; encryption gate |
+| `_default_form_tab.html.erb` | Default wrapper: `decidim_toggle_settings_tab_form` + `all_fields` |
+| `tabs/_omniauth_tab.html.erb` | Built-in OmniAuth layout |
+| `tabs/_emails_tab.html.erb` | Built-in SMTP layout |
+| `_settings_tab_submit.html.erb` | Cancel / save |
+| `_settings_tab_active_tab_field.html.erb` | Hidden `decidim_toggle_active_tab` |
+| `_encryption_not_configured_callout.html.erb` | Shown when `encryption_configured?` is false |
+| `tabs/_language_tab.html.erb` | Built-in locale table layout |
+| `tabs/_security_tab.html.erb` | Built-in security layout |
+| `tabs/_authorizations_tab.html.erb` | Built-in authorizations layout |
+| `tabs/_file_upload_tab.html.erb` | Built-in file upload layout |
+
+## Helpers
+
+`Decidim::Toggle::SystemSettingsTabHelper`:
+
+- `decidim_toggle_settings_tab_form(organization, tab)` — form shell, flash error replay, callouts
+- `decidim_toggle_update_settings_tab_organization_path(organization, tab_id:)`
+- `encryption_configured?`
+
+`Decidim::Toggle::SettingsFormBuilder` — `all_fields`, `fields_for_names`, `informative_callouts`.
+
+## Styles
+
+`app/packs/stylesheets/decidim/toggle/organization_settings.scss` — tab accordion layout.
+
+## See also
+
+- [Customize views](../integrate/customize-views.md) — integrator partials
+- [Tab registry](./tab-registry.md)
+- [Error handling](./error-handling.md)

data/website/docs/index.md

@@ -0,0 +1,80 @@
+---
+sidebar_position: 1
+slug: /
+title: Overview
+description: Tabbed System administration for Decidim — register org settings from your module
+---
+
+# Decidim Toggle
+
+decidim-toggle rewrites **System → Organizations** in the Decidim admin. Instead of one long form, settings are grouped in tabs. The gem ships built-in tabs (name, OmniAuth, SMTP, language, authorizations, security, file upload) and exposes a small API so your `decidim-*` module can add its own tab.
+
+With this gem you **add a tab**, **plug in your form and command**, and **read or write configuration** per organization through `Decidim::Toggle.config_for` — no extra tables .
+
+
+<div class="full">
+
+![Decidim Toggle /system menu for security](/img/screenshots_security_tab.png)
+
+</div>
+
+
+## Compare
+
+
+|  | Decidim | Decidim Toggle |
+| -- | ------| --------------- |
+| Update tenant name, host | ✅ | ✅ |
+| Advanced configuration | ✅ | ✅ |
+| Update SMTP credentials | ✅ | ✅ |
+| Configure machine translation | ❌ | ✅ |
+| Change locales | ❌ | ✅ |
+| Can extend the /system | ❌ | ✅ |
+
+
+
+## Get started
+
+<div class="full">
+
+![How it works](/img/schema_overview.png)
+
+</div>
+
+
+### Use in your `decidim-*` gem
+
+Add the dependency in your gemspec:
+
+```ruby
+# decidim-my_module.gemspec
+s.add_dependency "decidim-toggle"
+```
+
+Then register a tab in your engine — full steps in [Add a settings tab](./integrate/quickstart.md).
+
+### Install in a Decidim app (optional)
+
+Add to the Gemfile:
+
+```ruby
+gem "decidim-toggle"
+```
+
+```bash
+bundle install
+rails decidim_toggle:install:migrations
+rails db:migrate
+```
+
+## Compatibility
+
+Tested on Decidim **0.29**. Works on **0.31** as well (same System organization surface and Form/Command contract).
+
+## See also
+
+| You are… | Read |
+|----------|------|
+| Building a module tab | [Integrate](./integrate/index.md) → [Add a settings tab](./integrate/quickstart.md) |
+| Hacking decidim-toggle | [Contribute](/contributing) |
+| Something wrong | [GitLab issues](https://git.octree.ch/decidim/vocacity/decidim-modules/decidim-toggle/-/issues) |

data/website/docs/integrate/_category_.json

@@ -0,0 +1,8 @@
+{
+  "label": "Integrate",
+  "position": 2,
+  "link": {
+    "type": "generated-index",
+    "description": "Add a tab → define attributes → customize views."
+  }
+}

data/website/docs/integrate/attributes.md

@@ -0,0 +1,121 @@
+---
+sidebar_position: 3
+title: Attributes
+description: Form attributes supported by SettingsFormBuilder
+---
+
+# Attributes
+
+**Who reads this:** module developers defining tab form fields.  
+**Prerequisite:** [Add a settings tab](./quickstart.md) — form class from step 1.  
+**Next:** [Informative callouts](./informative_callout.md) or [Customize views](./customize-views.md).
+
+Declare attributes on your `Decidim::Form`. `Decidim::Toggle::SettingsFormBuilder` renders them via `all_fields` (default tab) or `fields_for_names` (inside a `form_layout_partial:`).
+
+```ruby
+module MyModule
+  class AdminConfigForm < Decidim::Form
+    include Decidim::Toggle::ModuleConfigForm
+
+    self.module_config_name = "my_module"
+    mimic :organization
+
+    attribute :enabled, :boolean
+    attribute :api_key, :string
+    attribute :max_items, :integer
+    attribute :mode, :string
+    attribute :tags, [String]
+
+    def self.collection_for_mode
+      [%w[live Live], %w[draft Draft]]
+    end
+  end
+end
+```
+
+## Supported attribute types
+
+| Declaration | Widget | Notes |
+|-------------|--------|-------|
+| `attribute :x, :boolean` | Checkbox | |
+| `attribute :x, :string` | Text field | `secondary_hosts` renders as textarea |
+| `attribute :x, :integer` | Number field | |
+| Other scalar types | Text field | Fallback when no collection |
+| `attribute :x, [String]` + `collection_for_x` | Check boxes | Multi-select |
+| Scalar + `collection_for_x` | Radio buttons | Single choice |
+| `translatable_attribute :x, String` | Translated field | Requires `Decidim::TranslatableAttributes`; locale keys hidden from `all_fields` |
+| `translatable_attribute :x, Decidim::Attributes::RichText` | Translated editor | Rich text per locale |
+
+`id` and per-locale keys (e.g. `name_en`) are excluded from `all_fields` when they belong to a translatable hash.
+
+## Collections
+
+Add `collection_for_<attribute_name>` returning `[[value, label], ...]`:
+
+```ruby
+attribute :users_registration_mode, :string
+
+def self.collection_for_users_registration_mode
+  Decidim::Organization.users_registration_modes.map do |mode|
+    [mode.first, I18n.t("decidim.system.organizations.users_registration_mode.#{mode.first}")]
+  end
+end
+```
+
+- **Scalar attribute** → radio buttons  
+- **Array attribute** (`[String]`, etc.) → check boxes  
+
+## Field helptext
+
+Optional copy under a field — see [Labels](./labels.md).
+
+```yaml
+# config/locales/my_module_en.yml
+en:
+  decidim_toggle:
+    system:
+      my_module:
+        helptext:
+          api_key: "Shown to server-side jobs only."
+```
+
+## Disabled fields
+
+Disable a field in the default builder by implementing either:
+
+- `#attribute_disabled?(attribute)` on the form instance, or
+- `#disabled_for_<attribute>?` per attribute
+
+```ruby
+def attribute_disabled?(attribute)
+  attribute == :beta_enabled && !Decidim::Toggle.gem_present?("decidim-beta")
+end
+```
+
+Disabled inputs are not submitted; keep your command aligned (ignore or reject unknown params).
+
+The field wrapper gets `class="field is-disabled"` (Decidim convention) so you can style muted labels/inputs in CSS.
+
+## Builder methods
+
+| Method | Use |
+|--------|-----|
+| `f.all_fields` | Every form attribute (default tab body) |
+| `f.fields_for_names(:enabled, :mode)` | Named subset inside a partial or layout |
+
+Used in views as `f` / `tf` (`Decidim::Toggle::SettingsFormBuilder`).
+
+## Nested or custom widgets
+
+Nested forms (e.g. `Decidim::System::FileUploadSettingsForm`) or non-standard markup are **not** auto-rendered. Use `form_layout_partial:` — [Customize views](./customize-views.md).
+
+For info, warning, and danger banners above the fields, see [Informative callouts](./informative_callout.md).
+
+## See also
+
+- [Add a settings tab](./quickstart.md)
+- [Labels](./labels.md)
+- [Informative callouts](./informative_callout.md)
+- [Customize views](./customize-views.md)
+- [JavaScript](./javascript.md)
+- [Integrate](./index.md)