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

Enh: Site redesign #11

Closed
wants to merge 5 commits into from
Closed

Conversation

ajstrongdev
Copy link

@ajstrongdev ajstrongdev commented Aug 30, 2023

Create a website redesign for FerenOS.

Todo:

  • Create homepage
    • Create navbar
    • Create banner
    • Add "learn more" section
    • Add notices
    • Add banners for apps
  • Add download page
  • Add "help" pages

@dominichayesferen
Copy link
Contributor

dominichayesferen commented Sep 3, 2023

tbh I'm probably not going to end up merging this on the virtue that it does not align with the design I want to go for with Feren OS's website by the time I actually get to giving it a proper website - I appreciate the offer, it's just... with my secrecy for now about how I plan to make it look... right now you're unlikely to ever get the result I'd want.

Plus another factor I need to consider besides that is longevity, as I want to be sure the technology used can last for many years to come - not that you likely didn't consider that already, it's just another thing I need to figure out once at that point of considering pull requests to create a non-Weebly Feren website.

@ajstrongdev
Copy link
Author

that it does not align with the design I want to go for with Feren OS's website by the time I actually get to giving it a proper website - I appreciate the offer, it's just... with my secrecy for now about how I plan to make it.

It would make more sense to be open so that contributors are able to align with your vision. This is still early development and so can absolutely be changed easily.

As for future-proof, this is utilising tailwindCSS, aside from that there are no other technologies to consider. It works perfectly fine and is future proof.

@dominichayesferen
Copy link
Contributor

dominichayesferen commented Sep 6, 2023

It would make more sense to be open so that contributors are able to align with your vision. This is still early development and so can absolutely be changed easily.

That's the plan. It's just that I want to drop in an initial base of my own first just so that EVERYONE, including myself, has an idea of the initial website I want to go for so it can be iterated by everyone accordingly, because right now the Weebly site is, contrary to popular belief, not the general design I'm aiming for with a non-Weebly one.

Not that I wouldn't be able to grasp your submission's code and syntax, just... I'd rather learn while building for future proofing reasons.
Edit: In a sense the idea is that the initial website, once made, is going to be more-so a surprise for the general public, and then once revealed able to be contributed to, with a unified OS-matching CSS, completely revamped Start Page, and even more.
I've tried to push people away from beating me to the punch as site redos like this one are unfortunately likely going to turn out to be waste of time and effort later for the reasons I've pointed out, which honestly sucks as I do seriously appreciate the effort (wrong place wrong time situation).

@ajstrongdev ajstrongdev closed this by deleting the head repository Sep 25, 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

Successfully merging this pull request may close these issues.

2 participants