feat: redesign OpenTDF.io homepage and update documentation styling

[vmorps]

Preview

opentdf-docs-preview-new-home.surge.sh

Summary

• Redesigned the OpenTDF.io homepage with new messaging and contemporary design
• Added new landing page sections: Hero, Problem/Solution, Developer First, Standards, Community, and Final CTA
• Updated documentation CSS to reflect the new design system

Additional changes (post-review)

• Favicon — restored favicon.svg (cyan diamond mark); a new brand mark for OpenTDF as an independent project is in progress and will be swapped in via a follow-up PR
• Restored light/dark mode toggle and made navbar fully theme-aware (light/dark glass)
• Removed orphaned logo marks (opentdf-icon.svg) — replaced by the above
• Full light mode support for the homepage — all landing sections (Hero, ProblemSolution, DeveloperFirst, Standards, Community, FinalCTA) now adapt to light mode; code windows and diagrams intentionally stay dark
• Fixed note admonition dark mode readability (decoupled :::note from amber styling; added proper dark amber for :::tip only)
• Footer theme-aware — footer now switches colours in light mode
• CLI card — replaced brew install opentdf/tap/otdfctl with a link to the latest otdfctl release
  — updated docusaurus-plugin-openapi-docs to 4.7.1 (was installed at 4.4.0 against a ^4.7.1 requirement); fixed post-processing script to remove duplicate *.info.mdx files the updated plugin now generates alongside index.mdx, which were breaking useCurrentSidebarCategory() during SSG

Test plan

• Visit the homepage and verify all new sections render correctly
• Toggle light/dark mode and confirm homepage, navbar, footer, and admonitions all adapt
• Check the site on mobile and desktop screen sizes
• Verify documentation pages reflect updated CSS styling
• Confirm favicon and navbar logo display correctly in both light and dark mode
• Confirm npm run build completes with zero errors

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello @vmorps, I'm Gemini Code Assist¹! 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 significantly enhances the user experience and visual appeal of the OpenTDF.io website by introducing a modern, redesigned homepage and updating the overall documentation styling. The changes aim to provide clearer messaging, better highlight key features, and offer improved navigation for developers and community members, making it easier to understand and engage with the OpenTDF project.

Highlights

• Homepage Redesign: The OpenTDF.io homepage has been completely redesigned with new messaging and a contemporary visual style, incorporating new sections like Hero, Problem/Solution, Developer First, Standards, Community, and a final Call to Action.
• Documentation Styling Update: The documentation CSS has been updated to align with the new design system introduced on the homepage.
• Favicon and Icon Assets: The site's favicon has been replaced with a new SVG, and a new OpenTDF icon asset has been added.
• Java SDK Code Samples: New code samples for Java SDK encrypt/decrypt collection operations have been added to the documentation.

🧠 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

• code_samples/java/decrypt-collection-example.mdx
  • Added a new Java code sample demonstrating how to decrypt a collection of NanoTDF files.
• code_samples/java/encrypt-collection-example.mdx
  • Added a new Java code sample demonstrating how to encrypt a collection of data into NanoTDF files.
• docusaurus.config.ts
  • Updated the favicon path to use a new SVG icon.
  • Modified the custom CSS configuration to include a new 'landing.css' file for homepage specific styles.
  • Updated the navbar logo source to a new SVG icon.
  • Restructured the navbar links to include Quickstart, SDKs, Specification, and Community, while moving GitHub to the right.
  • Revised the footer links, organizing them into 'Project', 'Developers', 'Community', and 'Sponsor' categories, and removed the old footer logo and copyright format.
• src/components/landing/Community.module.css
  • Added CSS styles for the new 'Community' landing page section, including responsive design for cards and text.
• src/components/landing/Community.tsx
  • Added a new React component for the 'Community' section of the landing page, featuring links to GitHub, Discussions, and Contribution guidelines.
• src/components/landing/DeveloperFirst.module.css
  • Added CSS styles for the new 'DeveloperFirst' landing page section, including responsive grid layouts for SDK cards and CTA buttons.
• src/components/landing/DeveloperFirst.tsx
  • Added a new React component for the 'DeveloperFirst' section of the landing page, showcasing various SDKs with install commands and copy functionality.
• src/components/landing/FinalCTA.module.css
  • Added CSS styles for the new 'FinalCTA' landing page section, including responsive design for call-to-action buttons and a background glow effect.
• src/components/landing/FinalCTA.tsx
  • Added a new React component for the 'FinalCTA' section of the landing page, providing calls to action for tutorials, documentation, and source code.
• src/components/landing/Hero.module.css
  • Added CSS styles for the new 'Hero' landing page section, including responsive grid layout, badge styling, and code window aesthetics.
• src/components/landing/Hero.tsx
  • Added a new React component for the 'Hero' section of the landing page, featuring a prominent heading, descriptive text, call-to-action buttons, and a code preview window.
• src/components/landing/ProblemSolution.module.css
  • Added CSS styles for the new 'ProblemSolution' landing page section, including responsive card layouts and text formatting.
