fastify / website-metalsmith

This project is used to build the website for fastify web framework and publish it online.

fastify-website

WARNING:
This repository was the previous home of the Fastify website till June 2023.
The new home is now fastify/website-next

This project is used to build the website for fastify web framework and publish it online.

Requirements

• Node 12+
• Install dependencies with npm install

Build

To trigger the build of the website you just need to run:

npm run build

This will execute all the steps necessary to create a build (static website).

If you are developing you can run:

npm start

This will trigger the build and also start a live server that will allow you to visualize the changes you are performing on the website.

(note that every time you make a change to the assets that constitutes the content of the website you will need to launch npm run build:website to trigger a rebuild)

Build steps

In case you are interested in knowing more about how the build process works, here are the main steps that are performed during its execution:

1. Cleanup: removes temporary resources that might have created from a previous build
2. Temp folders creation: Creates the needed folders for the build process
3. Get releases: uses the GitHub APIs to download the latest releases of Fastify so that the documentation pages can be regenerated dynamically.
4. Process releases: processes the releases creating all the necessary dynamic files that are derivate from the original fastify releases (mostly used to generate and process documentation pages)
5. Website generation: uses Metalsmith to compile a static version of the website.

Checkout the Package scripts to understand which files trigger these actions in case you want to have a look at the code for any of the steps described above.

Publishing as GitHub pages

The website is published automatically Circle CI using GitHub pages (branch gh-pages).

Every time there's a change on master, if the build was created successfully, then it is automatically published on GitHub Pages.

In order for this to work, Circle CI will need to be configured correctly providing all the necessary environment variables:

• DOMAIN: the custom domain to be used in GitHub pages (www.fastify.io)
• GH_EMAIL: the email of the GitHub user authorized in CircleCi to push to the gh-pages branch
• GH_NAME: the username of the GitHub user authorized in CircleCi to push to the gh-pages branch
• GH_TOKEN: (optional) a GitHub personal access token for the user specified in GH_NAME. If this is present the API calls to GitHub will be authenticated.
• CLOUDFLARE_EMAIL: the email of the CloudFlare account
• CLOUDFLARE_AUTH_KEY: the authorization key to perform API calls on CLoudFlare APIs
• CLOUDFLARE_ZONE: the ID of the CloudFlare Zone associated to the current domain

Contributing

Everyone is very welcome to contribute to this project. You can contribute just by submitting bugs or suggesting improvements by opening an issue or by sending a pull request.

License

Licensed under MIT License. © OpenJS Foundation and The Fastify team.

website-metalsmith's Issues

Request to use favicon.ico in a plugin

Hi all,
in a plugin I'm writing fastify-favicon I'd like (if possible) to use standard fastify favicon.
Or maybe I could load it from Fastify directly but currently it's not in that repository.
What do you think ?

Thanks a lot,
Sandro

Configure CI

• 1. Enable trigger on website repository commits
• 2. Enable trigger on fastify repository commits
• 3. Prepare fastify AWS S3 bucket for deploy
• 4. Configure CI environment variables (AWS credentials + Bucket Name)
• 5. Map custom domain to S3 bucket website (Depends on #7)

Deprecated beforeHandler in home page second example

Deprecated beforeHandler in home page second example. Must use preHandler.

Your Environment

• node version: none
• fastify version: >=2.10.0
• os: Linux Mint
• any other relevant information

/docs should point to the latest released version of the doc

As titled.

create anchors for the headings in the docs

like github!

set up the domain

Can you give me the IP addresses for the A level domain and/or for the CNAME?

Create a new page on fastify users

As titled!

Register/Reserve Domain name

We should have a proper domain name for exposing the website to the world. I see that fastify.com is taken. In case none of you is the owner of that domain we can maybe try to get fastify.js.org through dns.js.org.

Update team section

The website should reflect the new README in the main repo.

This requires changing the src/website/data/team.yml data file and the src/website/layouts/home.html template.

Ideally, we should respect the division between lead maintainers and contributors as in the main repo.

where can I submit my plugin?

Hi,

I just released another fastify plugin fastify-blipp.

I know my plugin is pretty dumb, but still think it can be useful :) Wanted to submit it to be present in the plugins list here:
https://www.fastify.io/ecosystem/

