-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOW TO CONTRIBUTE] Project target and management #32
Comments
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
It's amazing to see this repo get the attention it deserves! I'll try to help out where I can (to which, I'm sorry for not carrying it over the finish line the first time around). |
I would recommend we scrap i18n from the plan. |
@mcollina I think we are good to start the I would use this setting tho: I would propose these steps:
|
I agree. I'm still trying to get access to fastify.dev. Sigh. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Renamed the old repo to https://github.com/fastify/website-metalsmith @mcollina could we switch the |
that was done |
Hi,
If you are reading this, you want to contribute to the new Fastify website: thank you!
This message explains all you need to know to join.
Useful links
Contribute
If you want to contribute to this project, you can:
How to contribute
This repository follows the Fastify organization CONTRIBUTING and GOVERNANCE statements.
As a reminder: before working on an issue, be sure that:
To submit valuable changes to the project, you need to fork this repository and submit your code through a Pull Request. Here the step-by-step guides:
Project target
The target of this project is to redo the Fastify website: https://www.fastify.io/
Migrating to a new tech stack and new processes let the Fastify community contribute more easily to the documentation to let the Fastify web framework grow even more.
This journey was started by @Xhale1 and @luisorbaiceta, and all the credits till commit 3341dd3 and the work to sponsor this new project goes to them.
Tech Stack
The new website will be implemented with Docusaurus. It means that this project includes these topics:
I'm not an expert on these topics. I'm just a "documentation reader" and a "pragmatic problem solver", so do not expect a TODO-LIST during a PR review, but a collaborative discussion 🤝
Project Boundaries
We can't just delete the old website and create a new one 😄 We must abide by these constraints:
fastify/fastify
(not on this repository)<=3
Nice to have
TRACKING PROJECT: https://github.com/orgs/fastify/projects/7
These features are not in the scope of this specific project - but we will try to implement the required features while keeping in mind the following list:
Getting started
introductionhttps://medium.com/@fastifyjs
to this new websiteFor sure, we are going to do them in a follow-up project at least 💯
PS: if the issue you are looking at has an empty description, it means that I'm still writing down the requirements, be patient and, meanwhile, fork the repository and start playing with it.. does it work in your local environment?
Tasks
The text was updated successfully, but these errors were encountered: