# Theming/branding for MFEs

**URL:** <https://discuss.openedx.org/t/theming-branding-for-mfes/7386>\
**Category:** Development\
**Created:** [June 1, 2022, 1:43pm UTC](https://discuss.openedx.org/t/theming-branding-for-mfes/7386 "2022-06-01T13:43:27Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![dcoa](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/dcoa/32/3246_2.png) [@dcoa](https://discuss.openedx.org/u/dcoa)\
**Post date:** [June 1, 2022, 2:26pm UTC](https://discuss.openedx.org/t/theming-branding-for-mfes/7386/3 "2022-06-01T14:26:49Z")

</div>

Hi, if you are working on dev mode I think is better if you use the _module.config.js_

This is explained here:

> [@MFE header override](https://discuss.openedx.org/t/mfe-header-override/5125/14):
>
> Alright! I got it to work! module.config.js contents: module.exports = { localModules: [ // This line intercepts imports for the header's stylesheet and redirects them to the `src` directory of your local checkout of the header, which is where index.scss lives. { moduleName: '@edx/frontend-component-header/dist', dir: '../frontend-component-header', dist: 'src' }, // This line catches JavaScript imports and points them at that same src directory. { moduleName: '@edx/frontend…

And you can see it here too:

> **[GitHub - openedx/frontend-build: Common build scripts and tooling for Open...](https://github.com/openedx/frontend-build#local-module-configuration-for-webpack)**
>
> Common build scripts and tooling for Open edX micro-frontends. - GitHub - openedx/frontend-build: Common build scripts and tooling for Open edX micro-frontends.

And now I only tested with aliases installing a repository like this:

```cli
npm install --save @edx/brand@<myuser>/brand-openedx

```

I hope this could help you

---

_[View the full topic](https://discuss.openedx.org/t/theming-branding-for-mfes/7386)._