# Removing meta div from display and custom css

**URL:** <https://support.prodi.gy/t/removing-meta-div-from-display-and-custom-css/1028>\
**Category:** Uncategorized\
**Tags:** front-end, solved\
**Created:** [December 10, 2018, 7:50pm UTC](https://support.prodi.gy/t/removing-meta-div-from-display-and-custom-css/1028 "2018-12-10T19:50:54Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\
**Post date:** [December 12, 2018, 11:15am UTC](https://support.prodi.gy/t/removing-meta-div-from-display-and-custom-css/1028/6 "2018-12-12T11:15:13Z")

</div>

You can find the file in `static/index.html` in your Prodigy installation. To find the path, you can run the following command:

```bash
python -c "import prodigy; print(prodigy. __file__ )"

```

If you check out the `index.html` markup, you’ll see that it’s pretty straightforward and compact. `<div id="root"></div>` is where the app will be rendered – everything else stays intact. So if you add a `<style></style>` in the `<head>`, it will be available when you run the app.

The main downside here (and what a `"global_css"` setting would solve) is that you have to edit the static source and can’t easily add recipe-specific markup. So if one recipe needs some custom formatting and the other one doesn’t, that’s currently a bit tricky.

---

_[View the full topic](https://support.prodi.gy/t/removing-meta-div-from-display-and-custom-css/1028)._