You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently evaluating Puck for use in my project and this is by far the most intuitive DnD page builder I've come across! I just have one small question which I'm not sure if I'm just over looking.
Is there a way to render the editor in available space rather than it being position: fixed, left: 0, top: 0?
I've got a side navigation in my app, and the main content area to the right, and I want to render the editor in the main content space, rather than it taking the full screen width as you can see in the screenshot, it always renders behind my own side nav. I've tracked it down to the following CSS, but because the below CSS is applied in a Nested <div> I can't seem to get a CSS selector to actually target the position: fixed in order to override it.
hello, first good job and promising project. It will be great to get a way to override the global layout passing some style props.
thanx again to share it
Hi!
I'm currently evaluating Puck for use in my project and this is by far the most intuitive DnD page builder I've come across! I just have one small question which I'm not sure if I'm just over looking.
Is there a way to render the editor in available space rather than it being
position: fixed, left: 0, top: 0
?I've got a side navigation in my app, and the main content area to the right, and I want to render the editor in the main content space, rather than it taking the full screen width as you can see in the screenshot, it always renders behind my own side nav. I've tracked it down to the following CSS, but because the below CSS is applied in a Nested
<div>
I can't seem to get a CSS selector to actually target theposition: fixed
in order to override it.The closest I've gotten is by following the custom interfaces documentation (https://puckeditor.com/docs/extending-puck/custom-interfaces) however I'd rather not have to re-implement each part of the default editor interface.
Am I just missing something / is it possible to get the editor to adhere to constraints from the wrapping container like the example below;
Thanks!
The text was updated successfully, but these errors were encountered: