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

Performance page #2122

Closed
wants to merge 12 commits into from
Closed

Conversation

insectengine
Copy link
Collaborator

  1. Add new performance page
  2. Add to index page (re-org features band)
  3. Add performance page to primary navigation (re-org navigation)
  4. Add link to continuum page (Reactive) to the primary navigation

@holly-cummins

Copy link

github-actions bot commented Sep 20, 2024

🙈 The PR is closed and the preview is expired.

@holly-cummins
Copy link
Contributor

holly-cummins commented Sep 23, 2024

+1 to having this page, but I made some suggestions on Jeff Beck's google document that it would be nice to see incorporated here. The version on this PR doesn't mention our excellent throughput, which we need to start talking about.

@insectengine
Copy link
Collaborator Author

@holly-cummins - please check this out again as I've updated the content.

@holly-cummins
Copy link
Contributor

Looks good to me, thanks! :)

I'm looking forward to using that throughput icon in other places, too.

@holly-cummins
Copy link
Contributor

I'd add an approving review but I don't have the permissions to assign reviewers.

@insectengine
Copy link
Collaborator Author

I added some reviews.

_includes/header-navigation.html Outdated Show resolved Hide resolved
_includes/header-navigation.html Show resolved Hide resolved
<img class="dark-only" src="{{site.baseurl}}/assets/images/about/icon-reactive-dark.svg">
<h3><a href="/continuum">Reactive Core</a></h3>
<p>Built on a robust reactive core, Quarkus ensures fast and efficient performance, supporting the development of a wide variety of modern applications.</p>
<img class="light-only" src="{{site.baseurl}}/assets/images/performance/icon-performance.svg">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would not have put performance in the second item, on the second line.

I know it's a core strength, but, that's not going to attract lots of developers (otherwise, many languages would not be as popular as they are...).

<img class="light-only" src="{{site.baseurl}}/assets/images/performance/icon-performance.svg">
<img class="dark-only" src="{{site.baseurl}}/assets/images/performance/icon-performance-dark.svg">
<h3><a href="/performance">Performance</a></h3>
<p>Quarkus streamlines framework optimizations in the build phase to reduce runtime dependencies and improve efficiency. By precomputing metadata and optimizing class loading, it ensures fast startup times for JVM and native binary deployments, cutting down on memory usage.</p>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hum, this is semantically equivalent to the last sentence of the container feature.

_includes/performance.html Outdated Show resolved Hide resolved
_includes/performance.html Outdated Show resolved Hide resolved
_includes/performance.html Outdated Show resolved Hide resolved
_includes/performance.html Outdated Show resolved Hide resolved
_includes/performance.html Outdated Show resolved Hide resolved
@insectengine insectengine marked this pull request as ready for review October 24, 2024 22:44
@insectengine
Copy link
Collaborator Author

I feel this is ready for review...
1) Home Page - Updated the "features" band to "benefits" and added the Performance icon/text
https://quarkus-site-pr-2122-preview.surge.sh/

2) Performance Page - Updated content from the doc.
https://quarkus-site-pr-2122-preview.surge.sh/performance/

3) Flyout Nav - Added to the "Why" flyout

@holly-cummins
Copy link
Contributor

Where are we with this, @cescoffier? It would be fantastic to get this reviewed and up so we can start getting eyeballs on this important content.

@cescoffier
Copy link
Member

@holly-cummins @insectengine Hey! Sorry, missed the last update. It looks A LOT better. I will do a few suggestion later today:

  • @holly-cummins, don't we have an image for the introduction? I preferred ending the paragraph with the Why
  • The is the weird (or absence of) transition in the reactive core section
  • The high throughput paragraph does not talk about high throughput per se.

_includes/performance.html Outdated Show resolved Hide resolved
_includes/performance.html Outdated Show resolved Hide resolved
_includes/performance.html Outdated Show resolved Hide resolved
@holly-cummins
Copy link
Contributor

@cescoffier, it looks like your suggested changes are now live at https://quarkus-site-pr-2122-preview.surge.sh/performance/

@cescoffier
Copy link
Member

@holly-cummins not the landing page (order + outdated content).

Maybe we can limit this PR to the performance page.

@cescoffier
Copy link
Member

@insectengine Thanks for the update, waiting for the previous (because, no... I'm not reviewing HTML blurb :-))

@cescoffier
Copy link
Member

@insectengine The content on the landing page is outdated:

That's what we have on quarkus.io:
image

@insectengine
Copy link
Collaborator Author

@cescoffier - updated the Reactive title/content for the homepage.

@cescoffier
Copy link
Member

LGTM, @holly-cummins Are you ok?

@insectengine maybe squash the commits. 12 commits, that's a bit too much :-)

@holly-cummins
Copy link
Contributor

Yes, squash and go, I think!

@insectengine
Copy link
Collaborator Author

insectengine commented Nov 14, 2024

@cescoffier - A merge commit blocked any squashing I tried to do. I pulled the changed files into a new branch and submitted a new PR for the Performance page.

#2163

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.

3 participants