-
Notifications
You must be signed in to change notification settings - Fork 2
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
I can Click on block in blocks nav tree and edit it in sidebar , save and see it changed in preview #14
Comments
as discussed. take victors navtree code and include it in this addon to just get a very basic list of blocks. Later we can take this out and use the proper navtree that will be included in 18. |
@MAX-786 this is his latest version. We probably can't wait to have this merged but we can just copy some of the code and make a simpler version for now that list lists out the blocks |
@JeffersonBledsoe it seems like the blocks nav branch is almost finished. Would there be any problem using it as is and therefore using the latest 18 and 6.1 backend? |
Descision was to wait until the navtree is released into a 18 alpha and instead do the click on preview to select earlier #24 |
Not something that needs to be solved here but seems that blocks navtree doesn't really have a good logical place in the quanta design. Tabs are gone and instead you get a settings button and if you close the sidebar then you would have to use the quanta toolbar to open it again One obvious option is another icon in the toolbar. But its going to take up space for something not that often used. Instead I think it should be both in the Page settings and in the block settings
|
@MAX-786 the order tab is now deployed but I can't see to click on a block and edit it. I'm not sure if thats something you've broken or thats just not meant to be how it works? |
In volto, clicking on blocks in Order tab will select the block on screen, so I am aiming for that for the iframe. I'll create a seperate PR for that. |
No description provided.
The text was updated successfully, but these errors were encountered: