Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

Create pages Get Involved and Get In Touch #8

Closed
domingoruiz opened this issue Dec 11, 2020 · 12 comments
Closed

Create pages Get Involved and Get In Touch #8

domingoruiz opened this issue Dec 11, 2020 · 12 comments
Labels
priority: low This issue or pull request is of low priority tag: content Additions to (or modifications of) content in the repository type: enhancement New feature or request

Comments

@domingoruiz
Copy link

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
Copy link
Member

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
Copy link
Member

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

@hbjydev
Copy link
Contributor

hbjydev commented Dec 11, 2020

@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
Copy link
Member

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
Copy link
Author

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
Copy link
Member

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
Copy link
Author

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.

@rocky-linux rocky-linux deleted a comment from shadonna-bossy Dec 15, 2020
@domingoruiz
Copy link
Author

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

Thank you.

@hbjydev
Copy link
Contributor

hbjydev commented Jan 2, 2021

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

@hbjydev
Copy link
Contributor

hbjydev commented Jan 2, 2021

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

@hbjydev hbjydev transferred this issue from rocky-linux/rockylinux.org-hugo Feb 6, 2021
@hbjydev hbjydev added priority: low This issue or pull request is of low priority tag: content Additions to (or modifications of) content in the repository type: enhancement New feature or request labels Feb 6, 2021
@FoggyMtnDrifter
Copy link
Member

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

@hbjydev
Copy link
Contributor

hbjydev commented Feb 11, 2021

Yeah, I think so. Closing...

@hbjydev hbjydev closed this as completed Feb 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority: low This issue or pull request is of low priority tag: content Additions to (or modifications of) content in the repository type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants