Remove unused layouts and their CSS.

[XhmikosR]

• announcements.hbs
• in-the-news.hbs

I left the blogAnnounce collection as is, although it probably is redundant too, so must be its feed

[XhmikosR]

Actually now that I see site.json it seems the feed is also unused. Let me know how to proceed.

nodejs.org/locale/en/site.json

Lines 19 to 32 in ceaa1c0

	"feeds": [
	{
	"link": "feed/blog.xml",
	"text": "Node.js Blog"
	},
	{
	"link": "feed/releases.xml",
	"text": "Node.js Blog: Releases"
	},
	{
	"link": "feed/vulnerability.xml",
	"text": "Node.js Blog: Vulnerability Reports"
	}
	],

[XhmikosR]

@Trott should I also remove completely announcements?

[Trott]

@Trott should I also remove completely announcements?

I'm not sure. I don't know the ramifications. We can ping more widely for review or I can be educated.

[XhmikosR]

Let's ask more people. I added the complete removal of announcements. Not sure if we should add any redirections or not.

[Trott]

@nodejs/website

[XhmikosR]

@nodejs/build should we redirect the announcements index file or their feed? Note that this actually only removes the /announcements/index.html/ file and announcements.xml

Otherwise, I will split this patch so that we can merge the first one which is safe.

[XhmikosR]

Since I'm not getting any reviews, I dropped the second patch from this PR.

Now the patch just removes unused layouts and their CSS.

[rvagg]

This seems fine to me.
I'm a little shocked that we have nobody showing up to review though? what happened to our website team and where is our shiny new website that we've had a whole team pouring over?

[alexandrtovmach]

I think we haven't somebody who can give an answer about removed layouts, so let's merge PR and take a look on any issues that can be produced

[XhmikosR]

This shouldn't affect anything. I moved the other patch to separate PRs.

[nschonni]

Not sure about removing the content (now in other PR), but these do look unreferenced anyway so 👍

[bnb]

I'm a little shocked that we have nobody showing up to review though? what happened to our website team and where is our shiny new website that we've had a whole team pouring over?

@rvagg you can find that work in nodejs/nodejs.dev.

[rvagg]

@bnb thanks, so when do we get to replace nodejs.org?

[bnb]

That's a great question. I'm not involved to the point to be able to assert an answer to it. Perhaps @amiller-gh could give some insight on, though I don't necessarily think this PR is the correct venue for that.