However I see that ecosystem.yml reference is broken:
https://github.com/fastify/fastify/docs/_data/ecosystem.yml

And I was not able to find the source of the plugins list in the website repository.

What is the current way to submit plugin PR?

Regards,

Language selection / i18n

We should a dropdown for i18n so that users can view the chinese docs and any other languages

Mention TypeScript support our front page

We work hard on supporting TypeScript, we should reflect this on the front page of the site so devs know that we are a Node.js API Framework with TypeScript support.

Create proper images and metadata for social sharing

As per title.

Currently social sharing on Facebook and Twitter generates non ideal previews.

Mia-Platform logo disappears

I don't know why but not all organizations listed here are not showed in the website.

Rename repository to website

I would call this repository only website (as opposed to fastify-website).

What do you think?

At the moment I don't think I have permissions to do that.

Integrate cookieconsent to allow the integration with Google Analytics

https://cookieconsent.insites.com/

References #11

Broken links

Some pages link to broken links.

Running wget --spider -o wget.log -e robots=off --wait 1 -r -p --debug 'https://www.fastify.io/', the following links are broken:

Trovati 105 collegamenti rotti.
https://www.fastify.io/docs/v0.35.x/Middlewares/'./Reply.md'
https://www.fastify.io/docs/v0.42.x/Middlewares/Plugins.md
https://www.fastify.io/docs/v1.3.x/Middlewares/Plugins.md
https://www.fastify.io/docs/v1.2.x/Factory
https://www.fastify.io/docs/latest/Middlewares/Request.md
https://www.fastify.io/docs/v0.40.x/Middlewares/Reply.md
https://www.fastify.io/docs/v1.3.x/Middlewares/Hooks.md
https://www.fastify.io/docs/v1.5.x/Factory
https://www.fastify.io/docs/v0.39.x/Middlewares/Plugins.md
https://www.fastify.io/docs/v1.6.x/Middlewares/Request.md
https://www.fastify.io/docs/v0.37.x/Middlewares/Reply.md
https://www.fastify.io/docs/v0.41.x/Factory.md
https://www.fastify.io/docs/v1.0.x/Middlewares/'./Reply.md'
https://www.fastify.io/docs/v0.41.x/Middlewares/Hooks.md
https://www.fastify.io/docs/v1.0.x/Middlewares/Plugins.md
https://www.fastify.io/docs/master/Middlewares/'./Reply.md'
https://www.fastify.io/docs/v1.4.x/Middlewares/'./Reply.md'
https://www.fastify.io/docs/v0.36.x/Middlewares/Plugins.md
https://www.fastify.io/docs/v1.3.x/Middlewares/Reply.md
https://www.fastify.io/docs/v0.42.x/Factory.md
https://www.fastify.io/docs/v0.42.x/Middlewares/Request.md
https://www.fastify.io/docs/v1.3.x/Middlewares/Request.md
https://www.fastify.io/docs/v0.39.x/Middlewares/Request.md
https://www.fastify.io/docs/v0.41.x/Middlewares/'./Reply.md'
https://www.fastify.io/docs/v0.38.x/Middlewares/Hooks.md
https://www.fastify.io/docs/v1.1.x/Factory
https://www.fastify.io/docs/v1.5.x/Middlewares/Plugins.md
https://www.fastify.io/docs/v0.43.x/Factory.md
https://www.fastify.io/docs/v0.41.x/Middlewares/Reply.md
https://www.fastify.io/docs/v0.38.x/Middlewares/'./Reply.md'
https://www.fastify.io/docs/v1.4.x/Middlewares/Hooks.md
https://www.fastify.io/docs/v1.0.x/Middlewares/Hooks.md
https://www.fastify.io/docs/v0.38.x/Middlewares/Reply.md
https://www.fastify.io/docs/v1.0.x/Middlewares/Request.md
https://www.fastify.io/docs/v0.36.x/Middlewares/Request.md
https://www.fastify.io/manifest.json
https://www.fastify.io/docs/master/Middlewares/Hooks.md
https://www.fastify.io/docs/v0.41.x/Middlewares/Plugins.md
https://www.fastify.io/docs/v0.42.x/Middlewares/Hooks.md
https://www.fastify.io/docs/v1.3.x/Middlewares/'./Reply.md'
https://www.fastify.io/docs/v1.2.x/Middlewares/Plugins.md
https://www.fastify.io/docs/v0.38.x/Middlewares/Plugins.md
https://www.fastify.io/docs/v1.4.x/Factory
https://www.fastify.io/docs/v1.4.x/Middlewares/Reply.md
https://www.fastify.io/docs/v1.0.x/Middlewares/Reply.md
https://www.fastify.io/docs/v0.39.x/Middlewares/Hooks.md
https://www.fastify.io/docs/v1.5.x/Middlewares/Request.md
https://www.fastify.io/docs/v0.40.x/Middlewares/'./Reply.md'
https://www.fastify.io/docs/v0.35.x/Middlewares/Hooks.md
https://www.fastify.io/docs/master/Middlewares/Reply.md
https://www.fastify.io/docs/v1.0.x/Factory
https://www.fastify.io/docs/v0.42.x/Middlewares/Reply.md
https://www.fastify.io/docs/v0.37.x/Middlewares/'./Reply.md'
https://www.fastify.io/docs/v0.35.x/Middlewares/Plugins.md
https://www.fastify.io/docs/v1.5.x/Middlewares/Hooks.md
https://www.fastify.io/docs/v1.1.x/Middlewares/Hooks.md
https://www.fastify.io/docs/v0.41.x/Middlewares/Request.md
https://www.fastify.io/docs/v0.39.x/Middlewares/Reply.md
https://www.fastify.io/docs/v1.2.x/Middlewares/Request.md
https://www.fastify.io/docs/v0.38.x/Middlewares/Request.md
https://www.fastify.io/docs/v0.35.x/Middlewares/Reply.md
https://www.fastify.io/docs/latest/Middlewares/Hooks.md
https://www.fastify.io/docs/v0.43.x/Middlewares/Plugins.md
https://www.fastify.io/docs/v1.2.x/Middlewares/'./Reply.md'
https://www.fastify.io/docs/v1.4.x/Middlewares/Plugins.md
https://www.fastify.io/docs/v1.3.x/Factory
https://www.fastify.io/docs/v0.43.x/Middlewares/Hooks.md
https://www.fastify.io/docs/v1.6.x/Middlewares/'./Reply.md'
https://www.fastify.io/docs/v1.5.x/Middlewares/Reply.md
https://www.fastify.io/docs/v1.1.x/Middlewares/Reply.md
https://www.fastify.io/docs/v0.36.x/Middlewares/Hooks.md
https://www.fastify.io/docs/latest/Middlewares/'./Reply.md'
https://www.fastify.io/docs/v0.35.x/Middlewares/Request.md
https://www.fastify.io/docs/v0.43.x/Middlewares/'./Reply.md'
https://www.fastify.io/docs/latest/Middlewares/Reply.md
https://www.fastify.io/docs/master/Factory.md
https://www.fastify.io/docs/v0.40.x/Middlewares/Plugins.md
https://www.fastify.io/docs/v0.43.x/Middlewares/Reply.md
https://www.fastify.io/docs/v1.1.x/Middlewares/Plugins.md
https://www.fastify.io/docs/v0.37.x/Middlewares/Plugins.md
https://www.fastify.io/docs/master/Middlewares/Plugins.md
https://www.fastify.io/docs/v1.6.x/Middlewares/Hooks.md
https://www.fastify.io/docs/v1.2.x/Middlewares/Hooks.md
https://www.fastify.io/docs/latest/Factory
https://www.fastify.io/docs/v1.6.x/Factory
https://www.fastify.io/docs/v1.4.x/Middlewares/Request.md
https://www.fastify.io/docs/v0.43.x/Middlewares/Request.md
https://www.fastify.io/docs/v0.36.x/Middlewares/'./Reply.md'
https://www.fastify.io/docs/master/Server-Methods.md
https://www.fastify.io/docs/v0.36.x/Middlewares/Reply.md
https://www.fastify.io/docs/latest/Middlewares/Plugins.md
https://www.fastify.io/docs/v1.1.x/Middlewares/'./Reply.md'
https://www.fastify.io/docs/v1.6.x/Middlewares/Plugins.md
https://www.fastify.io/docs/v0.40.x/Middlewares/Hooks.md
https://www.fastify.io/docs/v0.39.x/Middlewares/'./Reply.md'
https://www.fastify.io/docs/v1.5.x/Middlewares/'./Reply.md'
https://www.fastify.io/docs/v1.6.x/Middlewares/Reply.md
https://www.fastify.io/docs/v1.2.x/Middlewares/Reply.md
https://www.fastify.io/docs/v0.40.x/Middlewares/Request.md
https://www.fastify.io/docs/v0.37.x/Middlewares/Hooks.md
https://www.fastify.io/docs/v1.1.x/Middlewares/Request.md
https://www.fastify.io/docs/v0.37.x/Middlewares/Request.md
https://www.fastify.io/docs/master/Middlewares/Request.md
https://www.fastify.io/docs/v0.42.x/Middlewares/'./Reply.md'
https://www.fastify.io/docs/v0.40.x/Factory.md

