Hi @Pixelart and @Webdeersign,
The Wordpress Stack from Yabdab pulled content from the Wordpress site using the WP Rest API. My stack embeds the actual content in a frame that seamlessly and responsively adjusts itself to the content.
That’s why, on the product page, I wrote the recommendations on how to use a WP theme, turn off headers and footers and menus, as that should be handled by RW. As result, the WP Embed stack will display the contents of the WP site exactly as if you navigated directly to. You can try that on the demo site.
I decided on this new approach instead of writing php loops, style sheets etc… for getting content from the wordpress site into RW, as there are already great themes for WP out there that are highly customizable and can easily reflect the look and feel of the content developed under RW. With this approach, I also felt that there would be little risk of obsolescence, since, if you can display in Wordpress you can display with the Wordpress Embed Stack.
Another aspect of my approach to display WP content like this, was to keep WP mostly as a CMS/Blog site and keep it simple, with a minimal number of plug-ins and minimal complexity, and use RW as the actual website/page development platform, including the great tools that the RW community has as it’s disposal.
There is one aspect in my approach that requires some attention on the part of the web-developers, which are links. All links (in the WP site only, not RW) referring to resources outside of the Wordpress site must include `target="_parent", otherwise those links will also open inside the WP stack. However, all links referring to things in the WP site, don’t need any changes.
Here is an example: <a href="https://www.axyn.com/site/products" target="_parent">Visit Axyn's Product Page</a>
I hope that this helps clarify how the stack works.
Cheers,
Ricardo