135
Support for more advanced structures and reusable components
in progress
Victoria Bresman
Our current templates and field types are pretty basic, and so we plan to add some functionality to make them a lot more flexible. This should make it really easy to create more flexible content structures, and also save some time when you have the same kinds of structure used on multiple items in your project.
The idea is to make it possible to create custom components out of a group of fields (or even a single field), and then have these accessible in a component library so they can be quickly added to items on the fly. This means you could have a component that's used inside templates and custom structures, and which can be easily updated from a single place. Which should save a bunch of time!
We're also keen to make it possible to say that a component should be repeatable on an item. This should be useful for things like galleries, or lists of things, where you're not sure how many you need from the outset.
Finally, we're also keen to review our field types themselves, and look into more specific field types to support more structured content. Also just improving the validation on fields, so you could say a field is required, or has to include a certain format of content.
This is in the very early stages of planning, so please let us know your thoughts.
Log In
Activity
Newest
Oldest
James Peacock
Hi folks. I wanted to share an update with you regarding components, namely a video walkthrough of a prototype demonstrating the creation of a component and adding that component to a template.
You can view the walkthrough here (7:38): https://share.getcloudapp.com/JrugPz7Y
You may have noticed our updated fields went live today, which means we can really start driving forward our component feature. Timelines remain unchanged from my previous comment (Q4 2020 beta/release). We will be working closely both internally and with our partners to determine which plans have access to components and this will be shared prior to release.
Let me know if you have any feedback or thoughts on any of the above!
Thanks.
Laura Salter
@James Peacock: This is AWESOME. I am very excited.
One comment I have... once I've added a component to a template (or a custom structure) on an item, I would like to be able to give that component a title/help text that is specific to that template. I wouldn't want to rename the component, but have an additional title and description.
e.g.) Image Gallery (component)
Employee Gallery Images (title)
Upload up to 5 images of your employees at events or having fun at the office. Photos should be 1200px x 1000px. (description)
Thanks!
James Peacock
@Laura Salter: Hi Laura. This is actually something we have been discussing recently - how can I repurpose a component for similar but different needs, without creating a brand new component.
Our first thought is to allow people to change the label of a component once it is added to a template/structure, just in the same you rename fields once you add them. So in your example, you'd add the 'Image Gallery' component, and simply rename it to 'Employee Gallery Images'.
Your next point is a little more involved, but it is very valid. Is it a case of adding a guideline field and allowing that to be edited at a template level? Or give components instruction text, like fields? Leave it with us!
F
Frank Desiderio
@James Peacock: Thank you james! Looks very promising. Can't wait to begin using it at the earliest (and hoping our project will still be active by the time it is released).
To Laura's point below,
I've been adding description fields BEFORE/OUTSIDE our current cobbled-together components, and wonder if, in the short-term, that same method may suffice with actual components (rather than have any kind of editable description be part of the component itself)
Mike Mason
@James Peacock: This looks great! One thing that stood out to me after watching was that it would be nice to be able to attach a thumbnail to a component template. This would allow the user to visually identify what a component will look like on the website when the content is moved over into our CMS. See image below for example of a doc I have created of our web components.
James Peacock
@Mike Mason: Hi Mike. Nice idea. Our work on asset management brings with it inline images. So a solution to this would be to add a guideline field in the component, and add any supporting imagery in there. In the meantime, adding a guideline field and linking to any supporting imagery would be a good workaround.
Carl Dunker
@James Peacock: Will components be shareable across multiple projects?
James Peacock
@Carl Dunker: Hi Carl. In the first instance components won't be shareable across projects, but you will be able to import components from other projects so you don't have to keep building them from scratch. We are looking into ways to introduce 'global' features, so things like components, templates and files shared across projects, but as yet not on our immediate roadmap.
James Peacock
Merged in a post:
Connected Fields / Fields Container / Field Groups
Laura Salter
I would love to see the ability to group fields together.
For example, we might have a Call to Action content block that would be made up of a Title, Short Description, and Button Text.
Currently, I would either have to use one text field for this and describe its pieces in the description (making it difficult/impossible to impose length restrictions on each particular piece of the CTA), or break it up into three different fields (making it difficult to show that they are connected).
I envision this working as such:
- Choose "grouped fields" or "container" from the list of field types.
- You could then name that container.
- Then, you could drag and drop whatever fields you wanted within that container.
I might choose a file upload, a text box, a second text box... whatever!
This would be amazing and would more closely mimic the CMS experience our clients will ultimately have in WordPress with ACF.
James Peacock
Hi everyone, we're actually working on a solution for this at the moment, which we're calling 'components'. They will work exactly as you describe. You'll build your component with whichever fields you wish, save it, then add that component to your structures/templates. You'll even be able to set the component to be repeatable, which will allow editors to create new instances of that component on the fly - super handy for things like image galleries, which could contain an asset field for the image, and text field for the description.
You can see more information on the progress we're making over on this Canny request: https://gathercontent.canny.io/feature-requests/p/support-for-more-advanced-structures-and-reusable-components
I'll also merge in this post so you can stay up-to-date.
F
Frank Desiderio
@James Peacock: Hello James. Thank you for your help on this critical (to us) functionality. Is there an ballpark ETA you're able to share for a beta? days? weeks? months?
Y
Yve Zotique
@James Peacock Hi James! I'm also super interested in the idea of reusable components that are a grouping of field types and can be pulled in to pages and/or templates. Is there a beta version available for use? Thank you!
F
Frank Desiderio
@James Peacock: equally interested in beta access too please :)
James Peacock
Hi @Frank Desiderio and @Yve Zotique great to see your interest in this. We're hard at work on components as we speak and are expecting both beta and release during Q4 of this year. Due to its popularity and the power it will give users it is our top priority right now, but although we want to get it in users' hands as quickly as possible, we also want to get it right.
This is why, as part of its development pipeline, we're introducing improvements such as newly designed fields (which you can see in a previous comment below). Left-hanging field names weren't compatible with our solution for components, so fields will have their names above, condensing fields into a single-column. This actually fixes a number of issues outside of components, such as quirky behaviour observed with longer field names, and also drastically improves usability on smaller screen sizes (though I admit we still have some way to go here).
We're also working on major performance improvements with field loading times. We're seeing huge reductions in loading times for items in testing, so I'm excited to get this release with you as soon as possible. The advantage this brings when working with components is clear.
In tandem with the components release, we're also working on improving the way we handle files. We're calling it 'single source of truth,' and it will finally allow the management of files outside of items. It is our first step in bringing our asset management into the 21st century. Upload files outside of items, comment on files themselves, quickly replace all instances of a file by replacing the master file, add alt tags to files. Again, we're working on releasing the first iteration of this during Q4 this year.
So, there's plenty to look forward to in the coming months. You'll be the first to know when we have a beta available to test!
In the meantime, feel free to ask me any questions.
James
F
Frank Desiderio
@James Peacock: thank you sir. this feature set will be key to the successful delivery of a global project of Ogilvy's/WPP's that's currently in-progress. We are keen to participate in the beta (alpha?) program the moment it becomes available, if not sooner, please
Nathan Mico
@James Peacock: I've just gone through the steps to create repeatable fields, and it's not showing up as an option anywhere. Is this because they only work on new templates, not existing templates made before the feature was added? I'm at the start of a content development project and am starting to setup the templates for this now. Any help you can give me would be great.
James Peacock
@Nathan Mico: Hi Nathan, sorry for the delay in getting back to you. Repeatable fields are only available on Scale and Transform plans. If you are on a legacy plan you'll need to upgrade to one of these plans to take advantage of them. If you already are on one of these plans and you still have trouble seeing them, reach out to our support team who'll be more than happy to help, and will frankly be a lot more responsive than me here on Canny!
M
Matthew Stevenson
This would be helpful. I think this comes in to play especially when you are using the repeatable option to add new items. You would want a title, description, and other fields all added for each new item added.
James Peacock
Hi everyone. In order to make components as intuitive as possible, we're working on ways to simplify fields. Originally fields were designed with labels hanging on the left in order to create a more seamless reading experience, but over time we have seen how being left-aligned has really hindered the user experience when long field labels are involved, especially when coupled with enabled field settings.
With that in mind, we'd like to get your feedback on a single-column approach to fields. This will allow for improved clarity for longer field labels, as well as containing field settings inside of fields themselves, rather than hanging on the left.
We're currently running a usability test and would love for you to get involved, testing the usability of the new fields in the structure editor. If it's something you'd be interested in helping with, you can access the test at this link:
For those of you who might not have time, you can find a preview of the new fields attached to this post, including an early look at a component.
Thanks! Any and all feedback you give will be super valuable.
Mike Mason
@James Peacock: I also spy field groups! 👀🎉
James Peacock
Hi all. Just a quick note to say that you now have access to the repeatable fields beta! As I mentioned previously, you can enable the setting on text fields in the structure editor.
We have a feedback survey ready for when/if you feel like sharing your thoughts on the feature here: https://gather-content.typeform.com/to/WAgtzH
You can also access this survey by clicking 'Give feedback'. We will be monitoring usage and feedback over the next couple of weeks.
Thanks, and we hope you enjoy using repeatable fields.
James Peacock
@Rachel Bertsch: Hi Rachel. It looks like you've enabled the setting, but the repeats themselves are added in the content editor.
Mike Mason
@James Peacock: I am not seeing this option enabled in my account yet
James Peacock
@Mike Mason: Hi Mike. Seems we had the same issue as before. I have enabled repeatable fields on your account now. I'll be in touch to see if we can prevent this happening again.
Mike Mason
@James Peacock: Sounds good, I see it now. Thanks!
Carl Dunker
@James Peacock: Strange. I’m not seeing this on my account either.
James Peacock
@Carl Dunker: Hi Carl, I've enabled the feature for you now. Looks to be the same issue as with Mike. When users sign up to Canny manually it isn't tied to their GC account, and then creates a duplicate account in Canny. I'll need to do some digging around to see how we can solve this for all users moving forward. Sorry for any inconvenience.
James Peacock
Hi everyone, I hope you're all keeping well. Over the past couple of months we've been quietly working away towards our goal of supporting more complex structures. Thanks to your participation in the survey we sent out, we have identified key areas that we need to improve in order to reach our destination of component-based structures.
The logical first step is the introduction of repeatable fields, and I'm happy to reveal you'll be able to get your hands on this feature, in beta, next week. In the first instance we'll be making text fields repeatable, and will be constantly monitoring usage data and feedback in order to meaningfully iterate the feature in the weeks to come.
Text fields will be made repeatable via the field settings menu in the structure editor, with the option to limit the number of instances of that field. In the content editor, authors can add and remove repetitions, and more importantly, reorder them.
You'll be given the opportunity to provide specific feedback on this feature when the beta rolls out next week.
We hope you find this first step a welcome addition to the app.
Rachel Bertsch
Yes to component based instead of template based layouts. This allows for more flexible content design and page layouts without repeating a million fields that will not be used.
James Peacock
in progress
Hi everyone, as the most requested theme of feedback we have for GatherContent, I'm happy to announce that we're starting work on bringing you more flexibility with fields and structure.
Some of you may have received a survey from us and we would appreciate it if you could spare 5-10 minutes answering some questions as your answers will directly help shape what this feature will look like.
Thanks to everyone for your on this so far. We read and take on board everyone's comments and can't wait to get some exciting updates onto your screens in the near future.
P
Pete McFarlane
Hi Laura, thanks for the suggestion. Have you tried to use tabs for this? Did that work somewhat or not at all?
Laura Salter
@Pete McFarlane: Hi Pete... tabs doesn't really work for this, in my opinion.
In our web design agency, Gather Content is both a precursor to wireframes and to setting up the website admin. A page in Gather Content should therefore flow like it will as a webpage layout and also be editable in a similar way to how it will be in the admin.
Hope that makes sense!
Load More
→