We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In Outline's Admin UI, is it possible to show Styles Options for just the Sections that actually exist on that Outline?
Something like declaring in the layout.yaml or index.yaml file which styles should appear like:
styles: core: base: Base accent: Accent font: Font link: Link section: above: Above below: Below footer: Footer bottom: Bottom configuration: breakpoints: Breakpoints menu: Menu
By default, it seems that All Styles options appear there, disregarding what sections an outline supports and this can be confusing for the user.
The text was updated successfully, but these errors were encountered:
Was just to about to ask same thing. Drove me mad last night trying to find was to remove default section styles for Helium.
Sorry, something went wrong.
No, it's not possible right now as there's no way to know which CSS rules are used by the layout.
Hi there - see this was added to the 5.4.24 milestone. Is there any update on this?
It was closed during the 5.4.24 milestone, not added or modified in any way, so @mahagr reply is final.
No branches or pull requests
In Outline's Admin UI, is it possible to show Styles Options for just the Sections that actually exist on that Outline?
Something like declaring in the layout.yaml or index.yaml file which styles should appear like:
styles:
core:
base: Base
accent: Accent
font: Font
link: Link
section:
above: Above
below: Below
footer: Footer
bottom: Bottom
configuration:
breakpoints: Breakpoints
menu: Menu
By default, it seems that All Styles options appear there, disregarding what sections an outline supports and this can be confusing for the user.
The text was updated successfully, but these errors were encountered: