@patternfly/patternfly 5.1.0-prerelease.26 → 5.1.0-prerelease.27
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md
CHANGED
|
@@ -63,19 +63,19 @@ When making visual changes to a full page example, new example preview screensho
|
|
|
63
63
|
|
|
64
64
|
## Guidelines for CSS development
|
|
65
65
|
|
|
66
|
-
- For issues created in Core that will affect a component in PF-React, a follow up issue must be created in PF-React once the Pull Request is merged. The issue should include the Core PR #, the Core Release, a link to the component in https://
|
|
66
|
+
- For issues created in Core that will affect a component in PF-React, a follow up issue must be created in PF-React once the Pull Request is merged. The issue should include the Core PR #, the Core Release, a link to the component in https://core-staging.patternfly.org, and information detailing the change.
|
|
67
67
|
- If global variables are modified in Core, a React issue should be opened to address this.
|
|
68
68
|
- CSS developers should ensure that animation is well documented and communicated to the respective React developer.
|
|
69
69
|
- Once the component/enhancement is complete it should receive sign off from a visual designer who can then update the master sketch file with any changes.
|
|
70
70
|
|
|
71
71
|
### Handlebars guidelines
|
|
72
|
-
[For information on how to contribute, refer to our guidelines.](/contribution)
|
|
72
|
+
[For information on how to contribute, refer to our guidelines.](https://core-staging.patternfly.org/contribution)
|
|
73
73
|
|
|
74
74
|
### CSS/Sass guidelines
|
|
75
|
-
[For more information on using CSS and Sass, refer to our guidelines.](/guidelines)
|
|
75
|
+
[For more information on using CSS and Sass, refer to our guidelines.](https://core-staging.patternfly.org/guidelines)
|
|
76
76
|
|
|
77
77
|
### Custom icon guidelines
|
|
78
|
-
[For more information on custom icons, refer to our guidelines.](/adding-custom-icons)
|
|
78
|
+
[For more information on custom icons, refer to our guidelines.](https://core-staging.patternfly.org/adding-custom-icons)
|
|
79
79
|
|
|
80
80
|
## Beta components
|
|
81
81
|
|
|
@@ -83,7 +83,7 @@ When creating a brand new component, it should be released as beta in order to g
|
|
|
83
83
|
|
|
84
84
|
## Testing for accessibility
|
|
85
85
|
|
|
86
|
-
PatternFly uses [aXe: The Accessibility Engine](https://www.deque.com/axe/) to check for accessibility violations. Our goal is to meet WCAG 2.0 AA requirements, as noted in our [Accessibility guide](https://
|
|
86
|
+
PatternFly uses [aXe: The Accessibility Engine](https://www.deque.com/axe/) to check for accessibility violations. Our goal is to meet WCAG 2.0 AA requirements, as noted in our [Accessibility guide](https://www.patternfly.org/accessibility/patternflys-accessibility).
|
|
87
87
|
|
|
88
88
|
### How to perform an accessibility audit with aXe
|
|
89
89
|
aXe is available as either a browser extension or npm script.
|
|
@@ -112,7 +112,7 @@ If you have any suggestions about ways that we can improve how we use this tool,
|
|
|
112
112
|
## FAQ
|
|
113
113
|
|
|
114
114
|
#### CSS Variables
|
|
115
|
-
[How do I use CSS variables to customize the library?](https://
|
|
115
|
+
[How do I use CSS variables to customize the library?](https://core-staging.patternfly.org/guidelines#variables)
|
|
116
116
|
|
|
117
117
|
#### Browser support
|
|
118
118
|
PatternFly 5 is supported on the latest two major versions of the following browsers:
|
|
@@ -41,7 +41,7 @@ cssPrefix: pf-v5-c-code-editor
|
|
|
41
41
|
</div>
|
|
42
42
|
</div>
|
|
43
43
|
<div class="pf-v5-c-code-editor__main">
|
|
44
|
-
<code class="pf-v5-c-code-editor__code">
|
|
44
|
+
<code dir="ltr" class="pf-v5-c-code-editor__code">
|
|
45
45
|
<pre class="pf-v5-c-code-editor__code-pre">
|
|
46
46
|
code goes here
|
|
47
47
|
</pre>
|
|
@@ -89,7 +89,7 @@ cssPrefix: pf-v5-c-code-editor
|
|
|
89
89
|
</div>
|
|
90
90
|
</div>
|
|
91
91
|
<div class="pf-v5-c-code-editor__main">
|
|
92
|
-
<code class="pf-v5-c-code-editor__code">
|
|
92
|
+
<code dir="ltr" class="pf-v5-c-code-editor__code">
|
|
93
93
|
<pre class="pf-v5-c-code-editor__code-pre">
|
|
94
94
|
code goes here
|
|
95
95
|
</pre>
|
|
@@ -238,7 +238,7 @@ cssPrefix: pf-v5-c-code-editor
|
|
|
238
238
|
</div>
|
|
239
239
|
</div>
|
|
240
240
|
<div class="pf-v5-c-code-editor__main">
|
|
241
|
-
<code class="pf-v5-c-code-editor__code">
|
|
241
|
+
<code dir="ltr" class="pf-v5-c-code-editor__code">
|
|
242
242
|
<pre class="pf-v5-c-code-editor__code-pre">
|
|
243
243
|
code goes here
|
|
244
244
|
</pre>
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@patternfly/patternfly",
|
|
3
3
|
"description": "Assets, source, tooling, and content for PatternFly 4",
|
|
4
|
-
"version": "5.1.0-prerelease.
|
|
4
|
+
"version": "5.1.0-prerelease.27",
|
|
5
5
|
"keywords": [],
|
|
6
6
|
"license": "MIT",
|
|
7
7
|
"scripts": {
|
|
@@ -45,7 +45,7 @@
|
|
|
45
45
|
"@commitlint/config-conventional": "^17.6.7",
|
|
46
46
|
"@fortawesome/fontawesome": "^1.1.8",
|
|
47
47
|
"@octokit/rest": "^20.0.1",
|
|
48
|
-
"@patternfly/documentation-framework": "5.
|
|
48
|
+
"@patternfly/documentation-framework": "5.2.0",
|
|
49
49
|
"@patternfly/patternfly-a11y": "4.3.1",
|
|
50
50
|
"@patternfly/react-code-editor": "5.0.1",
|
|
51
51
|
"@patternfly/react-core": "5.0.1",
|