# Editing css in Elements

**URL:** <https://forums.realmacsoftware.com/t/editing-css-in-elements/51421>\
**Category:** Elements\
**Created:** [September 30, 2025, 3:19pm UTC](https://forums.realmacsoftware.com/t/editing-css-in-elements/51421 "2025-09-30T15:19:06Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![plasticpom1](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/plasticpom1/32/28522_2.png) [@plasticpom1](https://forums.realmacsoftware.com/u/plasticpom1)\
**Post date:** [September 30, 2025, 3:19pm UTC](https://forums.realmacsoftware.com/t/editing-css-in-elements/51421/1 "2025-09-30T15:19:07Z")

</div>

Hello,

I purchased the Ascent Elements project.

There is additional css in this project eg the name of a text component states 'go to - CODE CSS ascent-linehover’.

Is it possible to change this css in Elements?

---

<div class="post-metadata">

**Author:** ![Fuellemann](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/fuellemann/32/22871_2.png) [@Fuellemann](https://forums.realmacsoftware.com/u/Fuellemann)\
**Post date:** [September 30, 2025, 3:45pm UTC](https://forums.realmacsoftware.com/t/editing-css-in-elements/51421/2 "2025-09-30T15:45:23Z")

</div>

@MultiThemes This is a question for you 🙂

---

<div class="post-metadata">

**Author:** ![MultiThemes](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/multithemes/32/25117_2.png) [@MultiThemes](https://forums.realmacsoftware.com/u/MultiThemes)\
**Post date:** [September 30, 2025, 4:24pm UTC](https://forums.realmacsoftware.com/t/editing-css-in-elements/51421/3 "2025-09-30T16:24:50Z")

</div>

Just sent an email with a temporary UPG 😎

I’m working on a **BIG upgrade,** not only for Ascent but for all projects in my store, all components with options panel, a big work, stay tuned!

 ![linehover](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/5/3/5398e5dcd5519b3f39758ebf429acd44253b1bab.jpeg)

@Fuellemann thanks a lot!

---

<div class="post-metadata">

**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\
**Post date:** [September 30, 2025, 5:44pm UTC](https://forums.realmacsoftware.com/t/editing-css-in-elements/51421/4 "2025-09-30T17:44:19Z")

</div>

@MultiThemes, users shouldn’t need to be specifying colours in css, is there any reason why you’re not using [Theme Colour here](https://docs.realmacsoftware.com/elements-docs/elements-language/component/properties.json/ui-controls/theme-color)?

There’s some more [information on component styling for developers here](https://docs.realmacsoftware.com/elements-docs/elements-language/component/component-styling) 🙂

---

<div class="post-metadata">

**Author:** ![MultiThemes](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/multithemes/32/25117_2.png) [@MultiThemes](https://forums.realmacsoftware.com/u/MultiThemes)\
**Post date:** [September 30, 2025, 7:12pm UTC](https://forums.realmacsoftware.com/t/editing-css-in-elements/51421/5 "2025-09-30T19:12:29Z")

</div>

> [@dan](#):
>
> , users shouldn’t need to be specifying colours in css,

Hi @dan This is a rare case,I can’t use the standard Tailwind color classes here because the animated element is generated with a `::before` pseudo-element, which Tailwind doesn’t support directly. That’s why I had to rely on standard HTML color values.

to change the behavior of the menu I use a simple CSS class, and I work only with a:link and on top of it I build everything with `::before`

…to make it flexible I’ve provided both a custom input field (so you can use any color you like) and a predefined list of the most common colors, including the option to add transparency.

Of course, if I find native Tailwind solutions to use ::before and ::after elements using utility classes I will use them but this is a rare case 😮

---

<div class="post-metadata">

**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\
**Post date:** [October 1, 2025, 7:00am UTC](https://forums.realmacsoftware.com/t/editing-css-in-elements/51421/6 "2025-10-01T07:00:13Z")

</div>

> [@MultiThemes](#):
>
> if I find native Tailwind solutions to use ::before and ::after elements using utility classes I will use them

Hi @MultiThemes

Tailwind does support `::before` and `::after`. You just need to use the `before:` or `after:` modifiers:

`before:bg-red-500`

And if you’d like to expose this as a control, you can combine [themeColor](https://docs.realmacsoftware.com/elements-docs/elements-language/component/properties.json/ui-controls/theme-color) with the format property. For example:

```auto
{
  "title": "Background",
  "id": "beforeBgColor",
  "format": "before:bg-{{value}}",
  "themeColor": {
    "default": {
      "name": "red",
      "brightness": 500
    }
  }
},

```

* * *

That said, I’m not sure how you’re building your menu effect, but I’d be cautious about relying on the current HTML structure or class names of the Menu component. If those change in the future, your code could break and that’s bad for everyone involved.

I’d really encourage finding solutions that don’t depend on internal implementation details. Think of those class names and structures as an “internal API”, they might change at any time.

If you ever need help when building something custom, please drop us a message and we’ll be happy to help you find a more robust approach 🙂

---

<div class="post-metadata">

**Author:** ![MultiThemes](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/multithemes/32/25117_2.png) [@MultiThemes](https://forums.realmacsoftware.com/u/MultiThemes)\
**Post date:** [October 1, 2025, 11:39am UTC](https://forums.realmacsoftware.com/t/editing-css-in-elements/51421/7 "2025-10-01T11:39:06Z")

</div>

I’m working on 6 complete components (with standard colors) , and the only panel I’ve shown is the one with HTML color 🙂  
Thank @ben , I’ll definitely check it out!
