lnug/website

Generated code in root of master branch

Closed this issue · 3 comments

At some point this repo was configured so that gh-pages uses the master branch (as opposed to the gh-pages branch).

At the moment we have both the source and the compiled output in the root directory of the master branch which can be confusing. Github requires that the generated markup be in the root.

When first timers want to change the sponsors page, they see sponsors.html go and change that, run the server and job done. Except that change will get overridden on the next build.

I've updated the readme to explain this but wonder if we can separate the two.

I wonder if master should just be used for the source and we have a script which pushes the generated files into a gh-pages branch.

i'm cool with that

@simonmcmanus - whats the action here?

Action is to split the generated code from the source to make it easier for newcomers.

Not something I plan to do now. Just something that needs doing and I wanted it recorded somewhere.