Planned to ask for a refund today, only to find out I was one day too late.
Apparently the Universe wants me to have more patience, to wait until the bugs are over.

When I saw this deal, it was love at first sight.
Moving away from Divi and Elementor, going for more flexibility in design and speed.

Since this is my first experience with FSE, it was quite a steep learning curve.
Greenshift UI is not always as expected or missing. (especially width setting precision)

In my case, For example: I want to have 3 Header rows.
Top row = Logo + language switcher + login/register
Row 2 = Desktop menu (site links) + Dashboard menu (visible after login)
Row 3 = Mobile menu, IDEM
Row 1 "disappears", and 2 and 3 must be sticky to TOP upon scrolling.

Groenshift has an option to add a logo for mobile.
But in bower this results in having 2 logo's on top of each other.
There are no mobile logo height and Length settings.
I found my way using Ai to add css code manually...

Despite enough free space between the columns, despite no-wrap, I got "wrap" issues.
Only Row 2 and 3 sticky to top? Either the entire Header, or none.

It also took me a long time to find out that some of my (ai) generated css code
placed under child-theme/assets/css was conflicting (my bad) but still issues not resolved.

So I decided to ask Gemini what are the known issues with Greenshift?
Learning Greenshift is known for being quite prone to errors (bugs) due to its massive number of features and animations.

The most well-known issues, functional quirks, and bugs in Greenshift are:

## 1. Issues with "Template Parts" and Sticky Headers
This is exactly the problem I am currently facing.

The problem: Greenshift functions (such as position: sticky) break as soon as a block is placed inside a WordPress Template Part or Synced Pattern (reusable block).

The cause: WordPress automatically wraps patterns inside an invisible extra code container (<header> or <div>). Greenshift makes the inner element sticky, causing it to "stick" inside its own invisible container instead of to the entire page.

## 2. CSS Synchronization & "No Styles on Frontend"
This is one of the most reported errors in the community.

The problem: You adjust colors, fonts, or layouts in the editor. It looks perfect in the backend, but as soon as you publish the page, all styling disappears on the live website (the frontend).

The cause: By default, Greenshift stores CSS styles in the database via special fields. If your page becomes too large, or if your web hosting has strict limits on database fields, the database truncates the CSS code.

* The official workaround for this is to enable the "Save styles inline" option in Greenshift settings.

## 3. Conflicts with Multilingual Plugins (WPML)
If you are building a multilingual website, Greenshift has known synchronization issues.

* The problem: When you translate a page using WPML, the CSS structure between the languages ​​often becomes corrupted. Modifying a Dutch page, for example, can inexplicably cause the layout of the English translation to break completely, or cause CSS classes to become incorrect.

## 4. Updates that break designs ("Update Regression")

* The problem: Because Greenshift uses an extreme amount of JavaScript and animation libraries (such as GSAP), plugin updates regularly introduce new layout issues (regressions). After an update, images sometimes lose their formatting, Query Loops stop working, or the editor responds slowly.

## 5. Behavior when copying and duplicating Patterns

* The problem: If you place a reusable pattern (Pattern) on a page, duplicate it, and then "ungroup" it, Greenshift keeps getting confused about which CSS styles belong to which element. This causes changes in one block to have an unwanted effect on the other block.

also, It will come in handy to switch easily between Desktop, iPad and Mobile, and when changing these settings remain device specific. and be able to switch back. In some settings where you can be specific, refreshing the page is the only way to go back to "normal" editing.

And when set visibility setting "hide on desktop", (for my mobile menu row)
adding, css code to allow view on desktop for admin, so you can continue editing as admin, without the row being seen in live browser. (ai created this code form me)

All-in-all, Greenshift is a powerful Page Builder for the WordPress Gutenberg editor with a lot of potential. A lot of work has been done, but there are still too many "bugs" for the most easy settings. (especially #2 It looks perfect in the backend, but as soon as you publish the page, all styling disappears on the live website ).

For now, because I lost weeks of my time, trying to figure everything out... , I better wait a while before trying again, hooping (expecting) that the known issues mentioned above are solved.