We are building a platform where users can create a simple styleguide. They can upload multiple variations of their logo (colored, black/white), some sample images for brand content, upload their fonts and define the colors used.
The users should be able to create their styleguides from the frontend (with CRED).
Now to my question: what is the best approach to allow users to create multiple instances of a certain type of content (e.g. logo)?
At first I thought, repeating fields are the way to go. But now I'm not sure anymore. Repeating fields seem fiddly. With child posts and relationships I think we can create a more polished user experience. Am I right or do I miss something?
I hoped it would be possible to create a styleguide with only one form. But maybe we have to split the creation into several steps, e.g. first the logos, then the colors, and so on. What do you think?
I hope you see what we want to achieve and can give us some insights.
2. You can use a fixed number (e.g. 2,3,4,5 etc) of regular and predefined fields to collect information in a single form. e.g.
Image file for variant 1:
Color code for variant 1:
Image file for variant 2:
Color code for variant 2:
… and so on
If your preference would be to collect all the information through a single form and would also like to make this information editable in the future (by users), option 2 is the way to go.
I hope this helps! Please let us know if you need any further assistance.
Thanks for sharing your thoughts. What do you think about using child posts? If I split up the creation into multiple steps, this seems to be a valid option as well. In a first step the user creates a style guide. Then he has multiple forms to add logos, colors and so on and they all display on the parent styleguide page.
This even brings the advantage, that you can work on your style guide over time without having to complete the form at once.
If you're leaning towards the idea of a multiple steps data submission, then the parent-post relationship is the way to go.
For clarity and clutter-free experience, you can split the child steps (logos, colors etc) into custom post types of their own and then assign them as a child in the one-to-many or one-to-one relationship (as required) with a parent post type "styleguide ".
