Skip to content
Open
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Added descriptions and adjusted use cases/tags
  • Loading branch information
davedbase committed Oct 28, 2025
commit 45450a52070a2bf7810252fe4c00bc12d445eb48
11 changes: 7 additions & 4 deletions src/routes/advanced-concepts/fine-grained-reactivity.mdx
Original file line number Diff line number Diff line change
@@ -1,16 +1,19 @@
---
title: Fine-grained reactivity
use_cases: >-
understanding core reactivity, performance optimization, building reactive
systems from scratch, learning framework internals
optimizing performance, reducing re-renders, understanding solid fundamentals,
building efficient apps, custom reactive systems
tags:
- reactivity
- performance
- signals
- effects
- performance
- optimization
- fundamentals
- reactive-primitives
version: '1.0'
description: >-
Master Solid's fine-grained reactivity system for targeted UI updates, optimal
performance, and efficient state management patterns.
---

Reactivity ensures automatic responses to data changes, eliminating the need for manual updates to the user interface (UI).
Expand Down
13 changes: 8 additions & 5 deletions src/routes/concepts/components/basics.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,16 +2,19 @@
title: Basics
order: 4
use_cases: >-
always, first component creation, learning component structure, understanding
lifecycle, component organization
starting new projects, creating components, understanding component structure,
building ui blocks, component organization
tags:
- components
- basics
- jsx
- lifecycle
- fundamentals
- always
- component-tree
- imports
- structure
version: '1.0'
description: >-
Learn Solid component fundamentals: creating reusable UI blocks, component
trees, lifecycles, and proper import/export patterns.
---

Components are the building blocks of Solid applications.
Expand Down
13 changes: 8 additions & 5 deletions src/routes/concepts/components/class-style.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,16 +2,19 @@
title: Class and style
order: 2
use_cases: >-
styling components, dynamic styling, theming, conditional css classes, inline
styles
styling components, dynamic theming, conditional styling, css integration,
responsive design, ui customization
tags:
- styling
- css
- classes
- dynamic-styling
- theming
- conditional-rendering
- themes
- dynamic
- ui
version: '1.0'
description: >-
Style Solid components with CSS classes and inline styles. Learn dynamic
styling, classList usage, and theme implementation.
---

