Introducing ReUI:Open-source UI components and apps built with React, Next.js and Tailwind CSS
Browse ReUI

Sass is not including fonts


Hello, I bought this "Keen v3.0.6" theme to add to my project.
The structure is different, so we use the sass directory.
This does not include the path or specifications for loading the icons fonts.
If I use the supplied styles and compare them with the compiled ones they are different by default in the project.

Functional file: plugins/global/plugins.bundle.css
Sass file with the problem: sass/plugins.scss


Text formatting options
Submit
Here's a how to add some HTML formatting to your comment:
  • <pre></pre> for JS codes block
  • <pre lang="html"></pre> for HTML code block
  • <pre lang="scss"></pre> for SCSS code block
  • <pre lang="php"></pre> for PHP code block
  • <code></code> for single line of code
  • <strong></strong> to make things bold
  • <em></em> to emphasize
  • <ul><li></li></ul>  to make list
  • <ol><li></li></ol>  to make ordered list
  • <h3></h3> to make headings
  • <a></a> for links
  • <img> to paste in an image
  • <blockquote></blockquote> to quote somebody
  • happy  :)
  • shocked  :|
  • sad  :(

Replies (7)


It sounds like you're navigating some challenges with integrating the "Keen v3.0.6" theme into your project. Just like using Drone Photography Services to capture the bigger picture from above, you may need to step back and reassess the overall structure to make sure everything aligns perfectly, especially with the icons and compiled styles. A fresh perspective could really help identify any missing links or discrepancies!



It sounds like you're dealing with some challenges integrating the "Keen v3.0.6" theme into your project, especially with the difference in structure and missing specifications for icon fonts. This is a common issue when using themes that have different setups or configurations compared to your existing project. Interestingly, you could think of the process of resolving these inconsistencies, like fixing paths and adjusting styles, as somewhat analogous to serving a section 8 notice in that both require a clear, systematic approach to ensure everything aligns properly. Just as a Section 8 Notice must be delivered correctly to have its intended legal effect, you’ll need to carefully manage these style and file path discrepancies to ensure the theme integrates smoothly into your project and functions as expected.



It sounds like you're facing some challenges with the Sass configuration and font integration in the "Keen v3.0.6" theme. Much like how funding programs help provide the necessary resources for projects to succeed, ensuring your Sass directory is properly configured and the correct paths for font icons are set will help your project run smoothly. Once the setup is right, you'll likely see better alignment between the supplied styles and the compiled ones, just as funding can align with the needs of a project to bring it to completion.



It sounds like you're navigating some tricky setup issues with the Keen theme! Maybe after resolving the icon font paths and SASS compilation, you can take a break by browsing for a lute guitar for sale—balance those tech challenges with some musical inspiration!



It seems like the issue stems from missing paths or mismatched configurations between the supplied styles and your Sass setup. Just like a super glue supplier ensures compatibility and reliability in their products, aligning the paths for icon fonts and ensuring your Sass directory is correctly configured will help achieve the desired results. Double-check the font paths and update your plugins.scss to match the structure.



The Keen v3.0.6 theme most certainly has the essential font files for the icons, but they may not be correctly linked in the given styles bitlife. Look for a "fonts" or "icons" directory in the theme files, then provide the location to these files in your CSS or Sass files.



Hi,

Please note that the KeenIcons source is located in src/plugins/keenicons.

All icon assets are added via gulp and webpack config under tools/gulp.config.js and tools/webpack/plugins/plugins.js, tools/webpack/plugins/plugins.sass.

Then recompile your assets folder with Gulp or Webpack.

Please note that the build tools are required only in the development environment just to compile the assets when the source folder files are modified. In the hosting/server deployment, you will only need the compile assets, no need to install the build tools dependencies there.

Regards.


Text formatting options
Submit
Here's a how to add some HTML formatting to your comment:
  • <pre></pre> for JS codes block
  • <pre lang="html"></pre> for HTML code block
  • <pre lang="scss"></pre> for SCSS code block
  • <pre lang="php"></pre> for PHP code block
  • <code></code> for single line of code
  • <strong></strong> to make things bold
  • <em></em> to emphasize
  • <ul><li></li></ul>  to make list
  • <ol><li></li></ol>  to make ordered list
  • <h3></h3> to make headings
  • <a></a> for links
  • <img> to paste in an image
  • <blockquote></blockquote> to quote somebody
  • happy  :)
  • shocked  :|
  • sad  :(
Text formatting options
Submit
Here's a how to add some HTML formatting to your comment:
  • <pre></pre> for JS codes block
  • <pre lang="html"></pre> for HTML code block
  • <pre lang="scss"></pre> for SCSS code block
  • <pre lang="php"></pre> for PHP code block
  • <code></code> for single line of code
  • <strong></strong> to make things bold
  • <em></em> to emphasize
  • <ul><li></li></ul>  to make list
  • <ol><li></li></ol>  to make ordered list
  • <h3></h3> to make headings
  • <a></a> for links
  • <img> to paste in an image
  • <blockquote></blockquote> to quote somebody
  • happy  :)
  • shocked  :|
  • sad  :(