6

Is it just a matter of giving it the correct parameters to generate the output with the correct design tokens applied? You're pretty close! In order to replicate the compact display using a static CSS file, do the following: Clone and use the SLDS repo Open up design-tokens/primitive/spacing.yml Update all the VAR_* tokens (e.g. VAR_SPACING_SMALL) to your ...


3

You can create custom tokens, but you cannot reference your custom tokens directly in your lightning component. If you want to create custom token other than Default token then you need to maintain a hierarchical structure of other tokens. Default token will be the parent and all others child and sub-child and so on. To extend Tokens in the parent token use ...


3

After reading several posts and checking Using Design Tokens with the Lightning Design System, it seems that you have to embed a lightning component that uses design tokens. It doesn't look like you can use design tokens directly within a Visualforce page, if you are developing web-based applications, you can use te design tokens as variables through CSS ...


3

EDIT 12/22/2019: keep an eye on the release notes for spring '20, they're still in preview so this could change, but looks like a fix is coming. https://releasenotes.docs.salesforce.com/en-us/spring20/release-notes/rn_lwc_custom_aura_tokens.htm I suspect that it's not working yet. I noticed that in this link Lighting Web Component Custom Design Token is ...


2

No, this change does not affect tokens or anything else. Only SLDS classes, including SLDS overrides in CSS, SLDS included in literal markup, and SLDS classes in strings in JavaScript, are affected. You should continue to use design tokens as they always have been.


2

To determine which bundle you're using, you check the app: <aura:application tokens="c:bundle2"> <!-- we now have bundle1 and bundle2 styles! --> <!-- Your app markup here --> </aura:application> 1 Because once you override a token in a child token bundle, the value which is specified in parent token bundle becomes rotten ...


1

Looks like the Token which you are trying to use is not a Global Token yet that's why it's erroring out https://developer.salesforce.com/docs/component-library/documentation/en/lwc/lwc.create_components_css_design_tokens


1

In Visualforce, all you can use are included CSS files (static CSS). It is not possible to use Design Tokens in Visualforce. If you wanted to take advantage of this, you could use Lightning Out and display a Lightning Component on the page.


1

From an experiment where I have a lightning-record-form component presented in a Community it renders like this by default: and like this when the Design Tokens are edited so confirming that the Design Token support is automatic i.e. the SLDS class references can be left unchanged in the component and the changes come through:


1

Salesforce finally adding support for LWC design attributes in Spring'20


1

Salesforce recently released this react component library for SLDS. I haven't had a chance to try it out yet, but it seems to be actively being worked on.


1

I'm posting this answer as a partial answer/work-around to hopefully help others, until a better answer is provided. Primary Font Accessing the chosen "Primary Font" from Community Builder can be accomplished by using the design token in the CSS file: .THIS .myThemeSection { font-family: t(fontFamily); } Company Logo and Header Image (Requires Site....


Only top voted, non community-wiki answers of a minimum length are eligible