Similar to HTML, Solid uses `class` and `style` attributes to style elements via [CSS (Cascading Style Sheets)](https://developer.mozilla.org/en-US/docs/Glossary/CSS).
Expand Down
15 changes: 9 additions & 6 deletions src/routes/concepts/components/event-handlers.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,16 +2,19 @@
title: Event handlers
order: 3
use_cases: >-
user interactions, click handlers, form events, custom events, event
delegation optimization
user interactions, click handling, form inputs, keyboard events, custom
events, touch gestures, event optimization
tags:
- events
- user-interaction
- forms
- event-delegation
- performance
- interactions
- handlers
- delegation
- performance
- dom
version: '1.0'
description: >-
Handle user interactions in Solid with event delegation and native events for
optimal performance and resource management.
---

Event handlers are functions that are called in response to specific events occurring in the browser, such as when a user clicks or taps on an element.
Expand Down
17 changes: 10 additions & 7 deletions src/routes/concepts/components/props.mdx
Original file line number Diff line number Diff line change
@@ -1,16 +1,19 @@
---
title: Props
use_cases: >-
passing data between components, component communication, reusable components,
parent-child data flow
passing data between components, parent-child communication, component
configuration, default values, prop management
tags:
- props
- component-communication
- data-flow
- reusability
- merge-props
- split-props
- components
- data
- communication
- mergeprops
- splitprops
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.
Expand Down
17 changes: 10 additions & 7 deletions src/routes/concepts/context.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,16 +2,19 @@
title: Context
order: 5
use_cases: >-
avoiding prop drilling, global state, theme management, authentication state,
deeply nested components
global state management, avoiding prop drilling, theme providers,
authentication state, shared data across components
tags:
- context
- global-state
- prop-drilling
- state-management
- provider-pattern
- theming
- state
- global
- providers
- sharing
- management
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.
Expand Down
17 changes: 10 additions & 7 deletions src/routes/concepts/control-flow/conditional-rendering.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,16 +2,19 @@
title: Conditional rendering
order: 1
use_cases: >-
showing hiding content, loading states, error states, user permissions,
dynamic ui
showing/hiding content, loading states, error displays, user permissions,
dynamic ui, feature toggles
tags:
- conditional-rendering
- loading-states
- error-handling
- dynamic-ui
- conditional
- rendering
- show
- switch-match
- switch
- match
- ui
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.
Expand Down
18 changes: 11 additions & 7 deletions src/routes/concepts/control-flow/dynamic.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,15 +2,19 @@
title: Dynamic
order: 2
use_cases: >-
dynamic component rendering, component switching, plugin systems, cms content,
configurable ui
dynamic component selection, polymorphic components, runtime component
switching, flexible ui rendering, component factories
tags:
- dynamic-components
- component-switching
- configurable-ui
- cms
- plugin-systems
- dynamic
- components
- rendering
- polymorphic
- runtime
- flexible
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.
Expand Down
18 changes: 11 additions & 7 deletions src/routes/concepts/control-flow/error-boundary.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,15 +2,19 @@
title: Error boundary
order: 5
use_cases: >-
error handling, preventing app crashes, user experience, graceful degradation,
error recovery
error handling, crash prevention, user-friendly errors, app stability, error
recovery, debugging production issues
tags:
- error-handling
- error-boundary
- crash-prevention
- user-experience
- error-recovery
- errors
- boundary
- handling
- recovery
- stability
- debugging
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.
Expand Down
13 changes: 8 additions & 5 deletions src/routes/concepts/control-flow/list-rendering.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,17 +2,20 @@
title: List rendering
order: 3
use_cases: >-
displaying arrays, dynamic lists, table data, todo lists, data visualization,
performance optimization
rendering arrays, dynamic lists, data iteration, tables, repeating elements,
collection display, 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.
Expand Down
19 changes: 10 additions & 9 deletions src/routes/concepts/control-flow/portal.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,18 +2,19 @@
title: Portal
order: 3
use_cases: >-
modals, tooltips, dropdowns, popups, overlays, z-index issues, clipped
content, accessibility improvements
modals, popups, tooltips, dropdowns, z-index issues, overflow clipping,
rendering outside parent container
tags:
- modals
- tooltips
- dropdowns
- popups
- overlays
- accessibility
- portal
- modal
- popup
- dom
- positioning
- z-index
- overflow
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.
Expand Down
14 changes: 8 additions & 6 deletions src/routes/concepts/derived-values/derived-signals.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,16 +2,18 @@
title: Derived signals
order: 1
use_cases: >-
computed values, reactive calculations, dependent state, always, any solid
project, data transformations
computed values, reactive calculations, dependent state, dynamic values from
signals
tags:
- signals
- reactivity
- computed
- derived
- calculations
- dependencies
- always
- computed
- state
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.
Expand Down
13 changes: 8 additions & 5 deletions src/routes/concepts/derived-values/memos.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,16 +2,19 @@
title: Memos
order: 2
use_cases: >-
expensive computations, caching, performance optimization, derived state,
preventing unnecessary recalculations
expensive computations, caching results, optimizing performance, derived
state, avoiding re-calculations
tags:
- memo
- performance
- optimization
- caching
- expensive-computations
- derived
- optimization
- 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.
Expand Down
12 changes: 7 additions & 5 deletions src/routes/concepts/effects.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,16 +2,18 @@
title: Effects
order: 4
use_cases: >-
side effects, dom manipulation, data fetching, subscriptions, cleanup,
lifecycle management, logging
side effects, dom manipulation, api calls, subscriptions, logging, reacting to
state changes
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.
Expand Down
17 changes: 10 additions & 7 deletions src/routes/concepts/intro-to-reactivity.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,16 +2,19 @@
title: Intro to reactivity
order: 1
use_cases: >-
always, learning solid, understanding reactivity, new developers, core
concepts
learning reactivity, understanding signals, reactive principles, state
management basics, getting started
tags:
- always
- learning
- fundamentals
- reactivity
- beginner
- core-concepts
- signals
- fundamentals
- state
- subscribers
- basics
version: '1.0'
description: >-
Master Solid's reactive system fundamentals: signals, subscribers, and
automatic UI updates for responsive applications.
---

**Note**: While this guide is useful for understanding reactive systems, it does use some Solid-specific terminology.
Expand Down
Loading