What is your work flow to go from design mockup to full website?

[Pinegrow_User]

@Terry44

What I did was create a div in the body of the page and using the eye in the code list on the right, for me it is on the right I turn it on and off. You can also set transparency on the img or div via css too if you wanted. Problem with setting it to the Body tag is that if you wanted to temporarily hide the image you can’t because it would hide the whole page.

@Terry44, it was just a basic example ideal for your mockup image workflow desires. But yes using a DIV allows for more manipulation and features via CSS and the current UI.

If it was to be an actual feature as previously hinted at …

@Pinegrow_User

It may be nice to have it as a feature via the UI or something similar on another level under the page. Have it so the user can chose and set a mockup / design image, the ability to toggle it on and off, set the opacity or overlay color, and delete the image as well.

Then it could be hidden from the user in the page tree, much like the “actions bar” etc., is on page items. Instead only accessible via it’s UI controls, and not directly by the user like a typical page item. I think this type of feature is also something that could help designer types better visualize as they set out to work with Pinegrow and use LIB , PROP , CSS , etc. Then as they add LIB items and change CSS properties they would begin to understand visually how those features work (by visual trial and error with their designs), in Pinegrow to accomplish their design and see visually the outcomes of those manipulations in comparison to their designs. After a while they would be less reliant on the underlying mockups and more in tune with the features and what needs are required.

Could be useful for some peeps. [ Feature Request - consideration @matjaz ]