How should themes and site variables be integrated?

[oliverlloyd]

I'd really like to use these features - it's stuff like this that makes Semantic so great - but it's not clear how this should work with Meteor.

Clearly the src file needs to exist somewhere but when I tried adding it I couldn't make Semantic pick up my config changes.

If you have an idea how this should be done and could find the time to add an example that would be amazing.

[grp06]

I have the same question. Oliverlloyd, let me know if you figure it out

[grp06]

Oliverlloyd. If you go into your .meteor folder, you'll see that when you install nooitaf:semantic-ui through terminal, you don't get the same file structure as you do if you look through the files here on github. I still havent't figured it out, but maybe that will help you

[nooitaf]

Sorry for the late reply.

This should be possible in the future, but at the moment its not. You can however remove this package and add the src folder from the semanti-ui source to a client/ folder in your project. Also add the meteor less package. After that you should be able to use the config file and do your overrides in the _site folder.

I might think something like this..

client/lib/semantic-ui/{src folder contents here}

# and dont forget
meteor add less

This package will change to support theming, but meteor doesn't make it easy at the moment :
We started working at a new official version which has exactly that customising point in mind. But we wont release before its smooth enough.

[oliverlloyd]

Amazing news about the official integration - Meteor and Semantic put together properly is a formidable combination. Well done.

Note. For others trying to get this temp. workaround setup then you'll have to change the name of theme.less to theme.import.less to stop it being compiled and failing because variables are not set. Obviously, you also have to change the @import reference to this file at the bottom of theme.config to match.

Font-Awesome is also broken but should be fairly simple to patch.

[oliverlloyd]

To hack fonts to work you can just put a copy of them in the /public folder; either using the folder structure expected in the request:

/public/themes/default/assets/fonts/

or using a symbolic link.

[nooitaf]

afaik symbolic links disappear on deployment.

[williamkhshea]

+1 I look forward to official support of theming.

[williamkhshea]

I'm just wondering if there is any timeline for it?

[javoire]

+1

[maxpain]

+1

[dmalik]

FYI - Stumbled across an issue using the src folder method. Modals and other modules relying on transition were not working for me. The culprit turned out to be not using autoprefixer. The solution was to remove the less meteor package and add the lauricio:less-autoprefixer package.

[nooitaf]

Great info @dmalik, thanks for sharing :)

[MattiSG]

+1

[iSuslov]

This is unacceptable! I spend almost an hour trying to customize it. Please, put a BIG warning that you DON'T support customizing in meteor. And remove this section from documentation on atmosphere. Seriously, for what I should know that there is a folder "/site" and it is EDITABLE. But it does not work! WTF!?

[nooitaf]

@iSuslov wrong repo?