Skip to content
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

Merged
merged 20 commits into from
Jan 7, 2019
Merged

Docs/onboarding #126

merged 20 commits into from
Jan 7, 2019

Conversation

khawkins98
Copy link
Contributor

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.

@@ -0,0 +1,56 @@
<?xml version="1.0" encoding="utf-8"?>

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;

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?

Copy link
Contributor Author

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.

@sturobson sturobson merged commit 90efcbc into develop Jan 7, 2019
@sturobson sturobson deleted the docs/onboarding branch January 7, 2019 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants