Custom landing pages powered by Metaobjects announced in Shopify's Summer ’23 Edition

Поділитися
Вставка
  • Опубліковано 25 лип 2023
  • We’ve released a new way to build and manage custom landing pages. Add structured content, like influencer profiles, FAQs, and store locations, with metaobjects.
    Discover more of the 100+ features in our Summer '23 Edition shopify.com/editions
  • Розваги

КОМЕНТАРІ • 16

  • @Supp1989
    @Supp1989 10 місяців тому +7

    0:42 Is there a tutorial or example how to create a quiz with metaobjects? Sounds really interesting

    • @inquisitivemind99
      @inquisitivemind99 10 місяців тому +1

      Exactly. That's too much of a tease - please tell more!

  • @gouravkumar772
    @gouravkumar772 10 місяців тому +1

    Metaobject organizes my content very well .

  • @ArdenCove
    @ArdenCove 10 місяців тому +2

    Will that product lists section be available to all templates soon? I couldn't find in Dawn or our custom template? Or is there any documentation on how to implement?

  • @ochies
    @ochies 8 місяців тому +1

    Do you plan to create a dynamic list of all products referencing the metaobject?
    It does not make sense to add the 'Products' manually, since a store is constantly updating, adding and deleting products. If we need to add/remove products manually for each metaobject it can be very time consuming. We should only apply the metaobject on the product page.

  • @DrazOutshineGaming
    @DrazOutshineGaming 10 місяців тому

    Our business will 100% utilise this!

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

    Hello. Is there any option to create an archive page for these metaobjects? Let say we create a metaobject 'services'. We may create individual services there but is there a way to created a page with entire dynamic list of these services?

  • @InvestTaner
    @InvestTaner 4 місяці тому

    Greater efficiency, Perfect 👍

  • @user-zb4gh2mg7k
    @user-zb4gh2mg7k 8 місяців тому

    I'm following this and attempting to build out a page as per the video, can anyone help me understand why I don't have the 'Product List' block available to me in the template? Or how I would make that available? Thanks

  • @louisb1
    @louisb1 10 місяців тому +2

    Great explanation & example. Can’t wait to do a deep dive into this and explore other use cases

  • @LivaEntertainment-nd1sg
    @LivaEntertainment-nd1sg 9 місяців тому

    Very nice

  • @HR-Services
    @HR-Services 10 місяців тому +1

    That's a great, helpful feature. Nevertheless, the product field ought to be dynamic, not static (ua-cam.com/video/lJRul3VdiU4/v-deo.html), since products frequently change and go beyond the range. Or am I mistaken?

    • @ochies
      @ochies 8 місяців тому

      Yeah, that is right. Since products are frequently changing, it should be a dynamic list of products. The metaobject gets all the referenced products, but I can't use it on a dynamic source - only if we hardcode this.
      There should be an option "Referenced Products" so we can add the products automatically

  • @foysalshopifyexpert
    @foysalshopifyexpert 10 місяців тому

    Great explanation & example.

  • @heathhudgins5636
    @heathhudgins5636 10 місяців тому +3

    I don't quite understand what this approach gains you over creating page templates and page metafields. Does this allow you to use the metaobject not only on a page but also within other templates/features?
    Edit: after thinking about it a bit more, not only does it allow metaobjects to be used in other functionality and on a unique page at the same time, as I mentioned above, but it also improves the admin experience tremendously.
    How? In the approach I mentioned first, around using page metafields, you'd essentially need many many duplicate page metafields, all individually detailed out and lumped together. I've done this, it blows. Alternatively, you could still create a metaobject and create a page metafield for this metaobject. That's clunky, too, because you have to hardcode references to that object in sections. Not a good option either. Now, we have a much better way. No only do you have access to the individual metaobject fields in the theme customizer dynamic sources via this technique, the metafields/settings aren't all grouped together with unrelated and unneeded metafields