UXUI-78 - Adding styling for inputs

[jodiedoubleday]

What does this PR do? (please provide any background)

• We have a few PR's in now to add or use input into the toolkit. These have been created but don't look particularly great.

What tests does this PR have?

None

How can be this tested?

• Run the UI toolkit
• grunt docs is your best bet, edit the HTML in dev tools and add an input to the page <input type="text" /> for example
• check ho it looks - not great
• add class="component-input" to the input
  It should no look good.

Screenshots / Screencast

What gif best describes how you feel about this work?

(it makes me sad that a lot of HX developers wont understand this GIF)

Developer Definition of Done/Quality Checklist (for PR author to complete BEFORE code review):

• I have checked the contributing document and I'm happy for this to be reviewed.

Software Engineer or Developer review:

• I’ve witnessed the work behaving as expected (this could be on the authors machine or screencast).
• I’ve checked for coding anti-patterns.
• I’ve checked for appropriate test coverage.
• I’ve run all the tests locally and they pass.

Software Engineer or project guru review:

• I’ve witnessed the work behaving as expected (this could be on the authors machine or screencast).
• I’ve checked for coding anti-patterns.
• I’ve checked for appropriate test coverage.
• I’ve run all the tests locally and they pass.

[robhuzzey]

Taking SE/DEV

[robhuzzey]

Looking at this at first glance, it looked like quite a few files were changed but they are actually auto generated (dist/ui-toolkit.standalone.js as an example).

I've reviewed the less files but I'd suggest removing the auto-generated files from the repo, stick them on .gitignore as they are not really part of the codebase.

[robhuzzey]

+1 from me

[jackdclark]

Yes sir 👍