-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs/onboarding #126
Docs/onboarding #126
Conversation
Feels like a much better ux
@@ -0,0 +1,56 @@ | |||
<?xml version="1.0" encoding="utf-8"?> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll look at some SVGO gulp plugin to avoid:
a) the need to optimise this by hand
b) further PRs with all that Adobe cruft in the SVG
const SassOutput = './public/css'; | ||
const autoprefixerOptions = { browsers: ['last 2 versions', '> 5%', 'Firefox ESR'] }; | ||
const config = JSON.parse(fs.readFileSync('./package.json')); | ||
global.vfName = config.vfConfig.vfName; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you talk me through this bit later?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep. It's more about the child theme support and thinking that maintenance would be easier when we can get VF-Core and the child theme to use as close to identical config files as possible.
A bunch of documentation tweaks to aid in the onboarding.
It also links off to the "pre-alpha" child theme, we can find/replace those as the concept evolves and we have a final name/correct URL.