New website #1518
Replies: 5 comments 19 replies
-
|
Do we already have a design in the works? Or do we need to work on that as well? |
Beta Was this translation helpful? Give feedback.
-
|
We have basically this: https://github.com/rome/tools/tree/main/assets So we still need to work on that |
Beta Was this translation helpful? Give feedback.
-
|
So basically just colours, icons and typography. We need to work on the prototype. |
Beta Was this translation helpful? Give feedback.
-
|
We've been talking about contracting a designer to help us set our early brand identity. We could also have them provide us with a website design |
Beta Was this translation helpful? Give feedback.
-
|
Ohhh. I don't consider me a designer, i just know some stuff about it! and have a professional doing that would be awesome! ✨ |
Beta Was this translation helpful? Give feedback.
-
|
Considerations about the design of the current website:
Anything else we could add to this list? |
Beta Was this translation helpful? Give feedback.
-
|
Nice. this looks good. But it's only for links with |
Beta Was this translation helpful? Give feedback.
-
|
Hmm yes. It wouldn't make sense to have that icon for simple links. I didn't think about that. I guess we can't add an icon for |
Beta Was this translation helpful? Give feedback.
-
|
I did this to see how it would look and i think it's too noisy.
But this makes a lot of sense for links with |
Beta Was this translation helpful? Give feedback.
-
|
I agree. Also, the noise really is the fact that we have too many links in a rather short text :D |
Beta Was this translation helpful? Give feedback.
-
|
@sebmck and I spoke about that |
Beta Was this translation helpful? Give feedback.
-
|
We should have an topbar for important links and search. I don't like the sidebar only design. |
Beta Was this translation helpful? Give feedback.
-
|
Personally more a fan of Preact, although I'm not against using Vue or Svelte just don't have experience with it. Don't know about how the rest of the team feels. Not trying to push against anything other than preact/react but using a tool the team is more comfortable with is probably a good idea. More so the staff as they'll probably be maintaining the website for longer. |
Beta Was this translation helpful? Give feedback.
-
|
+1 I don't mind having to use any of the mentioned libs but probably best to use the one we are most comfortable with. Unless we have some dedicated devs who focus on the website only. I guess most of us wanna work with the rest and not the website |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, i mentioned the others tools just to see what people think! And I'm inclined to use React. I've never used Preact, but it's basically React, so I'm ok with that! And I'll be working mostly focused on the website/front-ends only! |
Beta Was this translation helpful? Give feedback.
-
|
Please drop any links to developer tools / services websites that you really like. Personally I really like https://tailwindcss.com/ I would love to have interactive sections that explain the features of Rome really well |
Beta Was this translation helpful? Give feedback.
-
|
I really like the interactive sections! I was imagine something like that for the website! There's also the github homepage: https://github.com/ (logout or use browser's private mode to see) |
Beta Was this translation helpful? Give feedback.
-
|
I really like the idea of having interactivity like tailwind and github but looking at those pages, I think whats more important is that we get a professional design made. I understand this is already in the works so 💯 |
Beta Was this translation helpful? Give feedback.
-
I did most of the work in the current website, and when i did, i was in a moment where i was getting back to programming after almost 2 years without programming. There's thousands of things i can do better today and i would like to start to work on the new website. I'm opening this discussion, so we can define how it will be made!
I have suggested on discord to drop eleventy. And i don't think we need to use no deps and Rome for everything in the website now, but once Rome is ready!
Framework
In a local branch, I've already started to make some experiments using nextjs. Even though i like nextjs, i'm not sure it's the best option and we should consider the others frameworks. Lately I've been making a tool using SvelteKit and i like it. There's also gridsome, but looks like it'll take some time to upgrade to vue 3.
Even though i think we should use a framework, we still should keep deps at a minimum.
Styles
I would like to have styles centralized in one place, so any Rome webpage can use it. At first, service and website/docs! For this to happen, the front-end of the Rome service should use the same thing for styles as the website. I imagine sass or any css-in-js solution.
The module with all the styles would define general styles like color, spacing, typography, animation and etc, following the design tokens philosophy. Any specific style would be defined in the project itself, not in the module with general styles.
I don't like to use css vars for that because i think
color.primary("light");(scss or js) is better to read thanvar(--color-primary-light). In some cases the var can get too big!I've done some experiments with this idea a while back, but it can be done better than [this].(https://github.com/EduardoLopes/design-tokens-study/blob/main/src/styles/_space.scss)!
I can do a proof of concept, if needed!
Pages
Rome will be lot's of tools and i don't like the idea of having everything documented in a single page. Let's have a page for each tool!
There might be some points I'm missing! But I'm bringing this to discussion because i don't like the current website anymore and i wanna start working on a better visual identity to make a good looking/modern website. I'll be happy with anything we decided to use!
Beta Was this translation helpful? Give feedback.
All reactions