Skip to content
This repository was archived by the owner on Aug 8, 2023. It is now read-only.

Commit adb5637

Browse files
committed
Fix broken links
This fixes the two links that are broken, as mentioned in issue #39
1 parent 2f7aad7 commit adb5637

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

css/css-best-practices/readme.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ We use a modified version of BEM that we call CSM (Component, Sub-component, Mod
8383
.c-component.c--modifier
8484
```
8585

86-
We cover this convention in greater detail [here](#user-content-class-naming-convention-csm).
86+
We cover this convention in greater detail [here](../class-naming-conventions#class-naming-conventions).
8787

8888

8989
## Self Documenting Selectors
@@ -114,7 +114,7 @@ This principle is talked about in depth by [Harry Roberts on csswizardy.com](htt
114114

115115
## Name Spacing
116116

117-
The first thing you'll notice when going through Customer Success's CSS is that all of our class names are prefixed (aka: name-spaced) to one of two letters: `c-` or `t-`, meaning `_component_` or `_template_` respectively. See the [below table](#class-prefix-conventions) for more details on Mobify's namespacing practices.
117+
The first thing you'll notice when going through Customer Success's CSS is that all of our class names are prefixed (aka: name-spaced) to one of two letters: `c-` or `t-`, meaning `_component_` or `_template_` respectively. See the [below table](../class-naming-conventions#class-prefix-conventions) for more details on Mobify's namespacing practices.
118118

119119
Because we work on top of our client's markup and javascript, we need to make sure our class names will never conflict with their class names. By prefixing/namespacing our classes with `c-` or `t-`, we can be assured that 99.9% of those situations are avoided.
120120

0 commit comments

Comments
 (0)