An important Liquid object in the above snippet is metaobject.system which allows you to access various properties of a metaobject, including its URL path (as long as that metaobject has online_store capability). You can learn more about this object and other use cases in our developer documentation.
In the above snippet, the metaobject.name serves as the link text, while metaobject.system.url provides the relative URL. These objects can be argentina telegram screening combined with the link_to Liquid filter to generate a full link element with HTML link tags for each metaobject entry.
By default Liquid loops will return the first 50 items, so if you anticipate that a merchant will have more than 50 metaobject pages, you can implement pagination. This also gives you more control over how many items are returned, if you want to organize the index with a specific number of links on each page.
You can use the paginate tag to define how many items will appear on each page, and the paginate object can be included with the default_pagination filter to generate the necessary HTML elements for pagination links. Once implemented, your code will look like this:
Now, when there are over 25 links to metaobject pages, the pagination will be triggered and the additional links will be accessible on the next page. In this example I’ve used 25, but you can use any number up to 50.
Now that you’ve populated this section with this Liquid for loop you can assign the section to the custom page template created earlier. An example of how this could look.