-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Demonstrate content components #28
Comments
Hi, looking for an open source project to work on and as I have been experimenting with Kontent this seems like a good first step. Please get in contact to organise Kentico Cloud credentials so I can create a few Content Components. Also happy to jump on #25 |
Hi @JeremyOsz, thank you for your interest. I've already sent you an invite to the Kentico organization. Once you accept it, I'll be able to assign you this issue. Since I believe the description of this issue is quite unclear, I'm going to gather more information. In the meantime, you can contribute to the mentioned issue #25. Thank you! Edit: Everything is clear, this issue is ready for the implementation 😎 |
Hello @makma, is this issue still open ? |
Hi @galanggg, it seems it is. I've already sent you an invite to our organization. Once you accept it I can assign you this issue. Happy hacking! |
Thanks, @makma so I just make some projects to demonstrate content components ? |
I'd recommend to clone source Kontent project |
Motivation
In Rich text elements, one can create non-reusable, typed chunks of content called components.
Proposed solution
Use the "Component-only type", together with the "Component-using content type" types to demonstrate the usage of components.
Additional context
Should you wish to create some more real-world content types for the starter, drop a comment to this issue to get edit permissions to the project in Kentico Cloud.
The text was updated successfully, but these errors were encountered: