Replace all agnostic with agnosticui for consistency

AgnosticUI · Sep 16, 2020 · 57a62a9 · 57a62a9
1 parent ef56b3a
commit 57a62a9
Show file tree

Hide file tree

Showing 29 changed files with 1,644 additions and 1,459 deletions.
diff --git a/README.md b/README.md
@@ -71,11 +71,11 @@ If you open devtools and click between the two, you'll notice that the css custo
 
 ```css
 :root {
-  --agnostic-btn-bgcolor: hotpink;
+  --agnosticui-btn-bgcolor: hotpink;
 }
 ```
 
-So, if you were to place this in your application's top-level stylesheet, it would "override" AgnosticUI's fallback default: `--agnostic-default-btn-bgcolor`, and your default buttons would have a background of hotpink. Note, the only difference between the fallback and override variable names is the `-default-` part. That's the naming convention for all css custom properties in the framework.
+So, if you were to place this in your application's top-level stylesheet, it would "override" AgnosticUI's fallback default: `--agnosticui-default-btn-bgcolor`, and your default buttons would have a background of hotpink. Note, the only difference between the fallback and override variable names is the `-default-` part. That's the naming convention for all css custom properties in the framework.
 
 ### Frameworks
 

diff --git a/agnosticui-css/button-group.css b/agnosticui-css/button-group.css
@@ -9,8 +9,8 @@
 
 .btn-group > button {
   border-radius: var(
-    --agnostic-btn-radius,
-    var(--agnostic-default-btn-radius)
+    --agnosticui-btn-radius,
+    var(--agnosticui-default-btn-radius)
   );
 }
 .btn-group > button:not(:last-child) {