Skip to content

Commit f291d4d

Browse files
Merge branch 'main' into preload-entries
2 parents 7eec91d + 3446c55 commit f291d4d

File tree

211 files changed

+1806
-1108
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

211 files changed

+1806
-1108
lines changed

src/routes/advanced-concepts/fine-grained-reactivity.mdx

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,19 @@
11
---
22
title: Fine-grained reactivity
33
use_cases: >-
4-
understanding core reactivity, performance optimization, building reactive
5-
systems from scratch, learning framework internals
4+
optimizing performance, reducing re-renders, understanding solid fundamentals,
5+
building efficient apps, custom reactive systems
66
tags:
77
- reactivity
8+
- performance
89
- signals
910
- effects
10-
- performance
11+
- optimization
1112
- fundamentals
12-
- reactive-primitives
1313
version: '1.0'
14+
description: >-
15+
Master Solid's fine-grained reactivity system for targeted UI updates, optimal
16+
performance, and efficient state management patterns.
1417
---
1518

1619
Reactivity ensures automatic responses to data changes, eliminating the need for manual updates to the user interface (UI).

src/routes/concepts/components/basics.mdx

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,19 @@
22
title: Basics
33
order: 4
44
use_cases: >-
5-
always, first component creation, learning component structure, understanding
6-
lifecycle, component organization
5+
starting new projects, creating components, understanding component structure,
6+
building ui blocks, component organization
77
tags:
88
- components
9+
- basics
910
- jsx
1011
- lifecycle
11-
- fundamentals
12-
- always
13-
- component-tree
12+
- imports
13+
- structure
1414
version: '1.0'
15+
description: >-
16+
Learn Solid component fundamentals: creating reusable UI blocks, component
17+
trees, lifecycles, and proper import/export patterns.
1518
---
1619

1720
Components are the building blocks of Solid applications.

src/routes/concepts/components/class-style.mdx

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,19 @@
22
title: Class and style
33
order: 2
44
use_cases: >-
5-
styling components, dynamic styling, theming, conditional css classes, inline
6-
styles
5+
styling components, dynamic theming, conditional styling, css integration,
6+
responsive design, ui customization
77
tags:
88
- styling
99
- css
1010
- classes
11-
- dynamic-styling
12-
- theming
13-
- conditional-rendering
11+
- themes
12+
- dynamic
13+
- ui
1414
version: '1.0'
15+
description: >-
16+
Style Solid components with CSS classes and inline styles. Learn dynamic
17+
styling, classList usage, and theme implementation.
1518
---
1619

1720
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).

src/routes/concepts/components/event-handlers.mdx

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,19 @@
22
title: Event handlers
33
order: 3
44
use_cases: >-
5-
user interactions, click handlers, form events, custom events, event
6-
delegation optimization
5+
user interactions, click handling, form inputs, keyboard events, custom
6+
events, touch gestures, event optimization
77
tags:
88
- events
9-
- user-interaction
10-
- forms
11-
- event-delegation
12-
- performance
9+
- interactions
1310
- handlers
11+
- delegation
12+
- performance
13+
- dom
1414
version: '1.0'
15+
description: >-
16+
Handle user interactions in Solid with event delegation and native events for
17+
optimal performance and resource management.
1518
---
1619

1720
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.

src/routes/concepts/components/props.mdx

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,19 @@
11
---
22
title: Props
33
use_cases: >-
4-
passing data between components, component communication, reusable components,
5-
parent-child data flow
4+
passing data between components, parent-child communication, component
5+
configuration, default values, prop management
66
tags:
77
- props
8-
- component-communication
9-
- data-flow
10-
- reusability
11-
- merge-props
12-
- split-props
8+
- components
9+
- data
10+
- communication
11+
- mergeprops
12+
- splitprops
1313
version: '1.0'
14+
description: >-
15+
Pass and manage component props in Solid while maintaining reactivity. Learn
16+
mergeProps, splitProps, and best practices.
1417
---
1518

