Skip to content

Feat/website for auth#131

Open
Ingole712521 wants to merge 4 commits into
roshankumar0036singh:mainfrom
Ingole712521:feat/website-for-auth
Open

Feat/website for auth#131
Ingole712521 wants to merge 4 commits into
roshankumar0036singh:mainfrom
Ingole712521:feat/website-for-auth

Conversation

@Ingole712521

@Ingole712521 Ingole712521 commented Jun 18, 2026

Copy link
Copy Markdown

Summary

Adds a production-ready developer website for Auth Server under developer-website/. The site gives contributors and integrators a professional landing page, quick-start docs, and links to GitHub, Swagger, and the npm SDK.

Working #126

What's included

Landing page

  • Hero — Tagline, CTA buttons, tech stack pills, and animated terminal quick-start
  • Features — JWT, OAuth 2.0, MFA, social login, RBAC, and production ops
  • Architecture — Clean architecture layer overview
  • Resources — Links to Swagger, TypeScript SDK, and docs
  • Open source — MIT license CTA with GitHub star link

UI / UX

  • Dark theme with dot + grid background pattern and indigo accent glow
  • Full-viewport hero on first load; background extends under the fixed navbar
  • Glass-style header with icon navigation (Features, Docs, API, GitHub)
  • Animated terminal with typing effect, syntax highlighting, and blinking cursor
  • Staggered hero entrance animations (respects prefers-reduced-motion)
  • Responsive layout with mobile nav menu

Tech stack

  • Next.js 16 (App Router)
  • React 19
  • Tailwind CSS v4
  • Geist font family

Summary by CodeRabbit

Release Notes

  • New Features

    • Added comprehensive documentation page with getting-started guide
    • Introduced responsive navigation header with mobile menu support
    • Launched redesigned landing page featuring product highlights, architecture overview, resources, and open-source information
    • Added animated terminal demonstration component
  • Style

    • Migrated to modern CSS framework with enhanced animations
    • Redesigned global styling with gradient backgrounds and improved visual hierarchy
    • Added footer section with external links
  • Chores

    • Updated project dependencies to support new styling framework

- Added Tailwind CSS as a dependency and configured PostCSS.
- Updated global styles to utilize Tailwind's utility classes.
- Created a new layout with Header and Footer components for better structure.
- Implemented a responsive design for the homepage with feature highlights.
- Added a documentation page with setup instructions.
- Removed unused CSS files to streamline the project.
- Introduced new landing page components: Hero, Features, Architecture, Resources, and OpenSource.
- Updated global styles to include a new landing hero design with responsive background gradients.
- Replaced static content with dynamic components for better maintainability and scalability.
- Added icons for features to improve visual representation.
- Integrated tagline and description from a centralized copy file for consistency across the site.
- Updated global styles for a more cohesive dark theme and improved background effects.
- Refined landing hero section with new animations and responsive design.
- Introduced a Terminal component to simulate command-line interactions for user engagement.
- Adjusted layout and spacing across various components for better visual hierarchy.
- Enhanced footer and header styles to align with the new design language.
@github-actions

Copy link
Copy Markdown
Contributor

Thank you for your contribution! Before we can merge this PR, we need you to sign our Contributor License Agreement.

To sign, please post a comment on this PR with the following exact text:

I have read the CLA and agree to its terms


I have read the CLA and agree to its terms.


You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.

@coderabbitai

coderabbitai Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

The Next.js developer website is replaced from a starter template to a full landing page. Tailwind CSS is wired up via PostCSS, shared copy/link constants are introduced, two icon libraries are added, and the layout is rebuilt with Header/Footer. Five landing sections (Hero, Features, Architecture, Resources, OpenSource) with an animated Terminal are composed into the home page, and a new Docs page is added.

Changes

Developer Website Landing Page

