# Importing alternative checkboxes **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [October 9, 2024, 10:26pm UTC](https://forum.inductiveautomation.com/t/importing-alternative-checkboxes/97051 "2024-10-09T22:26:47Z")\ **Posts on this page:** 1\ **Showing post:** 9
**Author:** ![victordcq](https://avatars.discourse-cdn.com/v4/letter/v/f6c823/32.png) [@victordcq](https://forum.inductiveautomation.com/u/victordcq)\ **Post date:** [October 10, 2024, 6:59am UTC](https://forum.inductiveautomation.com/t/importing-alternative-checkboxes/97051/9 "2024-10-10T06:59:11Z")
Most of these seem possible to do with just some basic components... You will need some different css though. Mainly you will have to bascily rename all css class selectors with psc- infront I guess you could techincally create custom html too. You could put the creating of this in the injectables, than use markdwon to utilse them would be quite compact in the views itself... Though this is not a trivial thing to do. especcially to get some feedback back into perspective... Probably easier to just make a custom component where all that is already done 😛 > **[Using custom elements - Web APIs | MDN](https://developer.mozilla.org/en-US/docs/Web/API/Web_components/Using_custom_elements)** > > One of the key features of web components is the ability to create custom elements: that is, HTML elements whose behavior is defined by the web developer, that extend the set of elements available in the browser. > **[How to create a custom checkbox web component?](https://heybran.cn/blog/how-to-create-a-custom-checkbox-web-component/)** > > The \`:host\` selector in web components can be a bit tricky and confusing. However, fear not! In this post, I will cover all the different scenarios where you might use the \`:host\` selector, so you can become a pro at using it in your web components. --- _[View the full topic](https://forum.inductiveautomation.com/t/importing-alternative-checkboxes/97051)._