Skip to content
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

New docs website #3132

Open
4 tasks
mcollina opened this issue Apr 17, 2024 · 9 comments
Open
4 tasks

New docs website #3132

mcollina opened this issue Apr 17, 2024 · 9 comments

Comments

@mcollina
Copy link
Member

I think it's time to develop a new docs website.

This should be:

  • fully (or mostly) statically generated
  • hosted on Vercel (as part of the deal with the OpenJS Foundation for the Node.js website)
  • support multiple versions (v5.x and v6.x)
  • deployed from another repository (to support multiple versions)
@Ethan-Arrowood
Copy link
Collaborator

🚀 This has been on my mind for sometime.

I've evaluated a number of options including Docusaurus, Nextra, and more. I couldn't find any framework that really had all the features we need out-of-the-box. So... I started building it myself!

In a private repo, I have a Next.js site with MDX and Tailwind. I've wired everything up, and I figured out a way for use to have versioned docs by leveraging MDX's dynamic and extensible markdown-as-components system. Furthermore, I've leveraged the latest features of Next.js to statically generate as much of the site as possible during build time. I'm currently working on getting some base styles set up; I'm making sure it's responsive from the start too.

I've had limited time to work on this, and have also been struggling to sustainably work on open source projects. I'd be more than happy to share what I'm building and work on this in public, but I'd like to investigate crowd-funding this project so that it is sustainable for me.

@mcollina
Copy link
Member Author

@Ethan-Arrowood are you thinking of building a new framework, making it OSS and then use it here?

@anfibiacreativa
Copy link

Thank you for opening the issue, @mcollina . I always see documentation as a low hanging fruit to introduce folks to OSS contributions. It's a way to break through and also learn about the technology while improving the docs. I also think that it needs a prompt from the core maintainers that they're looking forward to a refresher, because coming forward and saying "I think docs can be improved" as a newcomer to OSS can be intimidating.

@Ethan-Arrowood
Copy link
Collaborator

@mcollina , nope. just building the site for Undici.

@Ethan-Arrowood
Copy link
Collaborator

Ethan-Arrowood commented Apr 24, 2024

Here is my current plan:

  • Implement some basic styles and write some contribution docs
  • Create some rough designs (using figma tldraw is easier)
  • Write a post announcing the site project
  • Publish post and repo simultaneously + market on social media

As I mentioned previously, I'd really like to crowd-fund this work. I have my personal sponsorship/donation process figured out, but I'm not sure yet how to manage money for a project. I will keep investigating this and try to figure it out asap.

Stay tuned 🚀

@mertcanaltin
Copy link
Member

@Ethan-Arrowood I can contribute to the development of the site

@mcollina
Copy link
Member Author

mcollina commented May 3, 2024

Created the new repo at https://github.com/nodejs/undici-website.

@Ethan-Arrowood
Copy link
Collaborator

I'm going to move new conversations to the repo.

I will also be pushing my draft work to a branch soon.

@Ethan-Arrowood
Copy link
Collaborator

Design: nodejs/undici-website#1
My draft work: nodejs/undici-website#2

Didn't get as far in the styling as I would like, but I just am really struggling with time management atm.

@mcollina mcollina pinned this issue May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants