What is the best way to do the full width background fix height only on index page? What should I use? Layout builder in template options and new section with new template position? With custom css (I wanted to do it through custom.scss and bootstrap breakpoints for responsive)
There are couple of ways you can do the background thing.
1. You can do a page class suffix for homepage (on menu class) and write custom CSS.
2. You can copy a existing Astroid style and assign it to homepage only and customize it to fit your needs.
If you like our support and products, tweet us at joomdev and let the world know about it.
The administrator has disabled public write access.
How to use bootstrap breakpoints in custom scss?
1 year 6 months ago #13868
But I am not familiar with astroid framework scss rules. There are astoid, zero and bootstrap folders in scss folder and there are so many rules. And I thought that all bootstrap functions already included.
I have feeling that there are some developer rules, preset of styles in scss to not to do double rules of white text colour etc.
You can do a page class suffix for homepage (on menu class) and write custom CSS.
Thanks bro. I understood that there is no need to change layout. Suffix is the best way.
You can copy a existing Astroid style and assign it to homepage only and customize it to fit your needs.
Please. can you give more detailed. Where I should fine the existing Astroid styles and read about it?
⚠️ Heads up!
The Sass team discourages the continued use of the @import rule. Sass will gradually phase it out over the next few years, and eventually remove it from the language entirely. Prefer the @use rule instead.
What’s Wrong With @import?
The @import rule has a number of serious issues:
• @import makes all variables, mixins, and functions globally accessible. This makes it very difficult for people (or tools) to tell where anything is defined.
• Because everything’s global, libraries must prefix to all their members to avoid naming collisions.
• @extend rules are also global, which makes it difficult to predict which style rules will be extended.
• Each stylesheet is executed and its CSS emitted every time it’s @imported, which increases compilation time and produces bloated output.
• There was no way to define private members or placeholder selectors that were inaccessible to downstream stylesheets.
The new module system and the @use rule address all these problems.
How Do I Migrate?
We’ve written a migration tool that automatically converts most @import-based code to @use-based code in a flash. Just point it at your entrypoints and let it run!
================================== @use sass-lang.com/documentation/at-rules/use
The simplest @use rule is written @use "<url>", which loads the module at the given URL. Any styles loaded this way will be included exactly once in the compiled CSS output, no matter how many times those styles are loaded.
A stylesheet’s @use rules must come before any rules other than @forward, including style rules. However, you can declare variables before @use rules to use when configuring modules.
JoomDev is not affiliated with or endorsed by Open Source Matters or the Joomla! Project. The Joomla! logo is used under a limited license granted by Open Source Matters the trademark holder in the United States and other countries.