I wanted to restate here and add to them – because these questions are for a current, time-sensitive WordPress/Divi website project:
1. It seems Overlay is not truly WYSIWYG. Whether as component or variant, my completed Figma design (for a website) doesn’t translate properly at all. Whether in Overlay preview or rendered test HTML output (with the CSS in <style> tag inside HTML head), many boxes seem shifted many pixels to the right. This despite the attribute not being set in Figma. Also, none of the embedded images display, with placeholders in their place. This contradicts the AppSumo screenshot showing a project that displays the image. I thought the styles would be proper with elements centered to web design best practices. Maybe I am doing something wrong. Is there a reason this is happening, and if so, how do I prevent it?
2. Even if #1 keeps happening, how do I visually edit the HTML inside the Overlay editor before I actually copy the code to an HTML file? The way Overlay is designed has me under the impression I could change the rendered HTML and CSS by dragging elements like in Figma. This is not the case. I find no ability to drag and drop.
3. SCSS for fonts and colors appears not to work properly in a straight copy. Some colors display, others don’t. Fonts don’t work at all; they default to browser default (Times New Roman or the likes). How do we make them work?
4. I expect that settings, such as tagging fonts and font colors as class names, can be changed after I am first asked about them. This also has not been the case. I would like to change this on the fly after creating an HTML output so I can more easily diagnose any future issues that may arise.
These issues are VITAL. I feel they hold us back from completing this project ahead of time. I am hopeful Overlay can serve its promoted purpose.
@Côme_Overlay, I’d much appreciate it if you could answer these questions. Pretty sure I’m not the only one.
Q: Hi I try to reach you from chat inside the web but after 10 days, no response.
So here I am.
First, You have nice app! Congrats.
But, I have questions regarding variant (not component) export.
When I try to export variant. it's always show 'Could not validate your component'. And I use your sample file. not my file or someone else. It's yours.
So any explanation to export variant will be great. I know you're not fulltime on this plugin. but when you release product that user need to pay before use it, user expect a support from you.
Q: Product needs work, needs the ability to export animations and effects.
Their support is lack luster. I am refunding.
Share Overlay
Q: Hello, is it possible to export to Tailwind ?
Has it been implemented since ?
Share Overlay
Q: Is this tool still being supported?
I haven’t seen the devs comment in a while.
Share Overlay
Verified purchaser
I think it is abandoned. It's a shame it is still on sale.
Hey there jamoooret and stephenzhao, this is Leo, from AppSumo!
I see you are having an issue with Overlay. Thank you for bringing that to our attention, we’re already looking into it! 🙂
If this isn’t resolved soon, please kindly reach out to support@appsumo.com.
(Please note that during this Black Friday period our support may take slightly longer than usual to respond. We appreciate your...
Was this ever resolved?
Is the product still supported?
Kind regards,
J
Q: Hey @Côme_Overlay, I asked these in support.
I wanted to restate here and add to them – because these questions are for a current, time-sensitive WordPress/Divi website project:
1. It seems Overlay is not truly WYSIWYG. Whether as component or variant, my completed Figma design (for a website) doesn’t translate properly at all. Whether in Overlay preview or rendered test HTML output (with the CSS in <style> tag inside HTML head), many boxes seem shifted many pixels to the right. This despite the attribute not being set in Figma. Also, none of the embedded images display, with placeholders in their place. This contradicts the AppSumo screenshot showing a project that displays the image. I thought the styles would be proper with elements centered to web design best practices. Maybe I am doing something wrong. Is there a reason this is happening, and if so, how do I prevent it?
2. Even if #1 keeps happening, how do I visually edit the HTML inside the Overlay editor before I actually copy the code to an HTML file? The way Overlay is designed has me under the impression I could change the rendered HTML and CSS by dragging elements like in Figma. This is not the case. I find no ability to drag and drop.
3. SCSS for fonts and colors appears not to work properly in a straight copy. Some colors display, others don’t. Fonts don’t work at all; they default to browser default (Times New Roman or the likes). How do we make them work?
4. I expect that settings, such as tagging fonts and font colors as class names, can be changed after I am first asked about them. This also has not been the case. I would like to change this on the fly after creating an HTML output so I can more easily diagnose any future issues that may arise.
These issues are VITAL. I feel they hold us back from completing this project ahead of time. I am hopeful Overlay can serve its promoted purpose.
@Côme_Overlay, I’d much appreciate it if you could answer these questions. Pretty sure I’m not the only one.
Thanks!
Share Overlay
Q: Hi I try to reach you from chat inside the web but after 10 days, no response.
So here I am.
First, You have nice app! Congrats.
But, I have questions regarding variant (not component) export.
When I try to export variant. it's always show 'Could not validate your component'. And I use your sample file. not my file or someone else. It's yours.
So any explanation to export variant will be great. I know you're not fulltime on this plugin. but when you release product that user need to pay before use it, user expect a support from you.
thanks
Share Overlay