Updated README.
This commit is contained in:
parent
a53996762f
commit
f270ca8a0d
@ -1,6 +1,6 @@
|
||||
# Source Code for [info.werefox.dev](https://info.werefox.dev)
|
||||
# Source Code for [werefox.dev](https://werefox.dev)
|
||||
|
||||
Here's all the source code for the site I host on [info.werefox.dev](https://info.werefox.dev).
|
||||
Here's all the source code for the site I host on [werefox.dev](https://werefox.dev).
|
||||
|
||||
(If the subdomain changes, I'll update the README)
|
||||
|
||||
@ -49,4 +49,4 @@ It's also likely that if you're editing data and components, you'll want to chan
|
||||
|
||||
Without writing an intro to the framework itself, I'll give a brief summary. If you take a look into the components, you'll notice that tags tend to have a *lot* of class names. Tailwindcss uses these class names to apply specific styling to elements, rather than making sets of CSS files to define styling based on classes and ids.
|
||||
|
||||
If you want to change the color palletes of things, you should look at `tailwind.config.js`. This file can define quite a few other things throughout the CSS framework, but I'll leave the investigation of that to some reading through of their documentation.
|
||||
If you want to change the color palletes of things, you should look at `tailwind.config.js`. This file can define quite a few other things throughout the CSS framework, but I'll leave the investigation of that to some reading through of their documentation.
|
||||
|
Loading…
Reference in New Issue
Block a user