errose28 commented on PR #135:
URL: https://github.com/apache/ozone-site/pull/135#issuecomment-2744395440
Thanks for working on this. I have some high level suggestions to improve
the appearance before looking at the text content. Although there are a lot of
suggestions here, most of them should be simple to implement.
## Banner
- Make the background a lighter shade of green, or maybe even gray. This
will help with contrast for the foreground elements.
- Add a gradient to the background. See the social card for an example of
this.
- Shrink the Ozone logo to be the same height as the text, then reduce the
size of the overall banner to match. This should be about a 50% reduction in
height.
- Make the foreground and background colors of the "download" button the
inverse of those on the "getting started" button, instead of giving it a clear
background.
- See [Nifi's banner](https://nifi.apache.org/) for an example of this.
## Sections
I think we can remove the "What is Apache Ozone" section. It is somewhat
redundant with the banner and breaks up the flow of the page. If we need more
info here we can expand the banner content, but I don't think we do.
For the icons, we can start out using [Bootstrap
icons](https://icons.getbootstrap.com/). These are MIT licensed SVG files that
we are already using in other parts of the site. These can be made larger and
have their foreground color changed to green, which should blend much better
than the emojis that are there currently. We may be able to make nicer icons
later, but this is an easy drop-in improvement. I've included specific options
for each section below.
I would lay out the sections similar to what
[Airflow](https://airflow.apache.org/) has done. Each section gets a title
centered in a large font, and each point below has a large single color icon,
one or two word title, and a description. The boxes around the text are not
necessary, and it might be simpler to remove them since it looks bad if they
are not all the same size.
Here is what I would recommend for each specific section. I think the
shorter titles read better, and a reasonable person is not assuming that the
homepage has an exhaustive list, so no need to clarify that these are only a
few highlights.
### Use Cases (Renamed from "Common Use Cases")
I would move this ahead of features, since it is shorter and more
fundamental. People don't care about the features if they don't have a use case
for it in the first place. The existing three sections here look good, here are
the icons I would pair them with:
- Data Lake [water icon](https://icons.getbootstrap.com/icons/water/)
- Object Storage [bucket icon](https://icons.getbootstrap.com/icons/bucket/)
- Big Data Storage [folder
icon](https://icons.getbootstrap.com/icons/folder2/)
I would leave the "See who uses Ozone" button at the end of this section,
but use the green background/white foreground like the other buttons.
### Features (Renamed from "Key Features")
These are the sections I would use here. There are still 6 options so we can
keep the 3x2 layout. Notably I have removed "cloud native" since our Kubernetes
story is not very good and I have yet to see anyone doing cloud deployments of
Ozone.
- Scalable [line graph
icon](https://icons.getbootstrap.com/icons/graph-up-arrow/)
- Resilient [connected nodes
icon](https://icons.getbootstrap.com/icons/diagram-3/)
- I would move this to second place since it is pretty important.
- I've removed "Reliable" from the title since that seems redundant
- Secure [lock icon](https://icons.getbootstrap.com/icons/lock/)
- I would use this as the new name for the "Enterprise Ready" section,
since the description is only about security
- Performant [speedometer
icon](https://icons.getbootstrap.com/icons/speedometer/)
- This is also important to call out, I've moved it towards the top of
the list.
- Multi-Protocol [stack icon](https://icons.getbootstrap.com/icons/stack/)
- We can combine the S3 and Hadoop sections into this one.
- Efficient [rack icon](https://icons.getbootstrap.com/icons/hdd-rack/)
- This is an important selling point. Ozone allows dense storage nodes
and can scale enough to consolidate multiple clusters of other storage systems,
which reduces operational costs.
### Integrations
This is a good section to have, and we can largely copy the layout from
[Airflow's homepage](https://airflow.apache.org/) since that's Apache licensed
code. I don't think we will have so many tiles here that the search bar is
necessary though. Each tile can link to the corresponding page in the
[Integrations
section](https://ozone-site-v2.staged.apache.org/docs/user-guide/integrations/).
Some items may link to pages in the admin guide, like
[Ranger](https://ozone-site-v2.staged.apache.org/docs/administrator-guide/configuration/security/ranger/),
[Knox](https://ozone-site-v2.staged.apache.org/docs/administrator-guide/configuration/security/knox/),
[Kerberos](https://ozone-site-v2.staged.apache.org/docs/administrator-guide/configuration/security/kerberos/),
[Prometheus](https://ozone-site-v2.staged.apache.org/docs/administrator-guide/operations/observability/prometheus/),
[Grafana](https://ozone-site-v2.staged.apache.org/docs/administrator-guide/operations/observability/grafana/),
a
nd Vault (no page on the website for this yet).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
