-
-
Notifications
You must be signed in to change notification settings - Fork 274
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
Redesigning conda-forge.org #1971
Comments
Happy to get feedback from the community :D |
This comment was marked as outdated.
This comment was marked as outdated.
Some more updates:
|
Thanks Jaime! 🙏 What level of feedback are you looking for at this stage? |
Thanks @jakirkham. Not much. Basically if anyone feels strongly about it and prefers we do it in a different way. I'll take silence as a go-ahead but it'd be better to have explicit support :D |
Sorry let me clarify. Is this meant as a high-level rough sketch of what you would like to do? If so, then comments would be about colors, layout, etc Or is this meant to go as-is? If so, comments would focus on missing links, typos, etc. Does that make more sense? Which of those are you going for? Or something else entirely? |
Ah ok, thanks for clarifying. The design is mostly settled now. We didn't get feedback back then (see hidden comments) so we had to assume folks were ok with our choices. We might fine tune some elements (i.e. the different states of the links), though, so if you have feedback in that direction, of course it's welcome. The currently proposed frontpage follows the conda-forge.org frontpage almost 1:1 in content, although it has been redesigned. That said, I'd like to focus on the transition to a new framework now without losing information in the way (no broken links, all functionality in place, etc). Once we are using the new framework we can easily submit PRs to adjust things. Let me know if you need more details, happy to provide them. It looks like we could start with a PR for point (1), right? |
The colors are not to my liking. Can we work on them? |
I think we chatted about the colors a few weeks ago? |
suggestions from @wolfv on colors |
Hello @conda-forge/core, @isabela-pf has shared three palettes I'm presenting below. Still preliminary and might need a few touches here and there, but these are ready for comments. In Isabela's words:
See them in action:
Try the dark/light theme switcher in the top bar to try both modes! If you ask me for my preferences, I really like the magenta, then cyan, and finally teal, but I would be happy with all of them. Please let us know if you have a preference! |
All 3 are beautiful in my mind ;) |
I agree that they all look great! Personally, I think the magenta one is the most aggressive, contrast-wise, so my order of preference is:
|
Cool! Yes, that matches what I'm seeing in an informal survey in the Quansight Slack:
|
Would be ok with Teal or Cyan. Magenta is too close to the red we wanted to move away from. Also is there an optical illusion at play or does Cyan have a gradient across it? For completeness, am writing down notes from the previous core meeting when we reviewed the new webpage together:
|
All of them have a gradient in the frontpage :D
Noted! |
I've merged the teal theme with some adjustments. I'll create issues for the pending tasks.
I think it does already. It's more noticeable in long docu pages, like this one. In short pages where the footer is already showing up, then it resumes the scrolling. |
New homepage is live! |
|
I think all we need to do is to move the CSS or w/e to the right path? |
paths are in this file: https://github.com/conda-forge/feedstock-outputs/blob/gh-pages/index.html We can change them there too. |
I can help design that page? My idea earlier was to design a card with name and its version as seen on conda metadata site. Thoughts? |
Sure! The search integration was done by hand so we'd need to ensure that translates. |
The primary usage of this page is to locate which feedstocks are generating a given package. So as an user I'd like to:
Note we have like 20k feedstocks so take into account the amount of HTML that needs to be rendered per item. It can get heavy. To that end, I think a simple table would be enough. While I love the info-rich cards, I don't think we can fetch the remote metadata in a performant way to display things like number of downloads or things like that, so let's stick to the metadata that it's provided in |
Status update:
My next item will be the announcements. Right now, this is a single RST page under the
However, I'm also tempted to merge the announcements into the current blog itself, and simply label each post type differently. Announcements would have a This is how it currently looks like in my local prototype: A single announcement: All announcements: The archive page: Thoughts? Footnotes |
More updates:
Coming next: community section. |
Latest updates:
|
Latest updates:
|
Latest updates:
|
Nice work! 👏 Submitted a couple PRs tweaking little things in the status page. Overall find it very clean and nice to read/explore! 🤩 |
In terms of the blog/announcement point above, would suggest we keep them separate. They serve different purposes and expect it is easier for user to consume what they want if we split them out As to blogpost activity, think we can pick this up. There are a number of things over the last year (or even past few months), which would benefit from a blogpost (website improvements, CI improvements, |
Hello conda-forge!
We now have a new website prototype available at https://cf-infra-docs.netlify.app/. This mostly showcases the work @asmitbm did during his GSoC internship last summer, but you can also see how some documentation would look like there, or the blog.
This prototype is based on the Docusaurus framework, which uses a React, Node and Markdown.
In parallel, @afshin has been working on a new status page in this PR. A preview is also available.
I've also done some work studying potential migration strategies for our documentation. I don't want to lose the valuable git history by converting all the RST over to MD, so instead I suggest the following strategy:
sphinx-markdown-builder
).I have a demo of how this strategy works in Quansight-Labs/cf-infra-docs#14. Plus the corresponding preview.
Migration steps
This is my proposed timeline:
feedstock-outputs
news/
#2057/docs/orga/
under/community
#2093/docs
in docusaurus #2077/docs
in docusaurus #2077/docs
in docusaurus #2077Thoughts, @conda-forge/core?
The text was updated successfully, but these errors were encountered: