Hello Chris,

Headless CMS is overkill if you have only one calculator or such content to be embedded.

If you want to exclude the header and footer and show just the calculator via iframe, try using a separate page template. [https://stackoverflow.com/a/51504775]

Using this approach, you can control the calculator’s design and embed it anywhere via iframe.

Also, make sure that the style and script tags are loading the resources. You can add the calculator site as a trusted oembed provider using this hook wp_oembed_add_provider.

iframe isn’t that good looking. Also I would prefer to disable the WordPress Frontend to make the content only visible at the destination URL.

Is headless cms the way to go or am I wrong?

Best Regards

How do I debug it?

just wanted to tell you about my project doing the same thing with Vue.js/Nuxt.js. It’s a complete dockerized dev environment. Maybe you’ve got some feedback?
https://github.com/northosts/wuxt

Hey, Michael!

Jo’s example in the posts.js file define’s for NextJS what the initial properties should be. NextJS is responsible for calling that method on the Component object. You can see one example inside the library here: https://github.com/zeit/next.js/blob/b88addfcd5d3d305664ff95a709b4a4df7e0cbcf/packages/next-server/lib/utils.js#L38), where the getIntialProps method is called on the component.

Awesome tutorial! Very helpful for me.
I have a question regarding the static method getInitialProps(). I don’t understand where this method is being called?

Thanks for finding that typo!

Things like GraphQL or Firebase or anything we can do to make our request faster or more dynamic would certainly help speed up the front-end of an app like this. I haven’t thought about it for this demo specifically, but that is certainly something worth writing about.

Small type in code – `hOur Posts Page!`. Extra `h` within h1 tag.