Layer / File(s) Summary
Tailwind setup and shared constants
developer-website/package.json, developer-website/postcss.config.mjs, developer-website/src/lib/copy.ts, developer-website/src/lib/links.ts
Adds tailwindcss, @tailwindcss/postcss, and postcss dependencies with PostCSS config; introduces TAGLINE, TAGLINE_SUB, and LINKS constants consumed by all components.
Shared icon components
developer-website/src/components/NavIcons.tsx, developer-website/src/components/landing/icons.tsx
Adds two icon libraries: NavIcons.tsx with navigation SVG icons (Features, Docs, Swagger, GitHub) and landing/icons.tsx with feature/UI icons (Shield, Key, OAuth, MFA, Users, Server, ArrowRight, ExternalLink).
Global CSS and layout shell
developer-website/src/app/globals.css, developer-website/src/app/layout.tsx, developer-website/src/app/page.module.css
Rewrites globals.css to Tailwind layers with hero glow, terminal blink, hero fade-in animations, and prefers-reduced-motion overrides; clears page.module.css; updates layout.tsx to mount Header/Footer with updated metadata.
Header and Footer components
developer-website/src/components/Header.tsx, developer-website/src/components/Footer.tsx
Adds a responsive Header with desktop nav, collapsible mobile menu (Escape-key dismissal, aria-* attributes, NavLink helper) and a Footer with license text and external links.
Animated Terminal component
developer-website/src/components/landing/Terminal.tsx
Client-side Terminal types through shell commands character-by-character with line pauses, loop reset, git/cd syntax highlighting, blinking cursor, and instant-completion for prefers-reduced-motion.
Landing page sections and home composition
developer-website/src/app/page.tsx, developer-website/src/components/landing/Hero.tsx, developer-website/src/components/landing/Features.tsx, developer-website/src/components/landing/Architecture.tsx, developer-website/src/components/landing/Resources.tsx, developer-website/src/components/landing/OpenSource.tsx
Adds five landing sections (Hero with Terminal, Features grid, Architecture layers, Resources cards, OpenSource CTA) and wires them into the Home page replacing the Next.js starter markup.
Docs page
developer-website/src/app/docs/page.tsx
New /docs route with metadata title "Docs" and a DocsPage component rendering Getting Started setup instructions (clone, Docker, SDK usage) and Next Steps links from LINKS.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Suggested labels

Medium, SSoC26

🐇 Hoppity hop, the site's brand new,
With Tailwind shimmer and a terminal too!
The hero glows, the cursor blinks,
git clone in style — what do you think?
From starter bones to landing grace,
This bunny built a beautiful place! ✨

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check ❓ Inconclusive The title 'Feat/website for auth' is vague and generic; it lacks specific detail about what the website accomplishes. Revise the title to be more specific, such as 'Add production-ready developer website with landing page, docs, and navigation' or 'Create Auth Server developer website with landing and documentation pages'.
✅ Passed checks (3 passed)
Check name Status Explanation
Description check ✅ Passed The pull request description is comprehensive and well-structured, covering the summary, what's included, UI/UX details, and tech stack. It exceeds the template requirements with substantive information.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@sonarqubecloud

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@developer-website/src/app/globals.css`:
- Line 3: Update the `.stylelintrc.json` configuration file to properly handle
Tailwind v4 at-rules. In the rules section, configure the `at-rule-no-unknown`
rule to ignore Tailwind directives by adding an `ignoreAtRules` array containing
"theme" and "import". If the stylelint configuration is no longer actively used
or maintained, you can alternatively remove the `.stylelintrc.json` file
entirely from the project to avoid confusion and maintenance overhead.

In `@developer-website/src/components/Header.tsx`:
- Around line 184-212: The mobile menu visual collapse controlled by the
grid-rows CSS classes does not prevent keyboard focus from reaching the NavLink
items and the "Get started" Link inside the menu-body. Conditionally render the
entire content inside the overflow-hidden div (which contains the NavLink.map
loop and the Link component) only when the open state is true, rather than
relying on CSS alone to hide it. This ensures that when the menu is closed,
keyboard users cannot tab through the hidden navigation items.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 7046d5a6-0200-430b-b207-b3a4338bb2dd

📥 Commits

Reviewing files that changed from the base of the PR and between 9ba7a54 and fc7790b.

⛔ Files ignored due to path filters (2)
  • developer-website/package-lock.json is excluded by !**/package-lock.json
  • developer-website/public/logo.png is excluded by !**/*.png
📒 Files selected for processing (19)
  • developer-website/package.json
  • developer-website/postcss.config.mjs
  • developer-website/src/app/docs/page.tsx
  • developer-website/src/app/globals.css
  • developer-website/src/app/layout.tsx
  • developer-website/src/app/page.module.css
  • developer-website/src/app/page.tsx
  • developer-website/src/components/Footer.tsx
  • developer-website/src/components/Header.tsx
  • developer-website/src/components/NavIcons.tsx
  • developer-website/src/components/landing/Architecture.tsx
  • developer-website/src/components/landing/Features.tsx
  • developer-website/src/components/landing/Hero.tsx
  • developer-website/src/components/landing/OpenSource.tsx
  • developer-website/src/components/landing/Resources.tsx
  • developer-website/src/components/landing/Terminal.tsx
  • developer-website/src/components/landing/icons.tsx
  • developer-website/src/lib/copy.ts
  • developer-website/src/lib/links.ts
💤 Files with no reviewable changes (1)
  • developer-website/src/app/page.module.css

--foreground: #171717;
@import "tailwindcss";

@theme {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify whether stylelint config is Tailwind-v4 aware and where the rule is enforced.

set -euo pipefail

echo "== stylelint-related config files =="
fd -HI 'stylelint|\.stylelintrc|stylelint\.config' .

echo
echo "== Search for at-rule-no-unknown settings =="
rg -n --hidden -S 'at-rule-no-unknown|scss/at-rule-no-unknown|ignoreAtRules|`@theme`|tailwind' .

Repository: roshankumar0036singh/auth-server

Length of output: 6047


🏁 Script executed:

cat .stylelintrc.json

Repository: roshankumar0036singh/auth-server

Length of output: 1436


🏁 Script executed:

cat -n developer-website/package.json | grep -A 5 -B 5 "stylelint\|lint\|script"

Repository: roshankumar0036singh/auth-server

Length of output: 742


Remove or update unused stylelint configuration for Tailwind v4 compatibility.

The .stylelintrc.json extends stylelint-config-standard-scss without configuring at-rule-no-unknown to recognize Tailwind v4 at-rules like @theme. While this doesn't currently impact CI (since stylelint isn't in the npm lint script), the config should either be removed if no longer used or updated to handle Tailwind directives by adding ignoreAtRules: ["theme", "import"] to prevent future issues if stylelint is re-enabled.

🧰 Tools
🪛 Stylelint (17.13.0)

[error] 3-3: Unexpected unknown at-rule "@theme" (scss/at-rule-no-unknown)

(scss/at-rule-no-unknown)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@developer-website/src/app/globals.css` at line 3, Update the
`.stylelintrc.json` configuration file to properly handle Tailwind v4 at-rules.
In the rules section, configure the `at-rule-no-unknown` rule to ignore Tailwind
directives by adding an `ignoreAtRules` array containing "theme" and "import".
If the stylelint configuration is no longer actively used or maintained, you can
alternatively remove the `.stylelintrc.json` file entirely from the project to
avoid confusion and maintenance overhead.

