-
Notifications
You must be signed in to change notification settings - Fork 22
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
Enhancement request: redesign #70
Comments
Hi @laurensdewaele 👋🏻 Thanks for your proposal, and it quite looks nice to me! Please feel free to raise a PR with your suggestions/implementations, and also, I would be happy to jump on a call with you if you wish to discuss more :) Let me know! 🤗 |
Cool! Could we communicate through Discord? |
Just to update: I & @laurensdewaele are in discussion, and let's see what we are able to get out of that 💁🏻♀️ |
Draft design suggestion: Note that this is a rough idea and sketch, just to convey my ideas. Things that I've tried to implement:
Please leave abundant feedback!
|
@laurensdewaele thanks for the design! 🎉 Feedback from my side:
I want to hear @arirawr and @lpil thoughts on this too! After that, we can move forward with this issue 🔥 Amazing work! 💪🏻 |
Hey Sonia, It's a little unclear what you mean by following 2 points, the rest is clear:
I was thinking of a table view, listing all the contributions.
Would the above design accommodate the splitting you're talking about? |
Hi!
3 out of the 4 open issues are design issues.
I fear a coherent feeling across the website might be lost if each issue is addressed separately.
After checking out the website, I'm super impressed by the contributions Embark is giving to open source!
Right now, that information is a bit tucked away behind links to GitHub, Patreon and Open Source Collective.
I would like to make it a lot more visible.
I have time available right now, and due to reasons mentioned above, would actually like to do an overhaul of the website.
Would this be something the team would be open to?
Kind regards,
Laurens
The text was updated successfully, but these errors were encountered: