Documentation metadata via Frontmatter (#1321)

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>

Author: 2 people

src/routes/concepts/components/props.mdx

@@ -1,19 +1,16 @@
 ---
 title: Props
 use_cases: >-
-  passing data between components, parent-child communication, component
-  configuration, default values, prop management
+  passing data between components, component communication, reusable components,
+  parent-child data flow
 tags:
   - props
-  - components
-  - data
-  - communication
-  - mergeprops
-  - splitprops
+  - component-communication
+  - data-flow
+  - reusability
+  - merge-props
+  - split-props
 version: '1.0'
-description: >-
-  Pass and manage component props in Solid while maintaining reactivity. Learn
-  mergeProps, splitProps, and best practices.
 ---
 
 Props are a way to pass state from a parent component to a child component.

src/routes/concepts/context.mdx

@@ -2,19 +2,16 @@
 title: Context
 order: 5
 use_cases: >-
-  global state management, avoiding prop drilling, theme providers,
-  authentication state, shared data across components
+  avoiding prop drilling, global state, theme management, authentication state,
+  deeply nested components
 tags:
   - context
-  - state
-  - global
-  - providers
-  - sharing
-  - management
+  - global-state
+  - prop-drilling
+  - state-management
+  - provider-pattern
+  - theming
 version: '1.0'
-description: >-
-  Share data across component trees with Solid's Context API. Avoid prop
-  drilling and manage global application state effectively.
 ---
 
 Context provides a way to pass data through the component tree without having to pass props down manually at every level.

src/routes/concepts/control-flow/conditional-rendering.mdx

@@ -2,19 +2,16 @@
 title: Conditional rendering
 order: 1
 use_cases: >-
-  showing/hiding content, loading states, error displays, user permissions,
-  dynamic ui, feature toggles
+  showing hiding content, loading states, error states, user permissions,
+  dynamic ui
 tags:
-  - conditional
-  - rendering
+  - conditional-rendering
+  - loading-states
+  - error-handling
+  - dynamic-ui
   - show
-  - switch
-  - match
-  - ui
+  - switch-match
 version: '1.0'
-description: >-
-  Conditionally render UI elements in Solid using Show, Switch, and Match
-  components for clean, readable conditional logic.
 ---
 
 Conditional rendering is the process of displaying different UI elements based on certain conditions.

src/routes/concepts/control-flow/dynamic.mdx

@@ -2,19 +2,15 @@
 title: Dynamic
 order: 2
 use_cases: >-
-  dynamic component selection, polymorphic components, runtime component
-  switching, flexible ui rendering, component factories
+  dynamic component rendering, component switching, plugin systems, cms content,
+  configurable ui
 tags:
-  - dynamic
-  - components
-  - rendering
-  - polymorphic
-  - runtime
-  - flexible
+  - dynamic-components
+  - component-switching
+  - configurable-ui
+  - cms
+  - plugin-systems
 version: '1.0'
-description: >-
-  Render components dynamically at runtime with Solid's Dynamic component. Build
-  flexible UIs with runtime component selection.
 ---
 
 `<Dynamic>` is a Solid component that allows you to render components dynamically based on data.

src/routes/concepts/control-flow/error-boundary.mdx

@@ -2,19 +2,15 @@
 title: Error boundary
 order: 5
 use_cases: >-
-  error handling, crash prevention, user-friendly errors, app stability, error
-  recovery, debugging production issues
+  error handling, preventing app crashes, user experience, graceful degradation,
+  error recovery
 tags:
-  - errors
-  - boundary
-  - handling
-  - recovery
-  - stability
-  - debugging
+  - error-handling
+  - error-boundary
+  - crash-prevention
+  - user-experience
+  - error-recovery
 version: '1.0'
-description: >-
-  Catch and handle rendering errors gracefully with ErrorBoundary. Prevent app
-  crashes and provide user-friendly error recovery.
 ---
 
 By default, if part of an application throws an error during rendering, the entire application can crash, resulting in Solid removing its UI from the screen.

src/routes/concepts/control-flow/list-rendering.mdx

@@ -2,20 +2,17 @@
 title: List rendering
 order: 3
 use_cases: >-
-  rendering arrays, dynamic lists, data iteration, tables, repeating elements,
-  collection display, performance optimization
+  displaying arrays, dynamic lists, table data, todo lists, data visualization,
+  performance optimization
 tags:
   - lists
   - arrays
-  - for
-  - index
   - iteration
-  - rendering
   - performance
+  - for-component
+  - index-component
+  - dynamic-data
 version: '1.0'
-description: >-
-  Efficiently render dynamic lists in Solid using For and Index components.
-  Optimize performance for different data scenarios.
 ---
 
 List rendering allows you to generate multiple elements from a collection of data, such as an array or object, where each element corresponds to an item in the collection.

src/routes/concepts/control-flow/portal.mdx

@@ -2,19 +2,18 @@
 title: Portal
 order: 3
 use_cases: >-
-  modals, popups, tooltips, dropdowns, z-index issues, overflow clipping,
-  rendering outside parent container
+  modals, tooltips, dropdowns, popups, overlays, z-index issues, clipped
+  content, accessibility improvements
 tags:
-  - portal
-  - modal
-  - popup
+  - modals
+  - tooltips
+  - dropdowns
+  - popups
+  - overlays
+  - accessibility
   - dom
-  - z-index
-  - overflow
+  - positioning
 version: '1.0'
-description: >-
-  Learn how Portal renders elements outside the normal DOM flow to solve z-index
-  and overflow issues for modals and popups.
 ---
 
 When an element requires rendering outside of the usual document flow, challenges related to stacking contents and z-index can interfere with the desired intention or look of an application.

src/routes/concepts/derived-values/derived-signals.mdx

@@ -2,18 +2,16 @@
 title: Derived signals
 order: 1
 use_cases: >-
-  computed values, reactive calculations, dependent state, dynamic values from
-  signals
+  computed values, reactive calculations, dependent state, always, any solid
+  project, data transformations
 tags:
-  - signals
   - reactivity
-  - derived
   - computed
-  - state
+  - derived
+  - calculations
+  - dependencies
+  - always
 version: '1.0'
-description: >-
-  Create reactive derived values that automatically update when their
-  dependencies change using Solid's derived signals.
 ---
 
 Derived signals are functions that rely on one or more [signals](/concepts/signals) to produce a value.

src/routes/concepts/derived-values/memos.mdx

@@ -2,19 +2,16 @@
 title: Memos
 order: 2
 use_cases: >-
-  expensive computations, caching results, optimizing performance, derived
-  state, avoiding re-calculations
+  expensive computations, caching, performance optimization, derived state,
+  preventing unnecessary recalculations
 tags:
-  - memo
   - performance
-  - caching
   - optimization
+  - caching
+  - expensive-computations
+  - derived
   - reactivity
-  - computed
 version: '1.0'
-description: >-
-  Optimize expensive computations with memos that cache results and only
-  recalculate when dependencies actually change.
 ---
 
 Memos are a type of reactive value that can be used to memoize derived state or expensive computations.

src/routes/concepts/effects.mdx

@@ -2,18 +2,16 @@
 title: Effects
 order: 4
 use_cases: >-
-  side effects, dom manipulation, api calls, subscriptions, logging, reacting to
-  state changes
+  side effects, dom manipulation, data fetching, subscriptions, cleanup,
+  lifecycle management, logging
 tags:
-  - effects
   - side-effects
-  - reactivity
   - lifecycle
+  - data-fetching
+  - dom-manipulation
+  - cleanup
   - subscriptions
 version: '1.0'
-description: >-
-  Manage side effects like DOM updates, API calls, and subscriptions that
-  respond automatically to reactive state changes.
 ---
 
 Effects are functions that are triggered when the signals they depend on change.
@@ -37,12 +35,6 @@ createEffect(() => {
 In this example, an effect is created that logs the current value of `count` to the console.
 When the value of `count` changes, the effect is triggered, causing it to run again and log the new value of `count`.
 
-:::note
-Effects are primarily intended for handling side effects that do not write to the reactive system.
-It's best to avoid setting signals within effects, as this can lead to additional rendering or even infinite loops if not managed carefully.
-Instead, it is recommended to use [createMemo](/reference/basic-reactivity/create-memo) to compute new values that rely on other reactive values.
-:::
-
 ## Managing dependencies
 
 Effects can be set to observe any number of dependencies.