Source: Linters/SAST tools

Comment on lines +184 to +212
<div
id="mobile-menu"
className={`grid border-t border-zinc-800/70 transition-[grid-template-rows,opacity] duration-200 md:hidden ${
open
? "grid-rows-[1fr] opacity-100"
: "grid-rows-[0fr] opacity-0"
}`}
aria-hidden={!open}
>
<div className="overflow-hidden">
<div className="flex flex-col gap-1 px-4 py-3 sm:px-6">
{nav.map((item) => (
<NavLink
key={item.label}
item={item}
onNavigate={closeMenu}
className={mobileNavLinkClass}
/>
))}
<Link
href="/docs"
onClick={closeMenu}
className="mt-2 inline-flex items-center justify-center rounded-xl bg-accent px-4 py-2.5 text-sm font-semibold text-white transition-colors hover:bg-accent-hover"
>
Get started
</Link>
</div>
</div>
</div>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Prevent keyboard focus from reaching collapsed mobile-menu links.

When open is false, Line 186-Line 190 only visually collapses the menu; interactive children remain mounted and can still be reached via keyboard tabbing. Keep hidden menu items out of the tab order (e.g., conditionally render the menu body only when open, or otherwise make the closed state non-interactive for keyboard users).

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@developer-website/src/components/Header.tsx` around lines 184 - 212, The
mobile menu visual collapse controlled by the grid-rows CSS classes does not
prevent keyboard focus from reaching the NavLink items and the "Get started"
Link inside the menu-body. Conditionally render the entire content inside the
overflow-hidden div (which contains the NavLink.map loop and the Link component)
only when the open state is true, rather than relying on CSS alone to hide it.
This ensures that when the menu is closed, keyboard users cannot tab through the
hidden navigation items.

@roshankumar0036singh

Copy link
Copy Markdown
Owner

@Ingole712521 provide ss to assess the ui

@roshankumar0036singh

Copy link
Copy Markdown
Owner

@Ingole712521 resolev all the suggestions and sonar workflow flagged issues

@Ingole712521

Copy link
Copy Markdown
Author

I am still working on it, it will take a time to create website in a week or maybe early

@roshankumar0036singh

Copy link
Copy Markdown
Owner

@Ingole712521 no problem but just show me progress like a hero page so i can be sure of the result for the design

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.

2 participants