Customizing documentation on organization variables#9
Customizing documentation on organization variables#9cjscheller wants to merge 5 commits intomainfrom
Conversation
✅ Deploy Preview for amazing-darwin-824daa ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
@cjscheller , It look like the same "problem" as getting the values from _config.yml, we can't directly use site variables in the markdown file. I hope the published value can be overrided before it is used to generate the html. I will take a look! |
|
@cjscheller Hi Carl! Thank you for your patience, I've had a busy week and weekend. I have not found a way to edit all Published flags from from _config.yml so I opened a thread on their repo. I hope to have a feedback soon and be able to help you. Is this an irritant or a blocker? |
|
@Xavbm No worries at all, has been a busy time for me as well. Thanks for following up and opening a thread. Not a blocker for me, as I have created a separate branch off of this one that hardcodes the published values where necessary. We'll wait to see what their response is. Feel free to drop a link to the thread here so we can track it. Thanks! |
Adds support for creating documentation site for other organizations via variables defined in
_config.yml.@Xavbm Thanks for helping me get this far. Running into one more issues that I'm hoping you can help me with:
published(based on the Jekyll docs). However, I am not able to tell if A) the configuration variable is even being rendered correctly in this Front Matter and B) if the string is correctly parsed as a boolean to setpublishedas needed. Here's an example. Any thoughts?