amplify-hosting VS wp-graphql

Amplify Web Hosting

Head to AWS Amplify Hosting and click on the Host your web app button. You’ll be redirected to this page.

Just looked up the feature request and looks like they still don’t support it https://github.com/aws-amplify/amplify-hosting/issues/56

As of today, Amplify doesn't support Next.JS@12 fully and because of that, it'd be better and safer to downgrade to version 11 (of course we'd miss some of the awesome features from v12 but that's fine). So I'm making it "next": "11.1.4" in the package.json. Since we're downgrading it to v11, we need to downgrade usage of webpack from 5 to 4 and for doing that we need to add webpack5: false to our next.config.js file. I also add SVG support to that file for the future and it looks like this:

The Bearcam Companion application was pretty much ready to go after my last post on Lambdas. The final step (at least for a minimum viable product) was to publish the site. Not surprisingly, I chose to use AWS Amplify Hosting.

Hosting a simple static website is one of those things one would expect to be easier on AWS (it is by far from the only one). AWS seem to have recognised this and now offer the AWS Amplify Hosting service. I have not used this service myself but like other services branded under the Amplify umbrella it will come with the usual trade-off: a quicker setup for less flexibility.

I've run into a similar issue where the company wanted to bring on their Wordpress blog content on one site into their main site. NextJS combined with WPGraphQL did the trick. If you are going the static site generation route the main drawback is having to rebuild and deploy every time a new blog post is made. Could host it on AWS Amplify but I use Netlify and Cloudflare Pages. Take a look through their pricing models and pick whatever feels comfortable for you (still assuming a static site generated setup). In my opinion, NextJS is good enough. If it gets the job done in a reasonable amount of time, pick it. You mention having experience with Vue so maybe Nuxt is a better option?

Amplify Web Hosting

In short: you don't. Or you enlist the help of AWS Support (which you will have to pay for). The Amplify web console doesn't share detailed build logs, so you'll have to fix your problems by trial and error.

If you're referring to Amazon's static site hosting service, Amplify, which does this kind of proxying, you'd be right that it is a PIA, however, it is also the only static site hosting service that requires you to update your routes through their console. And one of the oldest and most popular issues logged on their git repo is to have this changed.

Are you dead set on building a Nuxt + Vue application? Partial to NextJS like I am? Well good news everyone, WordPress has done a pretty decent job over the past couple of years building out the WordPress API and enabling developers to leverage WordPress as a Headless CMS. Pair that with the amazing WPGraphQL Pluginand you’re cooking with JavaScript. You get all the benefits of really solid backend CMS that end users are familiar with, and can grasp with a 1 hour CMS training, distributed using your favorite flavor of JavaScript.

I am using Headless Wordpress with https://www.wpgraphql.com/ for API hosted on SiteGround and Nextjs for frontend.

- WPGraphQL

Look at other popular plugins to see what they do, and how that's different from what you did. For example browse a bit through https://github.com/wp-graphql/wp-graphql

How does this compare to WPGraphQL https://www.wpgraphql.com that's been around for quite some time (https://github.com/wp-graphql/wp-graphql)

Did you find shortcomings with that plugin?

if you want to save yourself the headache of migrating all your content from WP you can keep WP and install something like this to get GraphQL data from your WP server. Then use Next.js with React Query or Apollo and rebuild your blog frontend only.

For a CMS-oriented solution (tbf, WP dashboard is pretty nice and familiar to many - plus rich plugin ecosystem, wide SEO and marketing support), try to push for Advanced Custom Fields as it is widely supported. For example, it can integrate with WPGraphQL (which could help unlock some modern frontend options).

WPGraphQL is pretty decent if you need an API for the content. WP's built-in "ajax" API has its purpose too, but I wouldn't use it as the main content API when the GraphQL option is readily available.

I've run into a similar issue where the company wanted to bring on their Wordpress blog content on one site into their main site. NextJS combined with WPGraphQL did the trick. If you are going the static site generation route the main drawback is having to rebuild and deploy every time a new blog post is made. Could host it on AWS Amplify but I use Netlify and Cloudflare Pages. Take a look through their pricing models and pick whatever feels comfortable for you (still assuming a static site generated setup). In my opinion, NextJS is good enough. If it gets the job done in a reasonable amount of time, pick it. You mention having experience with Vue so maybe Nuxt is a better option?