The full logs (sorry it is in italian):
wget.log

Organisations SVGs need explicit width or height

Nucleode logo is there but it displays with 0x0 pixels. I will fix this specific case manually and I will try to identify a way to avoid this from happening again before merging PRs.

CC: @mcollina @fox1t @cemremengu

Typo: Middlewares

There is no plural of 'middleware', just as with the noun 'software', it is countless.

References:
https://en.wiktionary.org/wiki/software
https://www.wordhippo.com/what-is/the-plural-of/middleware.html
https://english.stackexchange.com/questions/257120/middleware-vs-middlewares

and, why not: https://twitter.com/taylorotwell/status/530445528568709122

Broken link in Documentation for Server-Methods

In the Server-Methods doc page the link to Fastify factory function is broken.

This might be only one of many broken links, as it is probably due to the way the markdown file is processed and the links are altered to match the website URL.

Refs:

• fastify/fastify#819
• fastify/fastify#801

Change all the references to the old repo to the new one

Every reference to lmammino/fastify-website need to be changed to fastify/website

Depends on #4

Link to fastify-cli in the homepage

See fastify/fastify#1011

Write plugin documentation is missing

As titled.

Now I have no time to fix, if someone wants to fix it go ahead! :)
https://github.com/fastify/fastify/blob/master/docs/Write-Plugin.md

