This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
/
stanford_basic.libraries.yml
executable file
·141 lines (137 loc) · 4.3 KB
/
stanford_basic.libraries.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
# Drupal 8 uses the SMACSS system to conceptually categorize CSS rules. Note
# that some SMACSS nomenclature has been changed to avoid confusion with
# existing Drupal terminology.
#
# Base
# Base rules consist of styling for HTML elements only, such as used in a CSS
# reset or Normalize.css. Base rules should never include class selectors.
#
# To avoid ‘undoing’ styles in components, base styles should reflect the
# simplest possible appearance of each element. For example, the simplest usage
# of the ul element may be completely unstyled, removing list markers and
# indents and relying on a component class for other applications.
#
# Layout
# Arrangement of elements on the page, including grid systems.
#
# " Grid systems should be thought of as shelves. They contain content but are
# not content in themselves. You put up your shelves then fill them with your
# stuff [i.e. components]. – Harry Roberts, CSS Guidelines "
#
# Component (SMACSS “module”)
# Reusable, discrete UI elements; components should form the bulk of
# Drupal’s CSS.
#
# State
# Styles that deal with transient changes to a component’s appearance. Often,
# these are client-side changes that occur as the user interacts with the page,
# such as hovering links or opening a modal dialog. In some cases, states are
# static for the life of the page and are set from the server, such as the
# active element in main navigation. The main ways to style state are:
# * Custom classes, often but not always applied via JavaScript. These should be
# prefixed with .is-, e.g. .is-transitioning, .is-open;
# * pseudo-classes, such as :hover and :checked;
# * HTML attributes with state semantics, such as details[open];
# * media queries: styles that alter appearance based on the immediate browser
# environment.
#
# Theme
# Purely visual styling, such as border, box-shadow, colors and backgrounds,
# font properties, etc. Ideally, these should be separated enough from a
# component’s structure to be “swappable”, and omitting these entirely should
# not break the component’s functionality or basic usability.
#
# EXAMPLE:
#
# nameoflibrarygroup:
# version: VERSION
# css:
# base:
# css/drupal/all.css:
# css/drupal/print.css: { media: print }
# layout:
# css/layout/all.css: {}
# component:
# css/components/components.css: {}
# state:
# css/state/states.css: {}
# theme:
# css/pattern-library/all.css: {}
# js:
# js/build/scripts.js: {}
# dependencies:
# - core/jquery
#
# Uncomment the code below to load scripts.js file on all pages. This file also requires JQuery to be
# loaded on all pages. Consider implimenting your scripts through theme libraries if you wish to
# avoid this. https://www.drupal.org/developing/api/8/assets
#
# js/build/scripts.js: {}
# dependencies:
# - core/drupal
# - core/jquery
#
# patternlibrary:
# version: VERSION
# css:
# base:
# css/pattern-library/base/base.css: {}
# layout:
# css/pattern-library/layout/layout.css: {}
# component:
# css/pattern-library/components/components.css: {}
# state:
# css/pattern-library/states/states.css: {}
# theme:
# css/pattern-library/theme/theme.css: {}
# css/pattern-library/theme/print.css: { media: print }
admin:
version: VERSION
css:
base:
dist/css/admin.css: { }
basic:
version: VERSION
css:
base:
dist/css/base.css: { weight: 100 }
layout:
dist/css/layout.css: {}
component:
dist/css/components.css: {}
state:
dist/css/state.css: {}
theme:
dist/css/theme.css: {}
dist/css/print.css: { media: print }
js:
dist/js/base.js: { scope: footer }
dist/js/behaviors.js: { scope: footer }
dependencies:
- classy/base
- classy/messages
- classy/progress
- core/drupal
- core/jquery
- core/once
- core/modernizr
- stanford_basic/fontawesome
search-page:
version: VERSION
css:
theme:
dist/css/search-page.css: { }
user_login:
version: VERSION
css:
base:
dist/css/user_login.css: { }
fontawesome:
version: 5.15.4
remote: https://use.fontawesome.com/releases/v5.15.4/css/all.css
license:
name: FontAwesome
url: http://fontawesome.io/license/
css:
base:
//use.fontawesome.com/releases/v5.15.4/css/all.css: {}