Is your feature request related to a problem? Please describe.
NA - new feature development.

Describe the solution you'd like
The user should be able to import an alert component from the package. The alert component should enable the user to provide contextual information to their customers. The component's design should still try to keep in style with the rest of the library and neumorphic design (more info here) A common way to implement these types of components includes:

Describe alternatives you've considered
The user should be able to use Neu UI to quickly pick out alert variants to use.

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest. At a minimum the test should check whether the component successfully shows any child props.

We should have a test case covering the Input component implemented using Jest. More info on Jest can be found here.

For examples of how this is done, take a look at existing test cases in the library. An example would be the typography or button components.

This is part of epic #19.

Improvements to the readme are welcome. Any of the below would be considered a useful contribution, e.g.

• fixing typos
• improve layout
• adding additional relevant sections that improve the user or developer experience
• additional information on how people can contribute
• translations (see issue #25)

Neu UI is intended to be a stand-alone React component library that is styled to neumorphic design.

Other React libraries that try to do similar things but do not provide components with a similar style include:

• React Bootstrap
• Material UI
• Grommet
• Semantic UI

Neu UI was originally inspired by many of these libraries and attempted to provide something a little different to the already existing React component libraries on the market. Their docs are a good place to garner inspiration and an idea of what best practice may look like when improving documentation.

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest. At a minimum the test should check whether the component successfully shows any child props. If you are able to include tests for any additional functionality then that would be appreciated!

We should have a test case covering the Toggle component implemented using Jest. More info on Jest can be found here.

For examples of how this is done, take a look at existing test cases in the library. An example would be the CardHeader or Input components.

You can run your tests using npm run test or to see test coverage across the library npm run test:cov.

This is part of epic #19.

Describe the bug
The radio component does not appear correct on a mobile Android device. Have not attempted to replicate on iOS. Appears fine on desktop.

To Reproduce
Steps to reproduce the behavior:

1. Go https://neu-ui-docs.netlify.app/?path=/docs/form--input on a mobile Android device

Expected behavior
The "bullet points" should be aligned instead of out of place like they appear at the moment.

Screenshots

Smartphone (please complete the following information):

• Device: Samsung Galaxy 9+
• OS: Android 8.0.0.

Additional context
Add any other context about the problem here.

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest. At a minimum the test should check whether the component successfully shows any child props. If you are able to include tests for any additional functionality then that would be appreciated!

We should have a test case covering the FormGroup component implemented using Jest. More info on Jest can be found here.

For examples of how this is done, take a look at existing test cases in the library. An example would be the CardHeader or Input components.

You can run your tests using npm run test or to see test coverage across the library npm run test:cov.

This is part of epic #19.

Is your feature request related to a problem? Please describe.
A user should be able to import and easily create and use list components in their project.

Describe the solution you'd like
The user should be able to import list components from the package. The list component should enable the user to display ul and li items quickly and easily in their project, with a number of variants to choose from. The component's design should still try to keep in style with the rest of the library and neumorphic design (more info here) A common way to implement these types of components includes:

Describe alternatives you've considered
Alternative implementations seen used by a lot of other popular React component libraries include:

The existing toggle.js component needs to be refactored so that it uses the input[type=checkbox] element.

Describe the bug
So, it does not cause any breaking changes or anything, but there is a missing semicolon on line 14 of Button.js.
I can't even really take credit for it, my linter caught it 🤷‍♂️

But I have a PR for the fix if you want, I just was not sure if you would rather have me make a PR or just fix it yourself.

Either way just let me know here.

Thanks 😄

Rest of data excluded to save time

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest. At a minimum the test should check whether the component successfully shows any child props. If you are able to include tests for any additional functionality then that would be appreciated!

We should have a test case covering the CardBody component implemented using Jest. More info on Jest can be found here.

For examples of how this is done, take a look at existing test cases in the library. An example would be the CardHeader or Input components.

You can run your tests using npm run test or to see test coverage across the library npm run test:cov.

This is part of epic #19.

Explore how much value would there be to include Tailwind and avoid creating utility classes for the library from scratch.

Is your feature request related to a problem? Please describe.
A user should be able to import and easily create a nav bar component from the package.

Describe the solution you'd like
The user should be able to import a nav component from the package. The nav component should enable the user to create a nav, and its vertical or horizontal alignment. The style guide should include examples of how to include nav variants using other components available in the library.

The component's design should still try to keep in style with the rest of the library and neumorphic design (more info here) A common way to implement these types of components includes:

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest. At a minimum the test should check whether the component successfully shows any child props. If you are able to include tests for any additional functionality then that would be appreciated!

We should have a test case covering the ListItem component implemented using Jest. More info on Jest can be found here.

For examples of how this is done, take a look at existing test cases in the library. An example would be the CardHeader or Input components.

You can run your tests using npm run test or to see test coverage across the library npm run test:cov.

This is part of epic #19.

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest. At a minimum the test should check whether the component successfully shows any child props. If you are able to include tests for any additional functionality then that would be appreciated!

We should have a test case covering the Slider component implemented using Jest. More info on Jest can be found here.

For examples of how this is done, take a look at existing test cases in the library. An example would be the CardHeader or Input components.

You can run your tests using npm run test or to see test coverage across the library npm run test:cov.

This is part of epic #19.

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest. At a minimum the test should check whether the component successfully shows any child props. If you are able to include tests for any additional functionality then that would be appreciated!

We should have a test case covering the Check.js (Radio) component implemented using Jest. More info on Jest can be found here.

For examples of how this is done, take a look at existing test cases in the library. An example would be the CardHeader or Input components.

You can run your tests using npm run test or to see test coverage across the library npm run test:cov.

This is part of epic #19.

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest. At a minimum the test should check whether the component successfully shows any child props. If you are able to include tests for any additional functionality then that would be appreciated!

We should have a test case covering the CardSubtitle component implemented using Jest. More info on Jest can be found here.

For examples of how this is done, take a look at existing test cases in the library. An example would be the CardHeader or Input components.

You can run your tests using npm run test or to see test coverage across the library npm run test:cov.

This is part of epic #19.

Describe the bug
The downwards facing caret svg on the select component is blue. It should be black.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'https://neu-ui-docs.netlify.app/?path=/docs/form--input' and look at the select component
2. Alternatively, download the package import { Select } from 'ui-neu'
3. Use the component.

<FormGroup>
  <Label>Select</Label>
  <Select options={["egg", "milk", "bread"]}>Choose an option</Select>
</FormGroup>

Expected behavior
The caret is an inline svg. Used originally to improve cross browser compatibility of the custom select component. Might be worthwhile double-checking that this is the best way to do things.

The caret should be black. It currently appears blue.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows
• Browser: Chrome
• Version: 85.0.x

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest. At a minimum the test should check whether the component successfully shows any child props. If you are able to include tests for any additional functionality then that would be appreciated!

We should have a test case covering the CardText component implemented using Jest. More info on Jest can be found here.

For examples of how this is done, take a look at existing test cases in the library. An example would be the CardHeader or Input components.

You can run your tests using npm run test or to see test coverage across the library npm run test:cov.

This is part of epic #19.

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest. At a minimum the test should check whether the component successfully shows any child props. If you are able to include tests for any additional functionality then that would be appreciated!

We should have a test case covering the Select component implemented using Jest. More info on Jest can be found here.

For examples of how this is done, take a look at existing test cases in the library. An example would be the CardHeader or Input components.

You can run your tests using npm run test or to see test coverage across the library npm run test:cov.

This is part of epic #19.

The CircleCI pipeline is currently using a dependency called Auto to automatically update the release number when changes are pushed to master.

The dependency isn't working and is causing the pipeline to fail. We can either:

• fix the problem with the Auto dependency so that we hold onto the automatic release functionality (this is the preferred way)
• or we remove the Auto command from the CircleCI config file in root and manually update releases for the time being

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest. At a minimum the test should check whether the component successfully shows any child props.

For examples of how this is done, take a look at existing test cases in the library. An example would be the typography or button components.

Additional context
This issue is broken up into stories (or parts); if you are interested in contributing then ask to be assigned to a particular story.

Write a test case for...

a card component...

• Card component (#53)
• CardHeader component (#40)
• CardBody component (#52)
• CardTitle component (#54)
• CardSubtitle component (#55)
• CardText component (#56)
• CardImg component (#57)

a form component...

• Radio component (#63)
• Form component (#64)
• FormGroup component (#65)
• Input component (#41)
• Label component (#66)
• Select component (#67)
• Slider component (#68)
• TextArea component (#69)
• Toggle component (#70)

a list component...

• ListGroup component (#98)
• ListItem component (#99)

a nav component...

• nav component

misc components...

• Progress component (#71)
• Button component
• Typography component (#72)

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest. At a minimum the test should check whether the component successfully shows any child props. If you are able to include tests for any additional functionality then that would be appreciated!

We should have a test case covering the ListGroup component implemented using Jest. More info on Jest can be found here.

For examples of how this is done, take a look at existing test cases in the library. An example would be the CardHeader or Input components.

You can run your tests using npm run test or to see test coverage across the library npm run test:cov.

This is part of epic #19.

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest. At a minimum the test should check whether the component successfully shows any child props. If you are able to include tests for any additional functionality then that would be appreciated!

We should have a test case covering the Form component implemented using Jest. More info on Jest can be found here.

For examples of how this is done, take a look at existing test cases in the library. An example would be the CardHeader or Input components.

You can run your tests using npm run test or to see test coverage across the library npm run test:cov.

This is part of epic #19.

Describe the bug
Responsiveness of landing page needs improvements to behave better on mobile devices.

To Reproduce
Steps to reproduce the behavior:

1. Go to https://ui-neu.netlify.app/ on a mobile application or using chrome tools

Expected behavior
The button appearance is a bit cramped on mobile. The container also should have less padding on lower breakpoints to allow the content to breath a bit more.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: W10
• Browser: Chrome
• Version: 86.x

Smartphone (please complete the following information):

• Device: Samsung Galaxy 10

A lot of the work for this has already been done. All that is left is looking at implementing validation and help text to form elements.

• input
• label
• textarea
• range
• checkbox
• radio
• switch
• help text
• validation styles

Describe the bug
When cursor is hovered over button, it's not changed.

To Reproduce
hover cursor over button

Expected behavior
Cursor should be changed.

Screenshots

Desktop (please complete the following information):

• OS: Mac Os
• Chome
• Version 86.0.4240.80 (Official Build) (x86_64)

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest. At a minimum the test should check whether the component successfully shows any child props. If you are able to include tests for any additional functionality then that would be appreciated!

We should have a test case covering the Label component implemented using Jest. More info on Jest can be found here.

For examples of how this is done, take a look at existing test cases in the library. An example would be the CardHeader or Input components.

You can run your tests using npm run test or to see test coverage across the library npm run test:cov.

This is part of epic #19.

Is your feature request related to a problem? Please describe.
The CI pipeline has repeatedly been breaking for a while now. We're also not benefiting from the automated changelog, semver and publishing features that the dependency Auto should be providing.

Describe the solution you'd like
Shift the CI pipeline to GitHub Actions, integrate Auto and ensure pipeline is consistently passing.

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest. At a minimum the test should check whether the component successfully shows any child props. If you are able to include tests for any additional functionality then that would be appreciated!

We should have a test case covering the CardTitle component implemented using Jest. More info on Jest can be found here.

For examples of how this is done, take a look at existing test cases in the library. An example would be the CardHeader or Input components.

You can run your tests using npm run test or to see test coverage across the library npm run test:cov.

This is part of epic #19.

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest. At a minimum the test should check whether the component successfully shows any child props. If you are able to include tests for any additional functionality then that would be appreciated!

We should have a test case covering the CardBody component implemented using Jest. More info on Jest can be found here.

For examples of how this is done, take a look at existing test cases in the library. An example would be the CardHeader or Input components.

You can run your tests using npm run test or to see test coverage across the library npm run test:cov.

This is part of epic #19.

Is your feature request related to a problem? Please describe.
There isn't localisation options for the readme for most users.

Describe the solution you'd like
Additional translations of the README into other languages.

Current readme translations:

• English
• Vietnamese
• Brazilian Portuguese
• Greek
• Mandarin
• Polish
• Malay
• Italian
• Spanish
• German
• French
• Marathi
• Other...

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest. At a minimum the test should check whether the component successfully shows any child props.

We should have a test case covering the CardHeader component implemented using Jest. More info on Jest can be found here.

For examples of how this is done, take a look at existing test cases in the library. An example would be the typography or button components.

This is part of epic #19.

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest.

We need to improve the test coverage for the Typography component, currently implemented using Jest, to 100% coverage of the component. It currently stands at ~45%. More info on Jest can be found here (https://jestjs.io/).

For examples of how this is done, take a look at existing test cases in the library. An example would be the CardHeader or Input components.

You can run your tests using npm run test or to see test coverage across the library npm run test:cov.

This is part of epic #19.

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest. At a minimum the test should check whether the component successfully shows any child props. If you are able to include tests for any additional functionality then that would be appreciated!

We should have a test case covering the Progress component implemented using Jest. More info on Jest can be found here.

For examples of how this is done, take a look at existing test cases in the library. An example would be the CardHeader or Input components.

You can run your tests using npm run test or to see test coverage across the library npm run test:cov.

This is part of epic #19.

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest. At a minimum the test should check whether the component successfully shows any child props. If you are able to include tests for any additional functionality then that would be appreciated!

We should have a test case covering the TextArea component implemented using Jest. More info on Jest can be found here.

For examples of how this is done, take a look at existing test cases in the library. An example would be the CardHeader or Input components.

You can run your tests using npm run test or to see test coverage across the library npm run test:cov.

This is part of epic #19.

Is your feature request related to a problem? Please describe.
Test coverage across the application is low. We need to build confidence that the components have the expected behaviour that we want and to help mitigate any regression in the future.

Describe the solution you'd like
We need to implement better test coverage across the library. Ideally each component should be accompanied by a test case written using Jest. At a minimum the test should check whether the component successfully shows any child props. If you are able to include tests for any additional functionality then that would be appreciated!

We should have a test case covering the Card component implemented using Jest. More info on Jest can be found here.

For examples of how this is done, take a look at existing test cases in the library. An example would be the CardHeader or Input components.

You can run your tests using npm run test or to see test coverage across the library npm run test:cov.

This is part of epic #19.

Is your feature request related to a problem? Please describe.
NA - new feature development.

Describe the solution you'd like
The user should be able to import badge components from the package. The badge component should enable the user to provide contextual information to their customers. The component's design should still try to keep in style with the rest of the library and neumorphic design (more info here) A common way to implement these types of components includes:

Describe alternatives you've considered
The user should be able to use Neu UI to quickly pick out badge variants to use.

I've noticed that the README in english doesn't link to the already translated ones, and I think it would be a good idea to add a link to each translated README.

Btw, I would like to work on it too, since it's a really small change.