• src/components/landing/ProblemSolution.tsx
  • Added a new React component for the 'ProblemSolution' section of the landing page, outlining the challenges of traditional security and how OpenTDF provides solutions.
• src/components/landing/Standards.module.css
  • Added CSS styles for the new 'Standards' landing page section, including responsive grid layout for content and a TDF object diagram.
• src/components/landing/Standards.tsx
  • Added a new React component for the 'Standards' section of the landing page, detailing OpenTDF's adherence to standards like NIST ABAC and featuring a TDF object structure diagram.
• src/components/landing/index.ts
  • Exported all new landing page components (Hero, ProblemSolution, DeveloperFirst, Standards, Community, FinalCTA) for easier import.
• src/css/custom.css
  • Updated Docusaurus theme primary color variables to a new teal palette.
  • Modified the highlight code line background and border color.
  • Introduced new styling for 'tip' admonition blocks with amber colors.
  • Adjusted dark mode link, menu, and breadcrumb active colors to match the new primary color.
  • Removed specific dark mode navbar and footer styling, deferring to new global styles.
  • Updated navbar brand title color for dark mode.
  • Refactored footer styling to a new dark theme with updated link colors and copyright presentation.
  • Implemented a new navbar layout with brand on the left, nav items centered, and GitHub link on the right, including custom styling for the GitHub button.
• src/css/landing.css
  • Added new CSS utility classes for the landing page, including grid backgrounds, gradient meshes, text gradients, glow effects, code block animation, and section background colors.
  • Defined custom accent colors for SDK cards and their hover effects.
• src/pages/index.tsx
  • Updated the Open Graph description meta tag for the homepage.
  • Replaced the old homepage components (Hero, Columns, Features, Feedback) with the new set of landing page components (Hero, ProblemSolution, DeveloperFirst, Standards, Community, FinalCTA).
• static/img/favicon.svg
  • Added a new SVG file to be used as the site's favicon, featuring a dark background with a teal diamond and circle.
• static/img/filecontents.svg
  • Removed an outdated SVG image previously used to illustrate file contents.
• static/img/opentdf-icon.svg
  • Added a new SVG file for the OpenTDF icon, featuring a teal diamond and circle.

Activity

• No human activity has been recorded on this pull request yet.

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. ↩

[gemini-code-assist]

Code Review

This pull request introduces a major redesign of the OpenTDF.io homepage and new Java SDK code samples for encryption and decryption. A security audit identified several high-severity vulnerabilities in the Java code samples, specifically hardcoded secrets and insecure data handling. Additionally, the Java examples contain a compilation-preventing typo and resource leaks. These issues, even in documentation, pose a significant risk. It is strongly recommended to replace hardcoded credentials with a secure secret management solution, enforce secure TLS connections, correct the typo, and resolve resource leaks to adhere to best practices.

[vmorps]

Java sample files have been removed from the branch; they had nothing to do with my PR.

[jp-ayyappan]

/gemini review

[gemini-code-assist]

Code Review

This pull request introduces a complete redesign of the OpenTDF.io homepage, replacing the old content with a modern, visually appealing design and updated messaging. It adds several new landing page sections (Hero, Problem/Solution, Developer First, Standards, Community, and Final CTA) as React components. The documentation's CSS has also been updated to align with the new design system, including new color schemes, navbar styling, and footer design.

The new components are well-structured, and the styling makes good use of modern CSS features like custom properties, color-mix, and animations. The changes significantly improve the look and feel of the site.

I've added a couple of suggestions to improve the new CSS for the navbar, focusing on layout robustness and maintainability. Overall, this is a fantastic update.

[jp-ayyappan]

We also seem to have lost the light / dark switch functionality that is currently implemented in opentdf.io. We should fix that since it is used throughout the docs site.

[marythought]

tagging in @cassandrabailey293 for architecture awareness and review

[jrschumacher]

Blocking this PR. There is a relevant meeting next week and @cassandrabailey293 will reach out after.

[marythought]

Overall I really like the changes here and think this is a good, developer focused change in the right direction! I wonder about the existing content on the front page and if we should move it anywhere ("Project Overview and Current State
" for example could go in the feature matrix section) -- that can happen as a followup.

Also need to ensure that the code snippets are actually working code (https://github.com/opentdf/web-sdk for reference), or maybe a shortened version of https://opentdf.io/sdks/quickstart/go#go-implementation-code since the Go SDK has more features than web. Due to my newness I am not sure if this example actually works:

import { OpenTDF } from '@opentdf/sdk';
// Connect to the platform
const client = await OpenTDF.connect('http://localhost:8080');
// Encrypt with attribute-based policy
const ciphertext = await client.encrypt(data, {
attributes: ['https://example.com/attr/class/value/secret'],

[jrschumacher]

Looks like it was intended that the background of the first hero was to be

background-repeat: no-repeat;
background-size: cover;

Alignment found

[marythought]

🚀

[marythought]

🚀