Hello and thank you for contacting the Toolset support.
Before trying to elaborate on the requirements of your project, it is worth to mention each Toolset element that would be used and what each is meant to be used for. Our glossary is an interesting introduction to each of them https://toolset.com/glossary/
- Posts, Fields, Relationships, and Taxonomies are meant to hold and organize data.
- Custom Post Types are the core data element. WordPress includes default custom post types(Post, Page, Media) and Toolset allows you to create your own(Course, Chapter, etc.) https://toolset.com/glossary/custom-post-type/
- Custom fields allow extending posts with additional data(dates, numbers, choices, etc.) https://toolset.com/glossary/custom-fields/
- Toolset Relationships allows creating relations between data in different ways(one-to-one, one-to-many, many-to-many). A course can have multiple chapters for example. https://toolset.com/glossary/post-relationships/
- Taxonomies are a way of organizing posts in sets or classes(called terms in WordPress).
- https://toolset.com/glossary/taxonomy/
- https://toolset.com/glossary/taxonomy-term/
- Views, Content template, and Archive are meant to query, search, and display data.
- Archive templates are a default WordPress feature to display a list of posts, Toolset allows to customize how the data is queried and displayed. https://toolset.com/glossary/archive/
- Content templates are meant to display ONE post. They can be used inside a view's loop, an archive's loop, or inside another content template. https://toolset.com/glossary/template/
- Views are meant to display a list of posts. They use WordPress WP_Query to query the database of posts.
- https://toolset.com/glossary/view/
- https://toolset.com/glossary/wp_query/
- Forms are meant to allow the user to interact with the system from the frontend. A form can only create or update ONE post.
Toolset also offers a condition system in different parts. Conditions can be set for custom fields, they can be used inside content templates, views, and archives. They can also be used inside forms. Not all the possible conditions are available for all these cases, for example, the conditions on forms are very limited.
- https://toolset.com/course-lesson/custom-fields-conditional-display/
- https://toolset.com/course-lesson/using-toolset-conditional-block/
- https://toolset.com/documentation/legacy-features/views-plugin/conditional-html-output-in-views/
Toolset also allows extending taxonomies and users' data with custom fields. Read more about it in our documentation:
- https://toolset.com/documentation/user-guides/user-fields/
- https://toolset.com/documentation/user-guides/views/term-fields/
Please note that Toolset has introduced Toolset Blocks and some of the above articles may be related to the legacy Toolset Views(based on shortcodes).
https://toolset.com/2019/11/toolset-views-becoming-toolset-blocks/
You can still activate the legacy views editor in Toolset settings.
This being said, I'll try to answer some of your questions in a general manner.
To track the progress of a certain user, you can use posts for which the user is the author(eg. Certificate).
You can use views to query user's posts that have a certain value for a custom field(eg. Status)
You can use conditions inside views to display different elements depending on the user or post data(eg. different buttons depending on post status)
I wonder if this gives you a general idea of how Toolset works and how you can implement your requirements. Let me know if you have any questions or you need any more details.
However, for support rules, we are able to handle only one issue at a time. This helps us to bring you a better service and also helps other users to find all the information here exposed. For that reason, I have to kindly ask you to open a new thread if you need to elaborate more on any specific requirements of your project. You can assign it directly to me. In that way, you don't have to wait and we can continue working on it.
