npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@freshworks/button

v0.19.1

Published

Button component in Nucleus

Downloads

6,305

Readme

@freshworks/button

npm version npm

ember install @freshworks/button

Buttons in Freshdesk

Buttons means operation or series of operations. Buttons are interactive components that the users can click or touch to trigger corresponding business logic.

Scenario

There are several button variants used throughout the product. They are used in pages such as articles, forms, wizards and perform actions such as saving, cancelling or sending, or call users to those actions.

Guidelines

DO’s

  1. Label button with what action it triggers.
  2. Choose appropriate button for the context.
  3. Use primary button for the primary/important action of the page.
  4. Use secondary buttons as default buttons.
  5. Use link buttons as tertiary buttons for less prominent actions.
  6. Use consistent button placement and direction for a user journey.
  7. Use button against a contrast background and have essential white space around the button.

DONT’s

  1. Avoid using too many buttons in one page.
  2. Button copy shouldn’t be too wordy.
  3. Don’t use more than one primary button in a page.
  4. Don’t use buttons instead of tabs.
  5. Don’t trigger the action without alerting the user for destructive buttons.
  6. Don’t use destructive buttons for all delete/ cancellation scenarios. More applicable for actions which involves deleting the data permanently.
  7. Don’t enable primary button before all mandatory fields are filled.