GitHub user aglinxinyuan added a comment to the discussion: Support customizable landing/about pages via block composition
I think what you're describing is a common pattern in CMS (Content Management System) development. When someone deploys a new website, the admin typically starts by selecting a template or theme that matches the intended use case—such as e-commerce, a blog, or a portfolio. That template provides a default site structure, page layouts, color scheme, and placeholder content. >From there, the admin customizes the individual pages and content to fit their >specific needs. I think a similar configuration-first approach could work well for Texera flavors. A flavor could ship with a default landing page configuration (along with its patches, services, and deployment configuration), while still allowing administrators to customize it after deployment. This provides reproducible, version-controlled defaults without sacrificing flexibility. GitHub link: https://github.com/apache/texera/discussions/6726#discussioncomment-17761032 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
