makepixelswork / corebootstrap Goto Github PK

• Update to v4.6.0
• Update HTML templates
• Update website docs
• Update README.md

I think I made a mistake here, by importing the whole framework, after I already imported some smaller files.

On the right, is my build file, that compiles the final CSS. On the left is the original bootstrap import. In red the small files I include first, and in yellow the whole framework I include later in my build.

When I check the final CSS, there doesn't seem to be anything wrong with the file. I don't see double references inside the compiled file (as of yet). Maybe my PrePros compiler removes the double entries?

Is this a mistake ...or not?

PS: Don't mind the version numbers. The files are just examples.

Just create compiler and basic html templates that compile according to their version. Then include all those in the framework. Done.

Font Awesome's 5th version (5.x.x) increments too fast. Its minor (5.1 / 5.2 / etc) and patches (5.2.1 / 5.2.2 / etc) are updated within weeks or even days.

During the write-up of this issue, the CoreBootstrap latest Font Awesome version is 5.3.1... whilst Font Awesome itself has gone well into its 5.11.2 version.

I've been thinking to only increment the major and minor releases and link to other version within the readme or additional installation info files.

Or write code that implements this remotely.

Added this as an issue. To be resolved.

According to the v5.3.0 docs ( https://getbootstrap.com/docs/5.3/customize/color/#colors ) there are now secondary and tertiary colors. While CoreBootstrap already used primary and secondary, the tertiary color presets aren't (yet) enabled. To be added.

Add the following code to the base settings in the main sass file.

q {
  &::before {
    margin-left: 2px;
    margin-right: 2px;
  }
  &::after {
    margin-left: 2px;
    margin-right: 2px;
  }
}

Too busy with compiler issues, but you need to remove the double H1 in your own code. Bad practice!

Research most used mixins and add them to my own project.

In LESS it is possible to add variables within variables and inject a variable within the path of a folder structure. I've yet to find a solution for this issue for Sass.

Its not a biggy... users are able to update a few instances of code themselves, but its would be handy of this was possible in Sass. This would improve coding a lot. You only need one place to update your framework versioning, and not -like in Font Awesome's case- five updates lines of code.

Example LESS vs Sass vars

Is this correct? My local file is not updated since November 2023.

Last week, new version has been released. Add it.

• https://github.com/twbs/bootstrap/releases

• https://designshack.net/articles/css/10-less-css-examples-you-should-steal-for-your-projects/