Tell us what you are trying to do?
I'm trying to create a table view like shown on hidden link
The table (technische bijzonderheden) shows a table view with on the left the table header and on the right the value. Should I create a view (with filter?) or should I place the values from my custom post type and fields directly in the template in an html table?
Is there any documentation that you are following?
No, unfortunately there's no specific user case available. Overall there's not much info for a beginner to start with in my opinion regarding what views are and how to use them or when not to. I've spend a lot of hours to find something I could use or suits my needs, but It is still very technical and global info most cases.
Thanks. I will try and do that. But I would also like to now why? When should I use a view and why do i have to use a content template in this case. This info would help me a lot understanding the choices I should make in the future.
No I’m not using block builder as I’m using WP Bakery instead. Don’t like the guttenberg editor.
So in this case you will use a content template. I'm under the assumption that you want to customize how you are displaying your Single post items on the frontend. This is what content templates allow you to do.
For views they are for when you want a list of posts to be displayed on a page using some query, for e.g List of post attached to taxonomy A.
Since you want a table and i'm assuming the values for this table will be stored on the single post then a content template or some form of page template will be needed.
So I see you are using WP Bakery to do your templates so this will work just as well.
That's correct, so simple said. For one item there's no need the create a view. Only when I need a list of items from a loop? Would love a step by step tutorial section where also different scenarios are discussed. Toolset claims to be simple and without coding any needed. But the reality is that, at least in my case, the available documentation handles only the basics for the most part. To help people understand how to use the different elements, it would be really nice if you guys created a step by step section with multiple scenarios in mind for the same solution or end goal. Also the why is very important in my opinion.
Thanks, also for understanding. People like me (beginners) need real step by step tutorials, without leaving anything out. This means describe all steps even if mentioned in other tutorials and related to the specific user case at hand.
That said, it would really help if the tutorials refer to real user cases and/or examples instead of general info. And also what NOT tot do in specific situaties and describe the consequences when people make wrong decisions or at least other then described. The "why" is most import for understanding and correct decision making. I guess it would reduce the support load as well for you guys for recurring questions.