Add non-canvas element management with controller and service integration#574
Add non-canvas element management with controller and service integration#574stijnpotters1 wants to merge 6 commits into
Conversation
|
Looks good! There is a difference between the pen-pot tho. In the design, there can be two rows in each component. A type and a name (or ref in the case of an include). The type should be small and bold while the name would be larger. Is there is no name, the type should be the same styling as the name would've been. Also, I think elements should just be called components. 
Also, I think each component should be clickable to configure it, even if it has a button to go to the studio. That makes it easy to rename an adapter for example or to delete it. |
Improved! |
There was a problem hiding this comment.
Maybe sub components defined here should be in their own files
…ler integration and improved frontend according to feedback
…s non-canvas components
…implementations with ContextEditorFooter for improved consistency and clarity
stijnpotters1
force-pushed
the
feat/add-non-canvas-elements
branch
from
bfb10e5 to
fe2d1bd
Compare
|
|
It might be interesting to explore the possibility to give this a more flat and calm design. |
3 participants
Uh oh!
There was an error while loading. Please reload this page.