-
Posts
-
Ok, here is an ‘oops’ moment that I thought would work but now has screwed me.
On one of my sections in Cornerstone I added “Display: none;” thinking that I could hide the particular section temporarily since the clint does not have all the content ready yet. I figured that this way I could do what I can accomplish now and then finish this later without having to create the section from scratch.
Now I find that this hides the ‘hidden’ section in Cornerstone but the section renders normally when the browser renders the live page.
The section in question is on this page (http://yuensmartialarts.com/yuens-martial-arts/) and the section that I want hidden is the Instructor section at the bottom.
Is there a way to undo my “Display:none;” so I can still see it in Cornerstone and ultimately accomplish hiding a section only when it renders the site. Perhaps this may be something that others could make use of as well.
Another observation and possibly a ‘feature’ would be a way to see in Cornerstone all sections of a site in the Cornerstone editor (desktop/mobile/etc) with a color border around them or something rather than only seeing the current rendering based on the device targeted? I find that I forget what sections have alternative version because I am only able to view live the rendering that I am currently on. Sometimes in development you are jumping back adn forth and seeing all sections targeting any and all devices would make Cornerstone easier to use.
If that last idea is confusing I can provide a mockup of what I am thinking.
Thanks
Hello There,
Thanks for posting in.
To undo the display:none; please go to Layout Tab, then click the specific section. Click the Inspect element button on the right of the name of the section. It will you to the section properties and now you can delete those inline style.We have a property/option called Hide Based on Screen Width that is available for Section and Rows. When you inspect element section or rows, you can click those different type of screen width where you want to hide those specific content of the section or rows.
Regarding the feature, in Cornerstone, we have an option to display the content per screen width. You can see the phone icon beside the Save button. Clicking those Icon will give you access to different screen options and it will display the content you set per screen. Displaying all content at once will defeat this purpose of showing it per screen. If this doesn’t clarify please provide screenshot of what you want.
Hope this helps.
Hi and thanks for pointing that section inspector out for me; huge sigh of relief!
With regards to the feature issue, the response you provided is exactly the reason there needs to be some way to see all Cornerstone sections at once regardless of browser width. If there were an additional option for editing all sections at once with some sort of color coded icon representing browser width for easy reference, then developers could work on all sections at once without having to bounce back and forth between different viewing widths. Once competed the width options can be used as you currently have them.
I generally find myself loading a browser with tabs for all widths to reference final rendering while I’m developing. This is hugely inefficient as I go back and forth a ton. Changing views inside of Cornerstone while editing is frustrating too since much of Cornerstone does not render accurately anyway and it’s easy to miss updating a section because they are hidden if developing for different widths. There is also no easy way to visually compare one section’s content from another.
Just an idea but while the realtime preview is helpful it is not a substitute for a true browser. This is true across all visual editors and not a criticism of Cornerstone. Given that, why not provide an additional editing viewing pane that allows editors to view and edit all widths simultaneously and then provide the existing ability to view based on browser width?
Regardless, thanks for the help with the first issue. I was panicking.
You’re most welcome! Thanks for the suggestion, We will forward it to our dev team a feature request. I can’t promise implementation or a timeline at this point, however, we do listen to our users and we’re always trying to improve. When we see something beneficial we do our best to make it happen. We’re actually working on a number of things so if this does get added to the pipeline, we’ll be sure to announce it when it’s ready. Thanks for understanding! Have a great day!
