- Created new JavaScript files for map pin, search, and user icons. - Added index.html with basic structure and linked assets. - Included vite.svg for the favicon.
36 lines
1.7 KiB
Markdown
36 lines
1.7 KiB
Markdown
# Lupmis 2.0 Design Guidelines
|
|
|
|
This repository contains the design guideline for Lupmis 2.0. It is intended to give product, design, and engineering teams a shared reference for the visual language, interface patterns, and usability principles used across the platform.
|
|
|
|
The guide is intentionally practical: it shows how the system should feel in real product contexts, including dashboards, consumer-facing screens, GIS/map experiences, shared components, and usability examples informed by Nielsen heuristics.
|
|
|
|
## Purpose
|
|
|
|
Use this guide as a common source of direction when designing, reviewing, or implementing Lupmis 2.0 interfaces. It helps align decisions around layout, component behavior, accessibility, consistency, information hierarchy, and overall product quality.
|
|
|
|
The goal is not to document every implementation detail. Instead, the guide provides a general design foundation that teams can apply across new and existing product surfaces.
|
|
|
|
## What Is Included
|
|
|
|
- Design system overview and component examples
|
|
- Common interface patterns for operational workflows
|
|
- Dashboard and analytics layout references
|
|
- Consumer portal examples
|
|
- GIS and map-based interface examples
|
|
- Usability guidance based on Nielsen heuristics
|
|
- Visual assets used by the guideline experience
|
|
|
|
## Using The Guide
|
|
|
|
Open `index.html` in a browser to view the compiled guideline experience.
|
|
|
|
## Recommended Use
|
|
|
|
Refer to this guide when:
|
|
|
|
- Starting a new Lupmis 2.0 feature or screen
|
|
- Reviewing interface consistency across modules
|
|
- Aligning designers and developers on expected behavior
|
|
- Checking whether a UI follows established product patterns
|
|
- Evaluating usability, clarity, and accessibility concerns
|