You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 27, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: apps/docs/README.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,13 @@ The documentation requires a specific style guide for consistency purposes. You
6
6
2. Lines should never contain ending periods
7
7
3. All components should have a description directly after the first top-level h1. You should always use `>` for these top level descriptions
8
8
4. Code _examples_ -- ie those that use code highlighting, should never contain a wrapper div, card, or other element. The _only_ exception is #5
9
-
5. Code examples should always contain a `<template>` if they require a `<script>` tag.
10
-
6.`<script>` tags should always be `<script setup lang="ts">` in that exact format
11
-
7. Rendered Vue code must be directly _before_ the code example from above. This code example must always be wrapped in a `<BCard>`
9
+
5. Code examples should always contain a `template` if they require a `script` tag.
10
+
6.`script` tags should always be `<script setup lang="ts">` in that exact format
11
+
7. Rendered Vue code must be directly _before_ the code example from above. This code example must always be wrapped in a `BCard`
12
12
8. Use PascalCase for components. In Vue code or example code
13
13
9. Headers should be APA Title Case <https://capitalizemytitle.com/style/APA/>
14
14
10. Props should always be kebab case, ex modelValue => model-value
15
15
11. Unordered lists should always use `-`, not any alternative (ie never `*`, `+`)
16
-
12. There should not be excess lines in markdown files. Either in `<script>` tags, or between elements in examples. This may affect readability, but assuming you've followed the Vue eslint rulings (read below), then it should be fine
16
+
12. There should not be excess lines in markdown files. Either in `script` tags, or between elements in examples. This may affect readability, but assuming you have followed the Vue eslint rulings (read below), then it should be fine
17
17
18
18
It is recommended to put Vue code that is md into a real Vue file first, let it auto lint so we keep regular styling of Vue examples
Copy file name to clipboardExpand all lines: apps/docs/src/docs/components/accordion.md
+14-14Lines changed: 14 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -10,13 +10,13 @@
10
10
11
11
<divclass="lead mb-5">
12
12
13
-
Build vertically collapsing accordions in combination with `<BCollapse>` component.
13
+
Build vertically collapsing accordions in combination with `BCollapse` component.
14
14
15
15
</div>
16
16
17
17
## How it works
18
18
19
-
The `<BAccordionItem>` uses the `<BCollapse>` component internally to make it collapsible. To render an accordion that’s expanded, add the `visible` property on the `<BAccordionItem>` component.
19
+
The `BAccordionItem` uses the `BCollapse` component internally to make it collapsible. To render an accordion that’s expanded, add the `visible` property on the `BAccordionItem` component.
<strong>This is the first item's accordion body.</strong> It is shown by default, until the collapse plugin adds the appropriate classes that we use to style each element. These classes control the overall appearance, as well as the showing and hiding via CSS transitions. You can modify any of this with custom CSS or overriding our default variables. It's also worth noting that just about any HTML can go within the <code>.accordion-body</code>, though the transition does limit overflow.
34
+
<strong>This is the first item's accordion body.</strong> It is shown by default, until the collapse plugin adds the appropriate classes that we use to style each element. These classes control the overall appearance, as well as the showing and hiding via CSS transitions. You can modify any of this with custom CSS or overriding our default variables. It is also worth noting that just about any HTML can go within the <code>.accordion-body</code>, though the transition does limit overflow.
35
35
</BAccordionItem>
36
36
<BAccordionItem title="Accordion Item #2">
37
-
<strong>This is the second item's accordion body.</strong> It is hidden by default, until the collapse plugin adds the appropriate classes that we use to style each element. These classes control the overall appearance, as well as the showing and hiding via CSS transitions. You can modify any of this with custom CSS or overriding our default variables. It's also worth noting that just about any HTML can go within the <code>.accordion-body</code>, though the transition does limit overflow.
37
+
<strong>This is the second item's accordion body.</strong> It is hidden by default, until the collapse plugin adds the appropriate classes that we use to style each element. These classes control the overall appearance, as well as the showing and hiding via CSS transitions. You can modify any of this with custom CSS or overriding our default variables. It is also worth noting that just about any HTML can go within the <code>.accordion-body</code>, though the transition does limit overflow.
38
38
</BAccordionItem>
39
39
<BAccordionItem title="Accordion Item #3">
40
-
<strong>This is the third item's accordion body.</strong> It is hidden by default, until the collapse plugin adds the appropriate classes that we use to style each element. These classes control the overall appearance, as well as the showing and hiding via CSS transitions. You can modify any of this with custom CSS or overriding our default variables. It's also worth noting that just about any HTML can go within the <code>.accordion-body</code>, though the transition does limit overflow.
40
+
<strong>This is the third item's accordion body.</strong> It is hidden by default, until the collapse plugin adds the appropriate classes that we use to style each element. These classes control the overall appearance, as well as the showing and hiding via CSS transitions. You can modify any of this with custom CSS or overriding our default variables. It is also worth noting that just about any HTML can go within the <code>.accordion-body</code>, though the transition does limit overflow.
41
41
</BAccordionItem>
42
42
</BAccordion>
43
43
<template #html>
@@ -48,23 +48,23 @@ Click the accordions below to expand/collapse the accordion content.
48
48
<strong>This is the first item's accordion body.</strong> It is shown by default, until the
49
49
collapse plugin adds the appropriate classes that we use to style each element. These classes
50
50
control the overall appearance, as well as the showing and hiding via CSS transitions. You can
51
-
modify any of this with custom CSS or overriding our default variables. It's also worth noting
51
+
modify any of this with custom CSS or overriding our default variables. It is also worth noting
52
52
that just about any HTML can go within the <code>.accordion-body</code>, though the transition
53
53
does limit overflow.
54
54
</BAccordionItem>
55
55
<BAccordionItem title="Accordion Item #2">
56
56
<strong>This is the second item's accordion body.</strong> It is hidden by default, until the
57
57
collapse plugin adds the appropriate classes that we use to style each element. These classes
58
58
control the overall appearance, as well as the showing and hiding via CSS transitions. You can
59
-
modify any of this with custom CSS or overriding our default variables. It's also worth noting
59
+
modify any of this with custom CSS or overriding our default variables. It is also worth noting
60
60
that just about any HTML can go within the <code>.accordion-body</code>, though the transition
61
61
does limit overflow.
62
62
</BAccordionItem>
63
63
<BAccordionItem title="Accordion Item #3">
64
64
<strong>This is the third item's accordion body.</strong> It is hidden by default, until the
65
65
collapse plugin adds the appropriate classes that we use to style each element. These classes
66
66
control the overall appearance, as well as the showing and hiding via CSS transitions. You can
67
-
modify any of this with custom CSS or overriding our default variables. It's also worth noting
67
+
modify any of this with custom CSS or overriding our default variables. It is also worth noting
68
68
that just about any HTML can go within the <code>.accordion-body</code>, though the transition
69
69
does limit overflow.
70
70
</BAccordionItem>
@@ -122,13 +122,13 @@ Add `free` property to make accordion items stay open when another item is opene
122
122
<HighlightCard>
123
123
<BAccordionfree>
124
124
<BAccordionItem title="Accordion Item #1">
125
-
<strong>This is the first item's accordion body.</strong> It is shown by default, until the collapse plugin adds the appropriate classes that we use to style each element. These classes control the overall appearance, as well as the showing and hiding via CSS transitions. You can modify any of this with custom CSS or overriding our default variables. It's also worth noting that just about any HTML can go within the <code>default</code> slot, though the transition does limit overflow.
125
+
<strong>This is the first item's accordion body.</strong> It is shown by default, until the collapse plugin adds the appropriate classes that we use to style each element. These classes control the overall appearance, as well as the showing and hiding via CSS transitions. You can modify any of this with custom CSS or overriding our default variables. It is also worth noting that just about any HTML can go within the <code>default</code> slot, though the transition does limit overflow.
126
126
</BAccordionItem>
127
127
<BAccordionItem title="Accordion Item #2">
128
-
<strong>This is the second item's accordion body.</strong> It is hidden by default, until the collapse plugin adds the appropriate classes that we use to style each element. These classes control the overall appearance, as well as the showing and hiding via CSS transitions. You can modify any of this with custom CSS or overriding our default variables. It's also worth noting that just about any HTML can go within the <code>default</code> slot, though the transition does limit overflow.
128
+
<strong>This is the second item's accordion body.</strong> It is hidden by default, until the collapse plugin adds the appropriate classes that we use to style each element. These classes control the overall appearance, as well as the showing and hiding via CSS transitions. You can modify any of this with custom CSS or overriding our default variables. It is also worth noting that just about any HTML can go within the <code>default</code> slot, though the transition does limit overflow.
129
129
</BAccordionItem>
130
130
<BAccordionItem title="Accordion Item #3">
131
-
<strong>This is the third item's accordion body.</strong> It is hidden by default, until the collapse plugin adds the appropriate classes that we use to style each element. These classes control the overall appearance, as well as the showing and hiding via CSS transitions. You can modify any of this with custom CSS or overriding our default variables. It's also worth noting that just about any HTML can go within the <code>default</code> slot, though the transition does limit overflow.
131
+
<strong>This is the third item's accordion body.</strong> It is hidden by default, until the collapse plugin adds the appropriate classes that we use to style each element. These classes control the overall appearance, as well as the showing and hiding via CSS transitions. You can modify any of this with custom CSS or overriding our default variables. It is also worth noting that just about any HTML can go within the <code>default</code> slot, though the transition does limit overflow.
132
132
</BAccordionItem>
133
133
</BAccordion>
134
134
<template #html>
@@ -139,23 +139,23 @@ Add `free` property to make accordion items stay open when another item is opene
139
139
<strong>This is the first item's accordion body.</strong> It is shown by default, until the
140
140
collapse plugin adds the appropriate classes that we use to style each element. These classes
141
141
control the overall appearance, as well as the showing and hiding via CSS transitions. You can
142
-
modify any of this with custom CSS or overriding our default variables. It's also worth noting
142
+
modify any of this with custom CSS or overriding our default variables. It is also worth noting
143
143
that just about any HTML can go within the <code>default</code> slot, though the transition does
144
144
limit overflow.
145
145
</BAccordionItem>
146
146
<BAccordionItem title="Accordion Item #2">
147
147
<strong>This is the second item's accordion body.</strong> It is hidden by default, until the
148
148
collapse plugin adds the appropriate classes that we use to style each element. These classes
149
149
control the overall appearance, as well as the showing and hiding via CSS transitions. You can
150
-
modify any of this with custom CSS or overriding our default variables. It's also worth noting
150
+
modify any of this with custom CSS or overriding our default variables. It is also worth noting
151
151
that just about any HTML can go within the <code>default</code> slot, though the transition does
152
152
limit overflow.
153
153
</BAccordionItem>
154
154
<BAccordionItem title="Accordion Item #3">
155
155
<strong>This is the third item's accordion body.</strong> It is hidden by default, until the
156
156
collapse plugin adds the appropriate classes that we use to style each element. These classes
157
157
control the overall appearance, as well as the showing and hiding via CSS transitions. You can
158
-
modify any of this with custom CSS or overriding our default variables. It's also worth noting
158
+
modify any of this with custom CSS or overriding our default variables. It is also worth noting
159
159
that just about any HTML can go within the <code>default</code> slot, though the transition does
0 commit comments