schemaorg VS Next.js

export class AboutComponent { private renderer = inject(Renderer2) private rendererFactory = inject(RendererFactory2) ngOnInit(): void { this.renderer = this.rendererFactory.createRenderer(null, null); this.addStructuredData(); } addStructuredData() { const script = this.renderer.createElement('script'); script.type = 'application/ld+json'; script.text = ` { "@context": "http://schema.org", "@type": "Organization", "name": "Your Angular App", "url": "https://your-angular-app.com", "logo": "https://your-angular-app.com/logo.png", "description": "Learn more about us at Your Angular App." }`; this.renderer.appendChild(document.head, script); } }

{` { "@context": "https://schema.org", "@type": "Article", "headline": "${post.title}", "image": "${post.image}", "author": "${post.author}", "publisher": { "@type": "Organization", "name": "My Blog", "logo": { "@type": "ImageObject", "url": "https://my-site.com/logo.png" } }, "datePublished": "${post.datePublished}" } `} script>

jsonresume-component is a web component that generates your resume with microdata following the Schema.org vocabulary set. It's custom element is and it fetches a resume.json file following the JSON Resume schema to create your resume. HTML is created from using the jsonresume-theme-microdata theme, creating a resume documented with microdata following the Schema.org vocabulary set.

type="application/ld+json"> { "@context": "https://schema.org/", "@type": "Recipe", "name": "Chocolate Chip Cookies", "image": "https://example.com/chocolate-chip-cookies.jpg", "description": "A classic recipe for delicious chocolate chip cookies.", // ... more recipe details ... }

Schema.org is a collaborative, community activity with a mission to create, maintain, and promote schemas for structured data on the Internet, on web pages, in email messages, and beyond. Schema.org website

itemscope itemtype="https://schema.org/Person"> itemprop="name">Scott Nath Work History itemprop="alumniOf" itemscope itemtype="https://schema.org/Organization"> itemprop="name">Company ABC itemprop="description">...company description... itemprop="employee" itemscope itemtype="https://schema.org/EmployeeRole"> itemprop="roleName">Software developer itemprop="description">...details about role... itemprop="alumniOf" itemscope itemtype="https://schema.org/Organization"> itemprop="name">Company Meow itemprop="employee" itemscope itemtype="https://schema.org/EmployeeRole"> itemprop="roleName">Sitting Volunteer History itemprop="alumniOf" itemscope itemtype="https://schema.org/Organization"> itemprop="name">Company 501c3 itemprop="employee" itemscope itemtype="https://schema.org/EmployeeRole"> itemprop="roleName">Software developer for free itemprop="description">...details about role...

I've been re-writing the HTML of my site and added structured data, in the form of microdata attributes, following the Schema.org vocabulary set. Structured data can be understood by search engines and other machines, giving your content structure and context.

Implementing Structured Data Markup annotation system, which can provide additional context about the content to search engines. Structured data markup such as Schema.org can be used to aid search engines to understand the content relevance and significance. This approach can help improve search results by improved ranking and visibility of the content.

export default async function Page({ params }) { const product = await getProduct(params.id); const jsonLd = { "@context": "https://schema.org", "@type": "Product", name: product.name, image: product.image, description: product.description, }; return ( {/* Add JSON-LD to your page */} {/* ... */} section> ); }

Repository: Next.js

Next.js: npx create-next-app@latest

Remix is a very cool React-based framework that makes the final jump back from the browser to the server. After starting with SPAs that fully ran in the browser, Next.js got the idea of rendering React components in the server, reducing the initial load time and improving crawlability. Remix takes this a step further: while Next.js cannot render dynamic content on the server, Remix can. As a user, this means even faster loadings times for any kind of dynamic content, and as a developer, you don't need to think about server-side vs client-side components. You just write React code, and it works.

Here is the tricky situation and that's why CRA is in a semi-dead state, it has not been deprecated but isn't receiving any updates not even security updates, along with that the new React.dev documentation doesn't mention CRA but suggests using React meta-frameworks like Next and Remix for new projects. You can read more about React's reasoning for it in this github issue discussion.

Probably the most known example https://github.com/vercel/next.js/discussions/19065

It was not an issue if you host in Vercel, as they provide the image optimization as a premium feature.

Implementing the requested feature would make the framework much better when self-hosted elsewhere. But there is neglection to resolve the issue. This is just one case.

This Reactjs version also includes React Server Components, so you can easily render components on the server. If you’re familiar with Next.js, whose components are server components by default, this is the same idea. Server components have advantages such as faster page load time, better SEO optimization, and overall better performance.

Next.js - for creating the application’s user interface and backend.

On fresh install (ts version), every page inside /src/app will throw module not found errors on imports. This is probably because in tsconfig.json, moduleResoultion is set to bundler. More here - https://github.com/vercel/next.js/discussions/41189

Next.js is a powerful React framework, that is widely used for building server-side rendered (SSR) or static web applications. Dockerizing a Next.js application can streamline the deployment process and ensure consistency between development, testing, and production environments