Remove the messaging that we are faster than XYZ, and focus on overhead and ease of use intead

Currently our messaging might come out as aggressive vs the rest of the frameworks. However, we want to be good citizens of the Node.js ecosystem, and we have all used and loved the other frameworks.

How about we remove the "Yx faster than" boxes, and we adjust the rest of the messaging to that we focus on overhead and ease of use?

I've done a similar work in fastify/fastify#358.

move away from the .io TLD

The UK is an aggressor in the Chagos Islands, it forcefully relocated residents in late 60's early 70's and is now ignoring a UN order return the islands to Mauritius - all the while it is profiting from the .io TLD.

Having talked it over with @mcollina he's asked me to open an issue proposing that we move away from the .io TLD , until/unless the Chagos Islands are restored.

http://www.thedarksideof.io/

https://www.bbc.com/news/uk-50511847

Same issue has been opened for Pino, pinojs/pino#746

Factory documentation is missing

As titled.

Now I have no time to fix, if someone wants to fix it go ahead! :)
https://github.com/fastify/fastify/blob/master/docs/Factory.md

Move website to GitHub pages + Cloudflare (CDN + SSL)

We are currently hosting the website on S3, which is not an ideal solution for several reasons:

1. It's a paid service
2. complex deployment process
3. No SSL (unless combined with CloudFront or some other CDN/SSL service)

