Modern Login Page (現代化登入頁面)

Created By
jerry3315765a year ago
Test repository for MCP server
Overview

What is Modern Login Page?

Modern Login Page is a responsive and modern implementation of a login interface that features an intuitive user experience and rich interactive functionalities.

How to use Modern Login Page?

To use the Modern Login Page, clone the repository from GitHub, navigate to the project directory, and open the login-page/index.html file in a web browser or run it using a local server.

Key features of Modern Login Page?

  • 🎨 Modern design with gradient backgrounds and card layout.
  • 🔒 Security features including real-time password strength checking and email format validation.
  • ⚡ Interactive experience with floating label effects and instant form validation feedback.

Use cases of Modern Login Page?

  1. Creating a user-friendly login interface for web applications.
  2. Implementing secure login features in web projects.
  3. Customizing themes for branding purposes.

FAQ from Modern Login Page?

  • Is this project suitable for production use?

This is a front-end example and should be integrated with a backend API for production use.

  • Can I customize the theme?

Yes! You can customize the theme by modifying the CSS variables in the style.css file.

  • What technologies are used in this project?

The project is built using HTML5, CSS3, and JavaScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jerry3315765
Star
0
Language
CSS
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago