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

Allow user to provide Liquid variables via sbt #72

Closed
tpolecat opened this issue Oct 26, 2016 · 2 comments · Fixed by #110
Closed

Allow user to provide Liquid variables via sbt #72

tpolecat opened this issue Oct 26, 2016 · 2 comments · Fixed by #110

Comments

@tpolecat
Copy link

It would be nice if I could say something like

micrositeVariables := Map(
  "version" -> version.value,
  "org"     -> organization.value
)

or something like this, and push them forward into Jekyll so that I could say {{microsite.version}} in my markdown … keeping versions correct in doc is always a problem. A good default map might include version, name, description, and org.

You may have something like this in mind already. If not maybe I can hack it up? wdyt?

@juanpedromoreno
Copy link
Member

Sounds good. Thanks!

We have to make a decision around this, Lars commented a different alternative: providing the ability to create your own jekyll configuration and put it as a resource: #43

@juanjovazquez
Copy link

This is very useful and is present in other tools like Paradox through the @var directive and the paradoxProperties setting. I'd rather not to leave SBT to configure these properties.

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 a pull request may close this issue.

3 participants