Hello, thank you for the feedback. Welcome to Loops & Logic and the forum.
It’s true that CCS was a simpler plugin, easier to use with shortcodes. What happened was, I was creating more complex and bigger websites using CCS, and began to have difficulties due to the limitations of how shortcodes work, its syntax and parser (in WP core).
For example, the post content has many filters applied for automatic formatting, including the do_shortcode
function; this causes unexpected changes to the resulting HTML. Another issue was that shortcodes aren’t really designed to be used in a “tree structure” like HTML templates. They can’t be nested, cannot pass values to each other, don’t work well in HTML attributes, and so on.
L&L was created to freshly imagine a template language that’s seamlessly integrated with HTML. It solves the issues I had with shortcodes, and made the templates more extensible and scalable. But I agree it’s not as simple to get started as with CCS. We’re trying to improve it with better documentation, examples, and articles.
About ACF integration, there’s a documentation page listing the supported field types.
At the bottom of the page is a short explanation of how to get fields from an options page. Assuming the options page was added with the acf_add_options_page function, you can access its fields by adding from=options
to the Loop and Field tags.
Here is an example of getting child fields from an ACF group field.
<Loop acf_group=field_name from=options>
<Field title />
<Loop acf_image=image_field_name>
<a href="{Field url}"><Field title /></a>
</Loop>
</Loop>