You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I understand Gatsby is a way to make a WordPress site static....
However, this doesn't make things easier for a bootstrap developer to design unless he know React....
So, My question is....
Isn't it much easier to "Just" make one custom meta field call HTML, and do a site scrap to custom meta field on publish.
This will store static content of the page into an custom meta field.
Then load the static content into a REACT headless WordPress BLANK theme.
This will also allow the user to add whatever plugin s/he wants, because the resulted output is static html.
Would that work better?
The text was updated successfully, but these errors were encountered:
Hi @samjco There is more to it than using static HTML. There are moving parts that requires user interaction and events in the whole cart and checkout flow.
So I understand Gatsby is a way to make a WordPress site static....
However, this doesn't make things easier for a bootstrap developer to design unless he know React....
So, My question is....
Isn't it much easier to "Just" make one custom meta field call HTML, and do a site scrap to custom meta field on publish.
This will store static content of the page into an custom meta field.
Then load the static content into a REACT headless WordPress BLANK theme.
This will also allow the user to add whatever plugin s/he wants, because the resulted output is static html.
Would that work better?
The text was updated successfully, but these errors were encountered: