All language subtitles for 002 Analyzing the Need for _head_ Metadata_Downloadly.ir_en

Now for this course section,

I will actually use that little events project we worked on.

So attached you find the latest snapshot of this.

If you download it, you need to run npm install.

And then once you did that,

bring up the development server with npm run dev.

This will give you this application year

and that's what we worked on over the last course sections.

Now the first aspect into which I want to dive here

is the metadata that had data we could add to every page

because if we inspect our page here

and we have a look not at the body but at the head section,

which carries important metadata and information

for the browser and for search engines,

then we see that it's pretty empty.

We got no description here.

We have no title for this page.

We've got a bunch of imports,

which are added automatically

by next JS for all our styles and so on

but we don't have that metadata,

that extra data which we typically want to provide

on our page.

And, of course, that is something

which we definitely do want to have

on the application we're building

because that enhances the user experience

to a certain extent,

depending on what we set there.

For example,

showing a title which would show up in a tab up there

but it's also crucial for search engines

because search engine crawlers

like the Google crawler will have a look at the title

and the description set in that metadata.

And therefore, it is something we want to set.

And thankfully, next JS makes setting such head data easy.