search

rocky-linux / rockylinux.org-gatsby

The official website of the Rocky Linux project.
https://rockylinux.org
BSD 3-Clause "New" or "Revised" License
177 stars 78 forks source link

Create pages Get Involved and Get In Touch #8

Closed domingoruiz closed 3 years ago

domingoruiz commented 3 years ago

Hi. I have the idea that cretate a Get Involved page and Get In Touch page. If you agree with the idea, I could take care of it and propose a pull request. If you agree, it would be good if you assigned me the issue. I am also all ears for proposals for those pages.

Thanks you.

Bye.

FoggyMtnDrifter commented 3 years ago

I think we should hold off on any further changes for now. @hbjydev is working on a custom component library for us to use on a future version of the site, as currently TailwindUI's licensing would prevent users who don't own a license from contributing.

FoggyMtnDrifter commented 3 years ago

I do, however, think this would be a great idea for the future site!

hbjydev commented 3 years ago

@ressonix That's gonna take me a long while to build out yet, so don't stop making improvements to this on my count just yet. Not unless they're Tailwind UI stuff - just try not to implement any more of that.

FoggyMtnDrifter commented 3 years ago

Okay, so we should try not to use any more TailwindUI components on the site and start implementing custom components? Just wanted to get further clarification on that part.

domingoruiz commented 3 years ago

I think the site should have simply been Bootstrap. As you already know, simple things are easy to maintain. Right now we use Hugo, Nodejs for Hugo, the themes, too many things that can go wrong when we could have a fantastic website using just Bootstrap.

FoggyMtnDrifter commented 3 years ago

While I agree that Bootstrap would be easier to contribute with, I feel that TailwindCSS offers more flexibility and the ability to build custom components quickly. TailwindCSS also has tons of plugin support and makes it super easy to optimize our CSS files from the get-go.

It's one of those situations where one can be beneficial but limiting, and the other can be beneficial and more flexible but more complicated to set up.

domingoruiz commented 3 years ago

Another option is the combination of Hugo and Bootstrap. It would be much simpler than the current one and we would continue to have the advantages.

domingoruiz commented 3 years ago

@hbjydev Can you link the issue to me to get to it?

Thank you.

hbjydev commented 3 years ago

I don't think this page is something we really need. Let's take this to Slack and discuss there for now.

hbjydev commented 3 years ago

We need to get the content/documentation team involved for pages like that.

FoggyMtnDrifter commented 3 years ago

Are we good to close this @hbjydev since we're using the Wiki/Docs side of things for this stuff at the moment?

hbjydev commented 3 years ago

Yeah, I think so. Closing...