[Feature]: SEO

[thombruce]

Feature request

See #119 for work so far. This has been rolled back due to an unidentified issue.

These six modules are included in NuxtJS SEO

1. https://nuxtseo.com/docs/robots/getting-started/introduction
2. https://nuxtseo.com/docs/sitemap/getting-started/introduction
3. https://nuxtseo.com/docs/schema-org/getting-started/introduction
4. https://nuxtseo.com/docs/seo-utils/getting-started/introduction
5. https://nuxtseo.com/docs/og-image/getting-started/introduction
6. https://nuxtseo.com/docs/link-checker/getting-started/introduction

There are additional modules at a pro tier.

We want to install these individually in order to configure them properly and... hopefully to root out which one is giving us grief. The previous issue suggests the blame may lie with og-image but we don't know this to be the case absolutely.

Code of Conduct

• I agree to follow this project's Code of Conduct

[thombruce]

I am pushing a new dynamic branch on thombruce.com with the rollbacks in place to see if removing SEO has allowed for Vercel to build and run the application properly in "dynamic mode".

If I'm still seeing the same error, I'll report it here. We'll have to dig deeper to try and solve it...

[thombruce]

No, now we have a new error:

SyntaxError: Named export 'createJiti' not found. The requested module 'jiti' is a CommonJS module, which may not support all module.exports as named exports.

This is unexpected. My changes have nothing to do with a module called Jiti. Some Nuxt module has this installed...

We are out of date, aren't we? What version of Nuxt are we running...?

We're a few minor versions of Nuxt out of date, but not many. Could be worth bumping dependencies to see if that helps.

[thombruce]

Upgrading Nuxt and other dependencies, along with deleting the yarn.lock cache and rebuilding from scratch has gotten a dynamic version of thombruce.com to deploy! Hurray! 🎉

...none of the Nuxt Content content is present though. It's all still present when running yarn run dev. Very strange...

Nuxt Content needs some changes to its configuration to run dynamically in production, maybe? Yeah, that would make sense.

[thombruce]

What's interesting... the content is showing up in my search utility. It's there, the pages just aren't being rendered. This is resolvable. Maybe not tonight, but it is resolvable.

There's nothing in the Nuxt Content docs pointing me at a solution... Maybe I need to manually configure prerendering for the pages.

This is becoming a real pain in the ass, mind you, and I am very tempted to abandon the "dynamic" idea and revert to static pages. Those were working. The only thing motivating the switch to dynamic was og-image, and that may be broken anyway.

Something to think about. I will sleep on that.

[thombruce]

I am also tempted to begin a new Nuxt project from scratch that does not use TNT, but which does use...

1. Nuxt Content
2. Nuxt SEO

If we could get that to work, we could compare it to our TNT project and try to figure out what the hell is going wrong.

[thombruce]

Supplemental: I'm also more than a little tempted to just start TNT over from scratch. It's a good project but there's a lot of... "we went in the wrong direction here, here and here" that we could address. We'd love to make it simpler!

Is a TNT2 on the horizon?