1619
Props are a way to pass state from a parent component to a child component.

src/routes/concepts/context.mdx

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,19 @@
22
title: Context
33
order: 5
44
use_cases: >-
5-
avoiding prop drilling, global state, theme management, authentication state,
6-
deeply nested components
5+
global state management, avoiding prop drilling, theme providers,
6+
authentication state, shared data across components
77
tags:
88
- context
9-
- global-state
10-
- prop-drilling
11-
- state-management
12-
- provider-pattern
13-
- theming
9+
- state
10+
- global
11+
- providers
12+
- sharing
13+
- management
1414
version: '1.0'
15+
description: >-
16+
Share data across component trees with Solid's Context API. Avoid prop
17+
drilling and manage global application state effectively.
1518
---
1619

1720
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

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,19 @@
22
title: Conditional rendering
33
order: 1
44
use_cases: >-
5-
showing hiding content, loading states, error states, user permissions,
6-
dynamic ui
5+
showing/hiding content, loading states, error displays, user permissions,
6+
dynamic ui, feature toggles
77
tags:
8-
- conditional-rendering
9-
- loading-states
10-
- error-handling
11-
- dynamic-ui
8+
- conditional
9+
- rendering
1210
- show
13-
- switch-match
11+
- switch
12+
- match
13+
- ui
1414
version: '1.0'
15+
description: >-
16+
Conditionally render UI elements in Solid using Show, Switch, and Match
17+
components for clean, readable conditional logic.
1518
---
1619

1720
Conditional rendering is the process of displaying different UI elements based on certain conditions.

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

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,19 @@
22
title: Dynamic
33
order: 2
44
use_cases: >-
5-
dynamic component rendering, component switching, plugin systems, cms content,
6-
configurable ui
5+
dynamic component selection, polymorphic components, runtime component
6+
switching, flexible ui rendering, component factories
77
tags:
8-
- dynamic-components
9-
- component-switching
10-
- configurable-ui
11-
- cms
12-
- plugin-systems
8+
- dynamic
9+
- components
10+
- rendering
11+
- polymorphic
12+
- runtime
13+
- flexible
1314
version: '1.0'
15+
description: >-
16+
Render components dynamically at runtime with Solid's Dynamic component. Build
17+
flexible UIs with runtime component selection.
1418
---
1519

1620
`<Dynamic>` is a Solid component that allows you to render components dynamically based on data.

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

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,19 @@
22
title: Error boundary
33
order: 5
44
use_cases: >-
5-
error handling, preventing app crashes, user experience, graceful degradation,
6-
error recovery
5+
error handling, crash prevention, user-friendly errors, app stability, error
6+
recovery, debugging production issues
77
tags:
8-
- error-handling
9-
- error-boundary
10-
- crash-prevention
11-
- user-experience
12-
- error-recovery
8+
- errors
9+
- boundary
10+
- handling
11+
- recovery
12+
- stability
13+
- debugging
1314
version: '1.0'
15+
description: >-
16+
Catch and handle rendering errors gracefully with ErrorBoundary. Prevent app
17+
crashes and provide user-friendly error recovery.
1418
---
1519

1620
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

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,17 +2,20 @@
22
title: List rendering
33
order: 3
44
use_cases: >-
5-
displaying arrays, dynamic lists, table data, todo lists, data visualization,
6-
performance optimization
5+
rendering arrays, dynamic lists, data iteration, tables, repeating elements,
6+
collection display, performance optimization
77
tags:
88
- lists
99
- arrays
10+
- for
11+
- index
1012
- iteration
13+
- rendering
1114
- performance
12-
- for-component
13-
- index-component
14-
- dynamic-data
1515
version: '1.0'
16+
description: >-
17+
Efficiently render dynamic lists in Solid using For and Index components.
18+
Optimize performance for different data scenarios.
1619
---
1720

1821
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.

0 commit comments

Comments
 (0)