README should specify *extended* Hugo

[bjnath]

A user who installs Hugo by following the Getting Started link in the README will get the failure

error: failed to transform resource: TOCSS: failed to transform "style.sass"

when they run hugo server.

Users need to install the extended version, e.g.,

sudo apt-get install ./hugo_extended_0.70.0_Linux-64bit.deb

which I don't think is mentioned in the page we're linking to.

Extended Hugo is a requirement of the Hugo Fresh theme (see Troubleshooting at the bottom the page).

[rgommers]

That's right, good catch. You're not the first one to run into that @bjnath. Would you be able to open a PR to fix the README?

[bjnath]

Wasn't able to push the PR:

(doc-build-38) bjn@lynnfield:~/numpy_newsite/numpy.org$ git push origin hugo_install_readme
ERROR: Permission to numpy/numpy.org.git denied to bjnath.

[rgommers]

That's because the standard workflow is for you to "fork" this repo (button at right top of the page). You then push your changes to a new branch in your own fork, and from there you can send a PR.

The process is described at https://numpy.org/devdocs/dev/index.html#development-process-summary (just change the name of the repo from numpy to numpy.org).

[rgommers]

The rationale for that is that is we let every contributor create new branches in this repo, it would get very messy very quickly. Pretty much every open source project uses this "send PR from forks" method.

[bjnath]

I did fork:

and the step that failed was right out of https://numpy.org/devdocs/dev/index.html#development-process-summary:

[bjnath]

OK, I see -- I have origin set the same as upstream:

(doc-build-38) bjn@lynnfield:~/numpy_newsite/numpy.org$ git remote -v
origin  [email protected]:numpy/numpy.org.git (fetch)
origin  [email protected]:numpy/numpy.org.git (push)
upstream        https://github.com/numpy/numpy.org.git (fetch)
upstream        https://github.com/numpy/numpy.org.git (push)

I'll fix it and try again.

[bjnath]

All set, filed PR #241

[bjnath]

PS, @rgommers, thanks for clarifying how it works. I was following the steps but couldn't visualize what was happening.

[rgommers]

No worries, thanks for the PR!

One more tip: if you add in your commit message next time closes gh-231 or fixes gh-231, then this issue gets auto-closed when your PR is merged.

[bjnath]

Great tip, will do! Thanks.