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

Variables in theme.toml file vs config.toml #1082

Closed
zhe opened this issue Apr 28, 2015 · 4 comments
Closed

Variables in theme.toml file vs config.toml #1082

zhe opened this issue Apr 28, 2015 · 4 comments
Labels

Comments

@zhe
Copy link

zhe commented Apr 28, 2015

Hi everybody,

I'm currently make a theme for Hugo. I want to access some custom variables in the template, the way to do that is to write those variables in params in config.toml file rather that in theme.toml file. The scenario for sharing a theme is to download a theme into the themes folder and enable it by hugo -t themename or add it in config.toml. How about those custom variables with the theme? Do we need to add thoese into the config.toml file too? OR just modify the values inside the theme.toml file.

I saw several theme.toml samples from existing themes. For example, some writes:

auther = "John Doe"
source_repo = "http://..."

some other writes:

[author]
    name = "John Doe"
    homepage = "http://..."

It would be better to access the variables inside the theme.toml file in the template files, after all some custom variables are bundled with their particular theme.

@bep
Copy link
Member

bep commented Apr 28, 2015

theme.toml is currently only used for building the Hugo themes site (which isn't up and running) ... but maybe its use should be expanded.

@zhe
Copy link
Author

zhe commented Apr 30, 2015

thanks @bep! I see now.

Another questions is when the Params variable's value is changed, the page won't livereload to reflect the changes. Is that because the config.toml is loaded once when run hugo server -w? For now we need to Ctrl+C stop the server, and run it again..

@bep
Copy link
Member

bep commented Apr 30, 2015

Yes - config.toml isn't watched. Adding it to watch would be possible, I guess -- but harder than to be worth it, me thinks. If you want params/data that is livereloaded, put it in toml/yaml/json files in /data.

@bep bep closed this as completed Jul 25, 2015
bep added a commit that referenced this issue Jun 16, 2020
ac2c4a487 Update documentation for Ugly URLs (#1082)
88bdec17a Change 072.0 to 0.72.0 in release post's description
2aa7d7818 Update rss.md (#1104)
c80677aeb Update quick-start.md (#1076)
d04196bbd Minor spelling and capitalization fixes
837d2feba Fixed spelling mistake
67dc78e12 Update installing.md
ce280c5d6 Update relurl.md
bb4d0e703 Capitalization and Redirecting URL fixes
e1fecada0 Update partials.md
1d99bb182 Typos and whitespacing issues fixed
b20dba125 actually fix index function link this time
f47d6f1e3 Fixing typos, whitespace issues and links
dc82309b9 fix link to the index function
1eab0cbea add missing word (#1130)
9c3ee62ae more fixes
e9bc5880a whitespace, typos and HTTPS fixes
93b806493 Add missing word to Module section
80ced9062 Display image on page bundles page.
727029b0a Update index.md
51fc48e4d Release 0.72.0
1ff68ac3b releaser: Add release notes to /docs for release of 0.72.0
f74a25b92 common/maps: Add Scratch.Values
2fd83db96 Add redirect support to the server
bdfccf9f4 Fix typo in install instructions
e12737ea6 Create SUPPORT.md

git-subtree-dir: docs
git-subtree-split: ac2c4a4871e90ddfb180f23704ce7ec9023529ca
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants