Skip to content

layout improvements, style consistency#85

Open
a-chris wants to merge 2 commits intopalladius:mainfrom
a-chris:main
Open

layout improvements, style consistency#85
a-chris wants to merge 2 commits intopalladius:mainfrom
a-chris:main

Conversation

@a-chris
Copy link
Contributor

@a-chris a-chris commented Mar 3, 2026

Improved layouts for a few pages and style consistency

Added /sponsors link

image

Updated sponsors page

image

Using the same yellow of landing page

image

Titles now have the same gray tone

image

Wider speaker carousel

image

Made blog layout responsive

before
image
image

after
image
image

@netlify
Copy link

netlify bot commented Mar 3, 2026

Deploy Preview for rubycon ready!

Name Link
🔨 Latest commit 035fa31
🔍 Latest deploy log https://app.netlify.com/projects/rubycon/deploys/69ab29115b3a340008810c2f
😎 Deploy Preview https://deploy-preview-85--rubycon.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the visual consistency and layout of the website. It standardizes color schemes for links and titles, introduces a new component for larger content sections, and refines the responsiveness of the blog page, resulting in a more polished and user-friendly interface.

Highlights

  • Color Consistency: Standardized link colors to a consistent yellow shade (yellow-600/400) and updated title text colors to a uniform gray tone (gray-600/700) across various pages for improved visual harmony.
  • Layout Improvements: Introduced a new section_large.html include to enable wider content sections, specifically applied to the speakers carousel, enhancing its presentation.
  • Responsive Blog Layout: Refined the articles (blog) page layout to be more responsive, ensuring better display and user experience on different screen sizes.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • rubycon.it/_includes/faq.html
    • Updated support and Discord link colors from text-amber-600 to text-yellow-600.
    • Changed the default text color in the FAQ section from text-gray-500 to text-gray-600.
  • rubycon.it/_includes/header.html
    • Added the cursor-pointer class to the tickets button for improved user experience.
  • rubycon.it/_includes/schedule.html
    • Applied text-gray-700 to bold schedule entries for consistent title styling.
    • Corrected a capitalization in 'Mouth of the Rubicon' to 'mouth of the Rubicon'.
  • rubycon.it/_includes/section.html
    • Removed a trailing newline character at the end of the file.
  • rubycon.it/_includes/section_large.html
    • Added a new include file for creating larger, centered content sections with a red separator.
  • rubycon.it/_includes/speakers.html
    • Switched from using section.html to the newly introduced section_large.html for the speakers section.
  • rubycon.it/_includes/venue.html
    • Changed icon and link colors from text-amber-600 to text-yellow-400 for consistency.
  • rubycon.it/_posts/2025-10-14-hotel-ambasciatori.md
    • Updated the Google Maps link color from text-amber-600 to text-yellow-400.
  • rubycon.it/articles.html
    • Modified the blog post card styling to ensure it takes full width and is centered, improving responsiveness.
  • rubycon.it/assets/css/style.scss
    • Added a default text color (#1f2937) to the header and mobile menu for consistency.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request introduces several useful style and layout improvements. My review focuses on improving maintainability and adhering to project guidelines. I've left a few comments on potential improvements regarding code duplication, redundant CSS, and the use of variables for colors.

A key point from the review is that this pull request is missing updates to the site version and changelog. The repository's style guide is clear on this point (lines 50-51 and 78), requiring an update to site_version in rubycon.it/_config.yml and an entry in CHANGELOG.md for all changes. Please ensure these files are updated before merging to comply with the project's contribution process.

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.

1 participant