Getting Started with Advanced Themer - My recommended Theme Settings (Part 1)

Поділитися
Вставка
  • Опубліковано 8 лют 2025

КОМЕНТАРІ • 31

  • @lencarter9070
    @lencarter9070 9 місяців тому +3

    Yes, I've been a bit overwhelmed. Thanks for the detailed explanations!

  • @jpk6916
    @jpk6916 2 місяці тому

    Nice and important video! Thanks

  • @prompt_shark
    @prompt_shark 9 місяців тому

    Thank you for this run down. I am new to page building and web design in wordpress and I have gone all in all Bricksbuilder and Advanced Themer as well as ACSS. This stack really makes page building a blast. So powerful and it produces really clean code which is what convinced me to make the transition.

  • @guga_cl
    @guga_cl 9 місяців тому

    Amazing video series !!
    It is very useful !
    Greetings from Chile

  • @genethompson9154
    @genethompson9154 9 місяців тому +1

    This was really useful - thanks !

  • @webcare_live
    @webcare_live 9 місяців тому

    Thank you, this was quite helpful!

  • @BGdev305
    @BGdev305 9 місяців тому

    This detailed walk-through / explanation on settings is right on time!
    Question..
    @13:44 It would be GREAT to be able to "link to" an external stylesheet! Meaning, have a field to enter URL to a stylesheet and AT could parse it like it does with one that is uploaded. This provides more options for including styles from that aren't in wordpress install and I'm using some styles from CSS I'm using from a totally different site AND server.
    From a development stand-point I could attach to different CSS not local to this install.. WHILE having the styles parsed in AT, thus available in the builder!

    • @maximebeguin4346
      @maximebeguin4346 9 місяців тому +1

      I used to test that option, but for some reason it kept creating fatal errors and I just gave up… 😢

    • @BGdev305
      @BGdev305 9 місяців тому

      @@maximebeguin4346 http / https conflict maybe? CORs? What about doing it with API call? Just thinking out loud lol.

  • @LupusDesign
    @LupusDesign 9 місяців тому

    Excellent!

  • @John.Rearden
    @John.Rearden 9 місяців тому +1

    Probably go the OS route and give customers customisation options to make life easier.
    3 Toggles at the Home Screen of AT
    1) Recommended
    2) Recommended with Frameworks
    3) Customise

    • @AdvancedThemer
      @AdvancedThemer  9 місяців тому +1

      Sounds easy isn’t? 😂

    • @hamburger--fries
      @hamburger--fries 9 місяців тому

      @@AdvancedThemer Sounds like 6 months of planning. Coding, bug testing....LMAO :-)

    • @John.Rearden
      @John.Rearden 9 місяців тому

      @@AdvancedThemer The idea being, AT becomes plug and play, instead of having to go through endless customisation which can be overwhelming for beginners to AT.
      Definitely not easy haha, but plug and play would be a great option to consider.

  • @groundpets5101
    @groundpets5101 9 місяців тому

    good work :)

  • @febryanvaldo
    @febryanvaldo 6 місяців тому

    Hello, i'm using Core Framework (the free one Web Based). Could i integrate the CSS of Core Framework with AT?

  • @OneBrokeBloke
    @OneBrokeBloke 9 місяців тому

    Are those variable shortcuts within the builter (like margins fields fx) something that only AT achieves, or are other programs or frameworks also doing that?
    Ive seen them in lots of videoes online, and they seem almost essential to using variables efficiently.

  • @NelmediaCa
    @NelmediaCa 9 місяців тому

    Question: I understand that some features have been marked as legacy, since they are available in drop-down menus... But like you, there are some that I still like to turn on... BUT, usually legacy also means that they will eventually disappear... SO, should we keep on enabling them for new sites, as they will stay there, or we shouldn't because at some point in a short, middle or long-term they will disappear?

    • @AdvancedThemer
      @AdvancedThemer  9 місяців тому

      I'm not planning to remove them any time soon. Some are still pretty useful to have as a quick shortcut. Though in future my focus will be to add new features inside the corresponding menus instead of creating shortcut icons.

  • @flekz384
    @flekz384 7 місяців тому

    i dont have the tab "global css variables", i only got "css variables" and i only have "Import Framework and Theme Variables als Submenu, i dont have Typography, Spacing, Border and i have no more options to toggle something on. what am i doing wrong?

    • @AdvancedThemer
      @AdvancedThemer  7 місяців тому

      That has been changed since 2.6 which now integrate the global variables inside the builder (as bricks variables). Make sure to check my video overview of 2.6 👍

  • @spacevertex
    @spacevertex 9 місяців тому

    The only big ticket thing missing is an integrated CSS framework. Bricks can be framework agnostic, but add-on developers replicating that agnostic stance deprives customers of value.
    Imagine if AT had an integrated CSS framework of its own, then it would be bang for the buck.
    Bricks + AT is all one would need.

    • @AdvancedThemer
      @AdvancedThemer  9 місяців тому +1

      Do we really need another framework though? Core, ACSS, oxyprops, tailwind, etc… I feel like there are plenty of choices already isn’t ?

    • @spacevertex
      @spacevertex 9 місяців тому

      @@AdvancedThemerAs Bricks matures, the value of AT will keep diminishing, as Bricks will implement many of the features of AT.
      But CSS frameworks will mature too, and Bricks is agnostic to CSS frameworks.
      For AT to have long term viability as a must have, I see no other option but to have an integrated CSS Framework built within AT.
      You have brought world class innovation to AT, I reckon that you can apply your mind to bring innovation to CSS framework for Bricks.
      Something to think about!

    • @AdvancedThemer
      @AdvancedThemer  9 місяців тому +4

      I’m not convinced Bricks will add most of AT features. Some for sure. But even if it happens, I’m not planning to watch it with my harms crossed. I’ll keep improving the existing features, and add new ones. I can’t see the value of the tool at risk really.

  • @kappesante
    @kappesante 9 місяців тому

    🥰

  • @hamburger--fries
    @hamburger--fries 9 місяців тому

    Great video! When will you release the part 2 with ACSS.

    • @AdvancedThemer
      @AdvancedThemer  9 місяців тому +1

      Tomorrow 👍

    • @hamburger--fries
      @hamburger--fries 9 місяців тому

      @@AdvancedThemer I am so excited! I am doing a massive project and am so confused how Automatic.css works with AT and Bricks. I am the guy using Bricks to code with ReactJS. I created a custom router for wp-scripts.

  • @johnosmond10
    @johnosmond10 7 місяців тому

    Why is it that every time I spend an hour or more watching a video about Advanced Themer, almost nothing in the video matches what I see in the software? CSS Variables tab is missing almost everything you pointed out in this video. There is nothing about typography, nothing about spacing, borders, border radius. This video is a waste of time.

    • @AdvancedThemer
      @AdvancedThemer  7 місяців тому +1

      This video has been recorded before Bricks released their variable manager inside the builder. Since then, we released v2.6 which converted the variables created inside the theme settings into native Bricks Variables. It allows you to manipulate your variables right inside the builder rather than going back and forth from the admin, and it won't create conflicts in case you deactivate Advanced Themer.
      Bricks and Advanced Themer are two softwares that evolve quickly, and I think that it's in the interest of the user to have AT quickly adapting to Bricks based on the updates it provides. The truth is - beside the variables tabs - all the other options in the actual version of AT are pretty much the same as the ones shown in the video. The recommended settings have also been implemented as default values when installing AT on a fresh install (or when resetting the the theme settings).