Windwalker
Windwalker

Reputation: 1945

Working with Semantic UI's Stub Files

I am currently starting development based on Semantic UI. In Semantic UI's Customization Guide, the use of the empty Stub Files, contained in the delivery.

As kind of a "proof of concept" for me, I try to modify some variables of the Button-Element.

If I understand the principle of customizing correctly, I shall customize all these variable within these stub files. So I edit /site/elements/button.variables to

@defaultBorderRadius: 3rem;

which leads to more rounded button corners.

Also I am able to define this definition within /themes/default/globals/site.variables, yielding the same effect. But this is no stub file.

If I now try to implement this definition in /site/globals/site.variables, this effect doesn't take place.

Assuming this is no bug in Semantic UI, I think I must have misunderstood the theming concept.

Can someone clarify that for me?

Thanks in advance, Sascha.

Upvotes: 0

Views: 189

Answers (1)

Windwalker
Windwalker

Reputation: 1945

I found out the root of problem:

Since I am working according Semantic UI's build guidelines (learnsemantic.com/guide/expert.html#gulp-commands), I am running the Watch task in the background.

If changing /site/globals/site.variables, gulp watch apparently doesn't recompile button.css. To get this file compiled anew, I need to do some change in button.less, in order to notify Semantic UI to rebuild the Button element.

Upvotes: 1

Related Questions