The TODO list to get this done is the following:

• Activate deploy on GitHub pages #25
• Reconfigure main NS DNS records as in the table below (mostly for @mcollina)

Current Nameservers	Change Nameservers to:
c.dns.gandi.net	gordon.ns.cloudflare.com
b.dns.gandi.net	meg.ns.cloudflare.com
a.dns.gandi.net	Remove

• Wait for DNS propagation (best if 24hrs)
• Check if Clouflare detected the DNS propagation and activated the API access (for @lmammino)
• Add CDN invalidation on deploy through cloudflare APIs (#27)
• Remove old deployment to S3 (#28)

Important Note: The switch shouldn't generate any downtime

Divide the plugins in the ecosystem page into core and community

Broken links

Links between documentation pages are all broken.
Example:

The page https://www.fastify.io/docs/latest/Getting-Started/ links to Routes#async-await, and href value is /docs/latest/Routes.md#async-await.

/docs/latest/Routes.md does not exist; it should be /docs/latest/Routes#async-await; but we can't just update the doc on github, without breaking the navigation on github.com.

Do you have a quick way to make Route.md redirect to Route?
Otherwise I think it should be handled by processDocFiles; eventually I've a PR for this.

Links green color contrast ratio is very low

🐛 Bug Report

Links green colour contrast ratio doesn't meet WCAG guidelines, and it's really burning my eyes. Color Contrast Checker

To Reproduce

Expected behavior

Colour contrast ratio must be at least 4.5:1 or more. Darkening the green color to #008571 pass the guidelines and looks much better for me.

Happy to help with the issue if you guys don't mind the new color.

Website build broken

The website build is currently broken with the following error:

> src/scripts/processReleases.js build-temp/releases src/website

/home/circleci/fastify-website/src/scripts/processReleases.js:232
      const name = match[1]
                        ^

TypeError: Cannot read property '1' of null
    at mergedLines.map (/home/circleci/fastify-website/src/scripts/processReleases.js:232:25)
    at Array.map (<anonymous>)
    at readFile (/home/circleci/fastify-website/src/scripts/processReleases.js:230:33)
    at tryToString (fs.js:513:3)
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12)

The same error happens also local.

Currently investigating on this

latest doc alias

as title, we should be able to do:

http://www.fastify.io/docs/latest/Getting-Started/

(this should point to the latest released version of the guide)

Broken parser in "JSON Schema and Shared Schema support" table

In the JSON Schema and Shared Schema support table there are two kinds of check marks, the thick and green one (I suppose the correct one) and the thin and black one, which should probably be rendered as a "X" or simply nothing. Probably a parser issue.

https://github.com/fastify/fastify/docs/_data/ecosystem.yml returns 404

The very bottom of https://www.fastify.io/ecosystem/ links to https://github.com/fastify/fastify/docs/_data/ecosystem.yml, but it is not found.

Review copywriting

Here is a list of the files that might require some attention:

• metadata.json - Contains some generic metadata used all over the website (it can also be used to specify a google analytics track id, in case you have one you want to use to track website visits.
• acknowledgements.yml - structured data used to build the acknowledgement list on the home page
• benchmarks.yml - Structured data used to build the benchmark page
• ecosystem.yml - Structured data for the list of plugins, used both on the home page and in the ecosystem page
• team.yml - Structured data for the team section on the home
• error.md - Content for the 404 page
• home.html - Layout for the home page (nunjucks syntax)
• ecosystem.html - Layout for the ecosystem page (nunjucks syntax)
• docs_page.html - Layout for the documentation page (nunjucks syntax)
• benchmarks.html - Layout for the benchmark page (nunjucks syntax)

In case you want to see the outcome of the changes locally, before submitting the PR you should find all the necessary instructions to do so in the README.

GitHub buttons do not load on live site

Error in console: Loading failed for the <script> with source “https://buttons.github.io/buttons.js”.

Broken links in doc

How to test this:

npm run build
cd build
http-server # install this with npm i -g http-server or alternatively use `python -m SimpleHTTPServer 8080`

# in another shell
wget --spider -o wget.log -e robots=off --wait 1 -r -p --debug 'http://127.0.0.1:8080'

Links still broken:

Found 70 broken links.

http://127.0.0.1:8080/docs/v0.41.x/Factory.md
http://127.0.0.1:8080/docs/v0.40.x/Middlewares/'/docs/v0.40.x/Hooks'
http://127.0.0.1:8080/docs/v1.6.x/Middlewares/'/docs/v1.6.x/Request'
http://127.0.0.1:8080/docs/v0.39.x/Middlewares/'/docs/v0.39.x/Reply'
http://127.0.0.1:8080/docs/v1.4.x/Factory
http://127.0.0.1:8080/docs/latest/Middlewares/'/docs/latest/Hooks'
http://127.0.0.1:8080/docs/v1.2.x/Middlewares/'/docs/v1.2.x/Hooks'
http://127.0.0.1:8080/docs/v0.43.x/Factory.md
http://127.0.0.1:8080/docs/v1.0.x/Middlewares/'/docs/v1.0.x/Reply'
http://127.0.0.1:8080/docs/v1.1.x/Middlewares/'/docs/v1.1.x/Reply'
http://127.0.0.1:8080/docs/v0.39.x/Middlewares/'/docs/v0.39.x/Hooks'
http://127.0.0.1:8080/docs/v0.37.x/Middlewares/'/docs/v0.37.x/Reply'
http://127.0.0.1:8080/docs/v1.0.x/Middlewares/'/docs/v1.0.x/Request'
http://127.0.0.1:8080/docs/v1.0.x/Middlewares/'/docs/v1.0.x/Hooks'
http://127.0.0.1:8080/docs/v1.1.x/Middlewares/'/docs/v1.1.x/Hooks'
http://127.0.0.1:8080/docs/master/Factory.md
http://127.0.0.1:8080/docs/v0.38.x/Middlewares/'/docs/v0.38.x/Request'
http://127.0.0.1:8080/docs/v0.43.x/Middlewares/'/docs/v0.43.x/Reply'
http://127.0.0.1:8080/docs/v0.35.x/Middlewares/'/docs/v0.35.x/Request'
http://127.0.0.1:8080/docs/v0.37.x/Middlewares/'/docs/v0.37.x/Hooks'
http://127.0.0.1:8080/docs/v1.0.x/Factory
http://127.0.0.1:8080/docs/v0.35.x/Middlewares/'/docs/v0.35.x/Reply'
http://127.0.0.1:8080/docs/v1.3.x/Factory
http://127.0.0.1:8080/docs/v0.42.x/Middlewares/'/docs/v0.42.x/Request'
http://127.0.0.1:8080/docs/v0.43.x/Middlewares/'/docs/v0.43.x/Hooks'
http://127.0.0.1:8080/docs/v0.41.x/Middlewares/'/docs/v0.41.x/Reply'
http://127.0.0.1:8080/docs/v0.35.x/Middlewares/'/docs/v0.35.x/Hooks'
http://127.0.0.1:8080/docs/v1.1.x/Middlewares/'/docs/v1.1.x/Request'
http://127.0.0.1:8080/docs/latest/Factory
http://127.0.0.1:8080/docs/v1.6.x/Factory
http://127.0.0.1:8080/docs/v0.41.x/Middlewares/'/docs/v0.41.x/Hooks'
http://127.0.0.1:8080/docs/v1.2.x/Middlewares/'/docs/v1.2.x/Request'
http://127.0.0.1:8080/docs/v0.37.x/Middlewares/'/docs/v0.37.x/Request'
http://127.0.0.1:8080/docs/v0.38.x/Middlewares/'/docs/v0.38.x/Reply'
http://127.0.0.1:8080/docs/master/Logging/Factory.md
http://127.0.0.1:8080/docs/v0.41.x/Middlewares/'/docs/v0.41.x/Request'
http://127.0.0.1:8080/docs/master/Middlewares/'/docs/master/Reply'
http://127.0.0.1:8080/docs/v1.2.x/Factory
http://127.0.0.1:8080/docs/v1.3.x/Middlewares/'/docs/v1.3.x/Request'
http://127.0.0.1:8080/docs/latest/Middlewares/'/docs/latest/Request'
http://127.0.0.1:8080/docs/v0.38.x/Middlewares/'/docs/v0.38.x/Hooks'
http://127.0.0.1:8080/docs/v0.36.x/Middlewares/'/docs/v0.36.x/Reply'
http://127.0.0.1:8080/docs/v1.5.x/Middlewares/'/docs/v1.5.x/Reply'
http://127.0.0.1:8080/docs/v1.6.x/Middlewares/'/docs/v1.6.x/Reply'
http://127.0.0.1:8080/docs/master/Middlewares/'/docs/master/Hooks'
http://127.0.0.1:8080/docs/v1.4.x/Middlewares/'/docs/v1.4.x/Request'
http://127.0.0.1:8080/docs/v0.42.x/Middlewares/'/docs/v0.42.x/Reply'
http://127.0.0.1:8080/docs/v0.36.x/Middlewares/'/docs/v0.36.x/Hooks'
http://127.0.0.1:8080/docs/v1.5.x/Factory
http://127.0.0.1:8080/docs/v1.5.x/Middlewares/'/docs/v1.5.x/Hooks'
http://127.0.0.1:8080/docs/master/Server-Methods.md
http://127.0.0.1:8080/docs/v1.6.x/Middlewares/'/docs/v1.6.x/Hooks'
http://127.0.0.1:8080/docs/v1.3.x/Middlewares/'/docs/v1.3.x/Reply'
http://127.0.0.1:8080/docs/v1.4.x/Middlewares/'/docs/v1.4.x/Reply'
http://127.0.0.1:8080/docs/v0.43.x/Middlewares/'/docs/v0.43.x/Request'
http://127.0.0.1:8080/docs/v1.1.x/Factory
http://127.0.0.1:8080/docs/v0.40.x/Middlewares/'/docs/v0.40.x/Request'
http://127.0.0.1:8080/docs/v0.42.x/Middlewares/'/docs/v0.42.x/Hooks'
http://127.0.0.1:8080/docs/v0.40.x/Middlewares/'/docs/v0.40.x/Reply'
http://127.0.0.1:8080/docs/v0.40.x/Factory.md
http://127.0.0.1:8080/docs/v0.39.x/Middlewares/'/docs/v0.39.x/Request'
http://127.0.0.1:8080/docs/v1.3.x/Middlewares/'/docs/v1.3.x/Hooks'
http://127.0.0.1:8080/docs/v1.4.x/Middlewares/'/docs/v1.4.x/Hooks'
http://127.0.0.1:8080/docs/latest/Middlewares/'/docs/latest/Reply'
http://127.0.0.1:8080/docs/v1.2.x/Middlewares/'/docs/v1.2.x/Reply'
http://127.0.0.1:8080/docs/v1.5.x/Middlewares/'/docs/v1.5.x/Request'
http://127.0.0.1:8080/docs/master/Factory/Logging.md
http://127.0.0.1:8080/docs/v0.42.x/Factory.md
http://127.0.0.1:8080/docs/v0.36.x/Middlewares/'/docs/v0.36.x/Request'
http://127.0.0.1:8080/docs/master/Middlewares/'/docs/master/Request'

Consider using docusaurus

https://docusaurus.io/en/
https://github.com/facebook/docusaurus

It has built-in i18n, search integration, theming, versioning, blog etc. geared towards opensource projects (used by some well known ones as well). It might be worth giving a try.

Dark theme

As titled.

Is it possible (in a simple way) to add a dark theme?

[Discussion] Possibility to automatically generate benchmarks file

It would be nice if we can somehow automatically generate the file used as data source to render the benchmarks page, so that we might be able to easily keep the page in sync with the evolution of the benchmarks.

I haven't dig in depth into this yet, so I can't propose a complete solution, but I'd love to raise the issue anyway, maybe you already have an easy solution in mind.

Google Analytics tracking id

In case we want to enable Google Analytics in the tracking.

@mcollina, if you want this, once you have a tracking id associated to fastify.io, you simply need to update src/website/metadata.json and insert the value under google_analytics.

The template will take care to pick up the value and generate the needed analytics snippet.

Depends on #18

Rate limit to Github API

node src/scripts/downloadReleases.js fastify/fastify build-temp/releases v0.11.0

downloading releases into /home/circleci/fastify-website/build-temp/releases
{ StatusCodeError: 403 - {"message":"API rate limit exceeded for 52.90.181.163. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)","documentation_url":"https://developer.github.com/v3/#rate-limiting"}
    at new StatusCodeError (/home/circleci/fastify-website/node_modules/request-promise-core/lib/errors.js:32:15)
    at Request.plumbing.callback (/home/circleci/fastify-website/node_modules/request-promise-core/lib/plumbing.js:104:33)
    at Request.RP$callback [as _callback] (/home/circleci/fastify-website/node_modules/request-promise-core/lib/plumbing.js:46:31)
    at Request.self.callback (/home/circleci/fastify-website/node_modules/request/request.js:188:22)
    at emitTwo (events.js:125:13)
    at Request.emit (events.js:213:7)
    at Request.<anonymous> (/home/circleci/fastify-website/node_modules/request/request.js:1171:10)
    at emitOne (events.js:115:13)
    at Request.emit (events.js:210:7)
    at IncomingMessage.<anonymous> (/home/circleci/fastify-website/node_modules/request/request.js:1091:12)
  name: 'StatusCodeError',

Broken link on https://www.fastify.io/docs/latest/Getting-Started/

Search and click on the word "ecosystem" and it throws 404

Dead link on lmammino.github.io/fastify page

I really like the documentation you put on github pages. While trying to find out which template you use I noticed that the link to the layout home.html is actually dead.

Unfortunately; It's the one in the footer which asks for PR to improve the page itself.

The link in question is: https://github.com/fastify/fastify/docs/_layouts/home.html

LTS missing in Doc section

https://www.fastify.io/docs/latest/ doesn't list LTS docs

Add past sponsor and contributors in the homepage

As titled!
I don't think the current configuration allows this, I can't do this work at the moment, so I'll leave this issue here :)

Ref: fastify/fastify#1171

logo in menu appears stretched

[Feature] switch to netlify deploy system

good point:

1. can preview the page in the pull request
2. simple migration

Preview URL: https://zen-kalam-f6e81f.netlify.com/

Keep update ecosystem page

How can we keep update the ecosystem list?

Document returning a stream from a route

re: fastify/fastify#23