A few suggestions?

Thanks for the suggestions, Luis! To take them in order:

1. I am certainly open to having the “Tailor this..” link outside of the Admin Bar. I hesitate to do so given that users can begin Tailoring pages from the front end too, and in that context I think it makes sense to have it up there alongside the “Edit page” link. What are your thoughts on this use case?

2. I agree with this suggestion, though this is a little difficult to achieve in practice. One of the benefits of Tailor is that it doesn’t replace your content with shortcodes; only elements that are dynamic (like recent posts) and should change between page saves are saved as shortcodes. For this reason, you cannot easily enqueue scripts based on whether a carousel exists on the page as this would typically be done in a shortcode, which aren’t used for carousels. As I see it, there are a couple of potential solutions: 1) use a shortcode for the carousel element and other static elements like Gallery which have a carousel layout option or 2) store some meta data against the post containing the script dependencies and enqueue them based on that. Again, I’d love to get your thoughts on this.

3. I am also open minded about using Tailor in different contexts. With respect to your ACF proposal, could you give me a brief description of how you’d see that working?

Thanks again!
Andrew.

Hey Andrew,

super nice plugin! How would you approach custom post types to integrate with your plugin?

Do I need to write another plugin therefor? In some cases we already have custom post types setup like Jetpack’s portfolio feature where it is not neccessary to create another custom post type.

I know that you can’t foresee how every custom post type in the world is setup with custom fields, data, etc.

However in basic cases custom post types work the same way as posts where you have a featured image, content, categories and tags. Would it make sense to implement a switch in the Posts Element within the builder where you can modify the post type?

Cheers,
Felix

Hi Felix,

Jetpack’s portfolio/project post type has been pointed out to me before and am interested to add support for it in an upcoming release. Keep an eye out for that!

Generally speaking, you’re right: we cannot know up front what attributes a custom post will have nor what display format makes sense for them. For that reason, I would suggest creating a simple extension for Tailor to fully support whatever custom post type you need (or let me know and if there’s sufficient interest I can built one myself).

If your custom post has all (or most of) the same attributes as a standard post, I would question why it is a custom post in the first place. Tailor allows you to select categories and/or tags to display, so if your custom post is similar in nature to a standard post you could create a category for whatever it is you’re wanting to display and then tweak the look and feel using the tool.

Whatever the case, do let me know as I’m very interested to learn more about how people are using Tailor (or how they would like to in the future)!

Cheers,
Andrew.

Hey Andrew,

custom categories belong to the corresponding custom post types only and are not accessible from the standard post type categories list.

Sometimes Custom Post Types help to have a clearer information architecture although they are following the same principles as posts and pages.

However, I would love to see a tutorial how to write an extension for Tailor to connect with already existing custom post types and custom fields (e.g. Advanced Custom Fields).

Keep up the good work!

Cheers,
Felix

Hi Andrew,

Many thanks for your comments.

1. I see your point. I wouldn’t mind having the option on both locations actually. The top bar is a crowded space with plugin like yoast filling that area. It’s just a small detail.

2. Well, not having shortcodes all over the place is another thing I love about Tailor so if the consequence of that is loading a few assets im pretty ok with it.

3. In some projects I use ACF fields to create different content regions on one give page. But after this a little more though, it might not be as important as I first imagined, and considering the implications when editing from the front-end as you mention on point 1) it might as well be ignored.

Thanks again Andrew.

Thanks again, Luis.

Adding a button as well as (or perhaps even in place of) the current Admin Bar is something I am happy to explore. Keep an eye out for this in the future ??

I would like to add some sort of support for ACF too. I’ll have a think about this and will happily accept any pull requests from people over on the GitHub project.

Cheers,
Andrew.