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
Description:
Currently, achieving a full-width layout in Flowershow seems challenging due to hardcoded margin/padding values in the main Layout component. The layout: unstyled option, which worked before in a commit related to responsiveness, is now limited to MdxPage, wrapped by the Layout component.
Proposed Solutions
1. Configuration Option for Full-Width:
We can add a configuration option in Flowershow to enable full-width layouts. This option could override the hardcoded values in the main Layout component, allowing users to have more flexibility in creating custom pages with different layouts.
Example:
// config.mjs
layout: {full_width: true// Sets the Layout component to fill all available width ( full width if there's no Toc or sidebar )}
Refactor LHS Sidebar and RHS ToC for Custom Pages:
If the LHS sidebar and RHS ToC only apply to markdown pages, consider refactoring to move these elements into the MdxPage. This would separate the responsibilities, making it feasible for users to create fully custom pages, similar to the NextJS style.
The text was updated successfully, but these errors were encountered:
Description:
Currently, achieving a full-width layout in Flowershow seems challenging due to hardcoded margin/padding values in the main Layout component. The layout: unstyled option, which worked before in a commit related to responsiveness, is now limited to MdxPage, wrapped by the Layout component.
Proposed Solutions
1. Configuration Option for Full-Width:
We can add a configuration option in Flowershow to enable full-width layouts. This option could override the hardcoded values in the main Layout component, allowing users to have more flexibility in creating custom pages with different layouts.
Example:
If the LHS sidebar and RHS ToC only apply to markdown pages, consider refactoring to move these elements into the MdxPage. This would separate the responsibilities, making it feasible for users to create fully custom pages, similar to the NextJS style.
The text was updated successfully, but these errors were encountered: