Jet Engine 3.5 Components in Bricks builder

แชร์
ฝัง
  • เผยแพร่เมื่อ 29 ก.ย. 2024
  • Here's a look at the initial release of the Jet Engine Components released in version 3.5. We also use ACSS + Frames to quickly create the template used for the components.
    ► Learn more: ◄
    🔗 Jet Engine Components Overview - crocoblock.com...
    ► Connect with me: ◄
    📺 Subscribe: / @daveden2
    👍 Facebook: / daveden2
    🐦 X (formerly Twitter): x.com/Daveden2
    🌐 Website: daveden.co.uk/
    ► Recommended Tools (Affiliate Links - Support the Channel!) ◄
    🔗Elementor Pro - daveden.co.uk/...
    🔗Dynamic Shortcodes - daveden.co.uk/...
    🔗Crocoblock JetEngine - daveden.co.uk/...
    🔗 Bricksbuilder: bricksbuilder.io/
    🔗 Epidemic Sounds: daveden.co.uk/...
    🔗 Hostinger: daveden.co.uk/...
    #crocoblock #bricksbuilder #components
    🎵 Soundtrack:
    "Life is a Dream" by Michael Ramir C. 🎶
  • แนวปฏิบัติและการใช้ชีวิต

ความคิดเห็น • 24

  • @joewebdev
    @joewebdev 2 หลายเดือนก่อน +1

    Isnt Bricks going to be building this component functionality into Bricks Builder natively, making using JetEngine not necessary?

    • @daveden2
      @daveden2  2 หลายเดือนก่อน

      Yes, I eagerly await the native Bricks components feature.
      But I sense one difference: the Bricks component would probably only work within Bricks, while JetEngine works in Gutenberg as well.

  • @jean-paulmesserli8269
    @jean-paulmesserli8269 2 หลายเดือนก่อน +1

    Thank you Daveden. Your Clips are so helpful for me know.

    • @daveden2
      @daveden2  2 หลายเดือนก่อน

      I'm happy to hear that!!

  • @daveden2
    @daveden2  2 หลายเดือนก่อน +1

    Do you think you'll use components in your workflow?

    • @edywerder
      @edywerder 2 หลายเดือนก่อน +1

      Not sure yet I still feel a bit insecure to use it, but this video helped a lot.

    • @daveden2
      @daveden2  2 หลายเดือนก่อน +1

      @@edywerder, yeah, I feel they still need to work on a few bugs

  • @maxziebell4013
    @maxziebell4013 2 หลายเดือนก่อน +1

    Nice, I imagine this aligns with the upcoming Bricks components. I hope we can incorporate in-place editing. The user accessibility of this feature within Bricks is debatable, as it may require user access to Bricks, but it remains beneficial for general building. I would opt to retain the user in Gutenberg or utilize AT to streamline the interface.

    • @maxziebell4013
      @maxziebell4013 2 หลายเดือนก่อน

      We are currently using a fourth-party plugin on top of third-party plugins. I appreciate that this is being made available, but eventually, these elements need to be integrated into Bricks Core (or even WordPress Core). Components, frameworks, and client editing (or exporting as Gutenberg blocks). I am pleased that all these integrations exist at the moment and shine a light on the possibilities of modern development.

    • @daveden2
      @daveden2  2 หลายเดือนก่อน

      Yeah, I'm curious about the final native Bricks component would be like too. I'm not a very big fan of Bricks inline editing, I feel Gutenberg does a lot better with inline editing.
      If we let clients use JetEngine components in Bricks, we might need Bricksforge or AT to hide other elements.
      I like the fact that we can make a Jet Engine component in one builder and use it in any other. That's where it differs from Gutenbricks.

    • @maxziebell4013
      @maxziebell4013 2 หลายเดือนก่อน +1

      @daveden2 Yes, an interesting approach. I still have a license from back in the day. I should dust it off and experiment with it. It's a great feature even without considering clients. It adheres to the Don't Repeat Yourself principles, allowing you to construct your entire project using components. This way, a complex build can be easily updated, even with ID styles since there aren't many locations to update. Integration with global CSS or a framework further simplifies the process.

    • @daveden2
      @daveden2  2 หลายเดือนก่อน

      I agree. All of these separate parts can simply become one big integrated builder.
      Have you had a chance to test out the WordPress Patterns override in WP 6.6?

  • @anthonyespino7214
    @anthonyespino7214 2 หลายเดือนก่อน

    Hello, can I put a slider and then show it in a jet form builder field, bringing the post source and custom template?

    • @daveden2
      @daveden2  2 หลายเดือนก่อน

      Sorry, I'm not sure I understand the question. Could you explain a bit further?

    • @anthonyespino7214
      @anthonyespino7214 2 หลายเดือนก่อน

      @@daveden2 hello. I have a radio type field in jet form builder. I have dynamically brought a cpt into this field and given it a custom template (listing item). I need to show it in the slider form. Can I do it with component?

    • @daveden2
      @daveden2  2 หลายเดือนก่อน

      @@anthonyespino7214 no, a component would not help in this case. A component simply converts a group of elements into a template. But with the ability to change the text content per instance.

  • @IssaKhlief
    @IssaKhlief 2 หลายเดือนก่อน +1

    I am using CrocoBlock products for a few years now, and they are excellent.
    Bricks is planning to launch components very soon, I wonder how these will work?😅

    • @daveden2
      @daveden2  2 หลายเดือนก่อน

      Yes, I am excitedly waiting to see the Bricks native version as well!
      However, I suppose one difference would be that the Bricks components would likely only function within Bricks. You may not be able to use them easily in Gutenberg.

  • @YasirShabbir
    @YasirShabbir 2 หลายเดือนก่อน +1

    This is a great feature from the Crocoblock team, who are known for their innovative solutions. However, I believe Advanced Themer offers similar functionality with extensive controls and features we need. Nonetheless, it’s fantastic that we’re getting this in JetEngine, which means we’re not limited to just Bricks. What are your thoughts?

    • @daveden2
      @daveden2  2 หลายเดือนก่อน

      Yes, Advanced Themer does have the Strict Editor View, which is excellent.
      I think Jet Engine's components differ in that:
      ● All sub-elements (heading, image, etc.) are packaged as a single component.
      ● You can restrict the HTML tags that editors can access in the component (h2, h3, p). AT would only allow you to disable the entire heading tag control.
      ● The component works in both Gutenberg and Bricks.
      I believe both plugins can work seamlessly together to improve the editor experience.

  • @web-atelier
    @web-atelier 2 หลายเดือนก่อน +1

    Great video, thanks.
    To use it or not, I am waiting to see the brick's native component.

    • @daveden2
      @daveden2  2 หลายเดือนก่อน +1

      Agreed 💯 I can't wait to see what Bricks comes up with

  • @javierrivera7303
    @javierrivera7303 2 หลายเดือนก่อน +1

    excellent video. very good tutorial, very technical 👏

    • @daveden2
      @daveden2  2 หลายเดือนก่อน

      Thanks!!