Jaishree2310/GlassyUI-Components

[FEATURE] <description>Correct Order of new components

Open

#232 opened on Oct 17, 2024

View on GitHub
 (4 comments) (0 reactions) (1 assignee)TypeScript (217 forks)auto 404
Hacktoberfestenhancementgssoc-exthelp wantedlevel3

Repository metrics

Stars
 (114 stars)
PR merge metrics
 (PR metrics pending)

Description

Is this a unique feature?

  • I have checked "open" AND "closed" issues and this is not a duplicate

Is your feature request related to a problem/unavailable functionality? Please describe.

Basic Usage Props Customizable option Theme ex: check Button theme

Proposed Solution

Don't create a component and copy-paste code use the order to follow for making new components.

Screenshots

No response

Do you want to work on this issue?

No

If "yes" to above, please explain how you would technically implement this (issue will not be assigned if this is skipped)

No response

Contributor guide

Research direction
Create a document describing the correct order for developing new components: Basic Usage, Props, Customizable Option, Theme. Use the Button component as a reference example.
Tech stack
typescript
Domain
documentationdeveloper experience
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80