• Hi, i have error on…

    Hi, i have error on my console and I have error in my terminal when I run npm run watch
    “WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
    This can impact web performance.
    main.css (284 KiB)

    WARNING in entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
    main (484 KiB)

    WARNING in webpack performance recommendations:
    You can limit the size of your bundles by using import() or require.ensure to lazy load some parts of your application.
    For more info visit https://webpack.js.org/guides/code-splitting/

    How to solve this error

    1. them.es Avatar

      This warning doesn’t produce an error and can be considered a recommendation. If you want to reduce the file size you can try to deactivate unneeded modules in main.scss (https://github.com/them-es/themes-starter-bootstrap/blob/main/assets/main.scss#L78-L112) but if this is not possible you can hide the warning via your webpack config: See https://stackoverflow.com/a/41167614 and https://github.com/webpack/webpack/issues/3486

    Leave a Reply

  • Starter Themes with a new build workflow

    We’ve received feedback from our community that the old build workflow (using Gulp and/or webpack to generate the CSS/JS assets) included several package vulnerabilities that have not been fixed for quite a while and obviously have become unmaintained by the creators.

    One could argue that this should not be problematic, as these dependencies only affect the local development system – and as long as the build process still works, there’s no need to change a running system.
    But using obsolete and unsupported software can be dangerous and can break things “overnight”. Not to mention potential security risks that may arise in the web development stack.

    So it was necessary to find a new simple, modern and future-proof build process for the frontend assets
    Fortunately the research did not take too long. The @wordpress/scripts package from the awesome Gutenberg community already comes with a proven and tested webpack configuration specific to WordPress development, which made it a perfect candidate to try out.

    After some trial-and-error the build process worked pretty well and that’s why all our Starter Themes (Full Site Editing, Bootstrap and Material Design) have been updated to include this “webpack only” workflow from WordPress. From now on Gulp (including its several internal dependencies that are outdated) is not needed anymore.

    Start the development process:
    $ npm run watch
    Build and minify the assets:
    $ npm run build

    👆 Breaking change: The build directories have been moved from /assets/css and /assets/js to /build which aligns with the @wordpress configuration. If you want to include the new workflow in an existing theme, please have a look at the source code in the Github repositories of the Starter Theme and adjust the paths of the JS/CSS assets in functions.php accordingly.


    Leave a Reply

  • WordPress Playground

    Would you like to play around with an instant WordPress installation that runs in your browser?

    Visit https://them.es/playground [🪄 powered by playground.wordpress.net] and give it a try.

    Quickly demonstrate the WordPress dashboard to interested people or temporarily test Themes and Plugins without the need of an entire web server:


    Leave a Reply

  • 20 years WordPress

    Today our favorite CMS celebrates its 20th anniversary 🎉. A special website dedicated to this event has been established by the WordPress team:

    What started as a way to make a better blogging experience has grown into a vibrant open source project that powers an ever-growing percentage of the world’s websites.


    Let’s commemorate some historic milestones, the WordPress project passed within two decades:

    May 2003: WordPress 0.7 – The first release

    January 2004: WordPress 1.0

    May 2004: Support for plugins

    August 2006: The first WordCamp has been organized

    December 2008: Automatic upgrades with a single click

    June 2010: Multisite functionality

    October 2013: Automatic maintenance and security background updates

    December 2015: The WP-API has been integrated

    December 2018: A new block-based Editor

    July 2021: theme.json

    January 2022: Full Site Editing


    Leave a Reply

  • Hi, I’ve installed everything for…

    Hi, I’ve installed everything for the bootstrap theme and trying to follow the instructions here: https://them.es/setup/
    Where it says “import the provided XML”, where is this provided? I can’t find it anywhere.

    1. them.es Avatar

      You’re right. The demo content XML is not shipped with the themes anymore. But you can download the file from the following resource instead: https://codex.wordpress.org/Theme_Unit_Test
      The Setup guide has been updated!

    Leave a Reply

  • Hi,

    When my site is loading, this link https://tl.ytlogs.ru/timesince is running in the background.
    I use this start theme for two my projects, now i have problems.


    Leave a Reply

  • I have been trying to…

    I have been trying to edit the website, from the given questionaire but, i do not have any option to change the contents of the website


    Leave a Reply

  • I get this /#more-57 in…

    I get this /#more-57 in my url from archive page on read-more link. SO how can I get rid of it?

    1. pinky08 Avatar

      He assumes that it is a post id

    2. them.es Avatar

      Not sure if this is the right place for this kind of support question as it’s not possible to replicate the issue without more information. Internal links (i.e. # page jumps) like you describe are not included in any of the Starter Themes we maintain. Probably WP stackexchange would be a better platform to ask for help.

    Leave a Reply

  • Problems styling bootstrap starter theme

    Hello! I’m fairly new to web programming, tough I’ve been developing mobile for a long time already. I was trying to set up a WordPress page using the Bootstrap Starter Theme for WordPress.

    Steps I followed before my problem:
    1. I downloaded from https://them.es/starter-bootstrap/ a theme with my custom settings.
    2. I added the new Theme to my WordPress page, and activated it
    3. I used that same file on my local machine, and installed all the npm dependencies
    4. I run the npm run watch command

    After all these steps, I modify the main.scss file, for example creating a color and updating the colors map according to the documentation.

    //4. Include any default map overrides here
    //Create your own map
    $custom-colors: (

    // Merge the maps
    $theme-colors: map-merge($theme-colors, $custom-colors);

    I let watch to compile all the files correctly, and after that, I copy all the files to the “themes” folder inside my wordpress folders.

    The problem is that if I try to use this new value on a page, for example using bg-testcolor in a nav, the variable won’t get used. If I inspect the code, the values that I see being used are from _root.scss, and it won’t have this new testcolor. If I continue looking at the inspector, the themes/mytheme/assets/dist/main.css will have the value correctly defined, but it is just not existing on the inspected code.

    Did I forget to configure anything?

    I hope I made myself clear, maybe this wasn’t asked the correct way. Thanks!

    Seems like importing
    <link rel="stylesheet" href="wp-content/themes/my_theme/assets/dist/main.css">
    In my header.php‘s header makes the page indeed use the variable I want of the compiled main.css file. I’m wondering if I missed some step on the installation process and the WordPress Theme is not using the correct variables? Ehitherway, now it feels like it’s working!!

    1. davidaz Avatar

      Can the problem be due to not installing the npm install dependencies on the host machine, and just compiling “locally” on my own pc? Just wondering

    2. them.es Avatar

      npm only needs to be installed on your local machine. And your custom-colors map code seems to work fine – the classes .bg-testcolor and .text-testcolor are successfully compiled on our test system as well.

      – Did you delete your browser cache and/or increase the theme version variable in style.css?
      – Alternatively you could try to define the new background-color directly via the classname e.g.

      .navbar { @extend .bg-testcolor; }

    3. davidaz Avatar

      Hello again,
      Indeed updating the style.css version seems to be the solution. Thanks for the quick response and of coruse for the great theme. Thanks to it I can do whatever I want 😀

      1. them.es Avatar

        Glad that your issue has been resolved and happy to read that the Starter theme is useful for you 😀

    Leave a Reply

  • npm “global” packages

    If you manage multiple themes with similar npm dependencies you should install npm packages globally and link them in your theme directories. First of all this saves a lot of disk space. But it also disburdens the upgrade process of development frameworks and toolkits that are used across projects.

    1. Install packages globally by adding the “-g” flag:
    $ npm install -g package_1 package_2 package_3 package_4 etc.

    2. Link the packages in your local theme directory/directories:

    $ npm link bootstrap @popperjs/core ...

    $ npm link material-components-web ...

    $ npm link autoprefixer css-loader sass sass-loader ...

    Happy Coding!


    Leave a Reply