I modified the sample to have Español instead of Italiano. The Spanish overwrites the English, and selecting Espanñol from the menubar gets 404 for Contacts. I tried to make the url /contactos instead of /contatti - but the button on the home screen tries to load /es/contacts (getting 404). The Spanish text overwrites the English at /contacts.
What did I screw up? I’ve been staring at the configs for hours.
Hi, I’m not sure I understood what you did, can you explain me a lil bit better?
I renamed .it.toml, to .es.toml, it to es, and changed it → es in the configs.
@CustomDesigned See Requesting Help.
@ololiuhqui if you intend to support the theme, I suggest you add the Discussion section in your theme repo for users to ask questions there.
Hmm. The exampleSite wasn’t a repo. I could make it one and do diffs.
the example site is in a the exampleSite branch.
@ololiuhqui might be worth a note in the readme and on the exmpleSite itself
Diff from exampleSite as distributed.
Note, the exampleSite as distributed works fine - I obviously messed it up with mods.
Looking at the diff gives me the feeling I might solve it myself. As always, just interacting is so helpful. Thanks.
The header layout has range .Translations. Maybe that is the problem? Where does .Translations come from?
first: dont overload the showcase section with support questions.
second: have a look at Translations.
third show your code. will be much faster
Oh - I see you split off a new topic!
Thanks. I did look at that, and the original working exampleSite does not have that section. I assumed the .en.toml and .it.toml files took the place of [languages]. But, I can try adding that section and see if it fixes whatever I broke.
Where would I add it?
pages can be translated by filename or folder. choose one option.Multilingual mode
i really encourage you to put your site source to a repo and share. …
Problem turn out to be accidentally removing the symlink from /var/www/html/sitedir to public in hugo dir. I started over with a fresh example site, copying over changes to see when it broke. It didn’t break. 
New question: what result is expected from formspree? I will not be using formspree. Their website does not describe the API. I discovered from trial and error that the theme expects a json response. No problem - but what is the structure?
I examined the javascript a bit, and it first looks for a boolean “ok” field at the top level. Maybe that is all that is needed.
if I where you I would start with the formspree docs and something like formspree hugo at DuckDuckGo
and if you still cannot get it:
please open a new topic for your formspree issue. providing some more details see Requesting Help
I didn’t really mess with the JS part of FormSpree, I just set up the integration in html, so I don’t really know..
I found I can also just return a new HTML page. Doesn’t match the nice theme, but it says “Thanks for your submission” in black on white. I always did B&W web apps with templates, and hired a designer to make it purty.