[BUG] - misleading themesdir inside exampleSite -> config.toml

[tcarreira]

Describe the bug
There should be no themesdir directive inside config.toml file (exampleSite directory)

If the line themesdir = "../.." is present on my config.toml file, I get an error

To Reproduce
1.

git submodule add -f https://github.com/mattstratton/castanet.git themes/castanet

2. copy the content from ./themes/exampleSite/config.toml to ./config.toml
3. run hugo server
4. error:

$ hugo server
Error: module "castanet" not found; either add it as a Hugo Module or store it in "/home/tcarreira".: module does not exist

Expected behavior
I was expecting to get a running website with the example provided

Desktop (please complete the following information):

• OS: Linux - Ubuntu 20.04
• Hugo version: Hugo Static Site Generator v0.74.3 linux/amd64 BuildDate: 2020-07-23T20:37:11Z

Additional context
I'm using Hugo for the first time, so I might be doing something wrong here, but after removing that line from my config.toml, everything is running.

[tcarreira]

I've created #287, but I'm still not sure if I was doing something wrong 😅

[mattstratton]

This is needed in order to run the exampleSite. You shouldn't copy that part, but the examplesite directory needs it in order to run properly for the Hugo showcase, tests, etc.

[tcarreira]

Ok, I think this would be a Creator's decision in the end.

Just for reference: https://themes.gohugo.io/hugo-clarity/#option-1-recommended
It is possible to do what you need with hugo server --themesDir ../.. and still have a completely functional exampleSite.

If you still keep that directive, I would suggest adding a note on how to install it (and copy the necessary files) as a theme in the README instructions.

And thank you for you help 😃

Hugo Clarity

A theme based on VMware's Clarity Design System for publishing technical blogs with Hugo.

[mattstratton]

Totally get that. I think also the instructions for the theme don't say to copy the config.toml, but to use it as a reference. I could make that more clear in the README however to that effect!