| /openbmc/webui-vue/docs/.vuepress/ | 
| H A D | config.js | 36             title: "Guidelines", 38               "/guide/guidelines/colors", 39               "/guide/guidelines/internationalization", 40               "/guide/guidelines/motion", 41               "/guide/guidelines/typography"
  | 
| /openbmc/webui-vue/docs/guide/coding-standards/ | 
| H A D | accessibility.md | 3 It is important that the OpenBMC Web UI meet accessibility guidelines 5 guidelines are known as the 6 [Web Content Accessibility Guidelines (WCAG)](https://www.w3.org/WAI/standards-guidelines/wcag/). 28 [WAI-ARIA](https://www.w3.org/WAI/standards-guidelines/aria/) can help make an 37 Assuring the Web UI meets accessibility guidelines requires a combination of 69 - [Web Content Accessibility Guidelines (WCAG)](https://www.w3.org/WAI/standards-guidelines/wcag/)
  | 
| H A D | readme.md | 4 guidelines for both SCSS and JavaScript syntax. 10 The guidelines we are following are:
  | 
| /openbmc/docs/security/ | 
| H A D | obmc-github-security-advisory-template.md | 3 This has guidelines for OpenBMC repository maintainers to follow when creating 5 guidelines][]. 10 [security response team guidelines]: ./obmc-security-response-team-guidelines.md
  | 
| H A D | obmc-security-response-team.md | 12 - guidelines for security response team members 42 [Guidelines for security response team members](./obmc-security-response-team-guidelines.md)
  | 
| H A D | how-to-report-a-security-vulnerability.md | 46   response team guidelines][]. 70 [security response team guidelines]: ./obmc-security-response-team-guidelines.md
  | 
| H A D | obmc-security-response-team-guidelines.md | 1 # Security response team guidelines 3 These are the guidelines for OpenBMC security responders, including the security 45      response team. For example, link to these guidelines. 159 Some of these guidelines were collected from:
  | 
| /openbmc/webui-vue/docs/guide/ | 
| H A D | readme.md | 34 ## Guidelines  section in Getting Started 36 The [guidelines section](/guide/guidelines/colors.md) contains the OpenBMC 38 application. How to theme the application to meet company brand guidelines is
  | 
| /openbmc/webui-vue/docs/guide/guidelines/ | 
| H A D | motion.md | 3 The motion guidelines are based on Carbon Design System guidelines. These 4 guidelines avoid easing curves that are unnatural, distracting, or purely 6 …to Carbon's animation documentation](https://www.carbondesignsystem.com/guidelines/motion/basics/).
  | 
| /openbmc/webui-vue/docs/customization/ | 
| H A D | theme.md | 6 removed or updated to meet organizational brand guidelines. 72 - [Carbon Design System Motion Guidelines](https://www.carbondesignsystem.com/guidelines/motion/bas… 130 palette is supported using the Sass variables outlined in the color guidelines 169 at the [color guidelines](/guide/guidelines/colors) to better understand default 205 The updated page header can include a small logo. The guidelines for adding a 207 challenging to meet all organization brand guidelines due to the minimal height
  | 
| H A D | readme.md | 87 OpenBMC Web UI. Any color settings needed to meet company brand guidelines will 165 - [View the color palette and hex values in the color guidelines](/guide/guidelines/colors) 214 throughout the application. These guidelines from the Cabon Design System avoid 254 - [Carbon Design System motion guidelines](https://www.carbondesignsystem.com/guidelines/motion/bas… 363 removed or updated to meet organizational brand guidelines.
  | 
| /openbmc/openbmc/meta-raspberrypi/.github/ | 
| H A D | PULL_REQUEST_TEMPLATE.md | 2 Please make sure you've read and understood our contributing guidelines. 4 For additional information on the contribution guidelines:
  | 
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/microsoft-gsl/ | 
| H A D | microsoft-gsl_4.0.0.bb | 1 SUMMARY = "GSL: Guidelines Support Library" 2 DESCRIPTION = "The Guidelines Support Library (GSL) contains functions \ 3     and types that are suggested for use by the C++ Core Guidelines \
  | 
| /openbmc/docs/ | 
| H A D | SECURITY.md | 31   response team guidelines][]. 55 [security response team guidelines]: ./obmc-security-response-team-guidelines.md
  | 
| H A D | cpp-style-and-conventions.md | 9 Guidelines" that Bjarne and Herb Sutter introduced at CppCon 2015. 43 following the C++ Core Guidelines. 69 ## Global Guidelines and Practices 71 Please follow the guidelines established by the C++ Core Guidelines (CCG). 448 ### Misc Guidelines
  | 
| H A D | hw-vendor-repos-policy.md | 22 guidelines to be used by the OpenBMC TOF in their decision to approve or not 79    the [upstream][upstream] guidelines 165 project efforts. Having a set of guidelines for this process helps to speed up
  | 
| /openbmc/openbmc/meta-aspeed/ | 
| H A D | README.md | 27 Patch checklist.  Please ensure patches adhere to the following guidelines: 30    guidelines](https://www.openembedded.org/wiki/Styleguide).
  | 
| /openbmc/entity-manager/configurations/ | 
| H A D | VENDORS.md | 13 For purposes of this repository, the following prioritized guidelines are used 34 These guidelines are not meant to be exhaustive rules to cover all scenarios and
  | 
| /openbmc/openbmc/meta-openpower/ | 
| H A D | README.md | 39 Patch checklist.  Please ensure patches adhere to the following guidelines: 42    guidelines](https://www.openembedded.org/wiki/Styleguide).
  | 
| /openbmc/openbmc/meta-hpe/ | 
| H A D | README.md | 46 Patch checklist.  Please ensure that patches adhere to the following guidelines: 49    guidelines](https://www.openembedded.org/wiki/Styleguide).
  | 
| /openbmc/openbmc/meta-ibm/ | 
| H A D | README.md | 66 Patch checklist.  Please ensure patches adhere to the following guidelines: 69    guidelines](https://www.openembedded.org/wiki/Styleguide).
  | 
| /openbmc/webui-vue/ | 
| H A D | CONTRIBUTING.md | 5 The following is a set of guidelines for contributing to the OpenBMC Web UI. 22 [OpenBMC Gerrit Setup/Integration guidelines](https://github.com/openbmc/docs/blob/master/developme… 114 Agreement (FPA), describing how IBM complies with the latest GDPR guidelines.
  | 
| /openbmc/qemu/docs/interop/ | 
| H A D | dbus.rst | 97 Guidelines  chapter 101 the "D-Bus API Design Guidelines":
  | 
| /openbmc/docs/designs/ | 
| H A D | redfish-resource-supplement-for-pfr.md | 13 NIST SP 800-193 provides technical guidelines and recommendations supporting 28 guidelines to implementers, including Original Equipment Manufacturers (OEMs) 51 Resilience by using guidelines provided by NIST SP 800-193. Some of the
  | 
| /openbmc/qemu/.github/workflows/ | 
| H A D | lockdown.yml | 27             guidelines about contributing on the project website:
  |