You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is Named Slots the recommended approach for building a paginated editor?
I'm building a page-based editor where each page has an editable header, body, and footer. The body content automatically flows to the next page when it overflows.
Would modeling each page as:
PageNode
├── header
├── body
└── footer
using Named Slots be the recommended architecture, or is there a better pattern for this use case?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Is Named Slots the recommended approach for building a paginated editor?
I'm building a page-based editor where each page has an editable header, body, and footer. The body content automatically flows to the next page when it overflows.
Would modeling each page as:
PageNode
├── header
├── body
└── footer
using Named Slots be the recommended architecture, or is there a better pattern for this use case?
Beta Was this translation helpful? Give feedback.
All reactions