Website

[ds300]

Website

[j6k4m8]

+1. Add a nice little demo and a quick-install button... it'll be lovely.

[nomirose]

I'll see what I can cook up.

[ds300]

I was going to wait until we're ready to release a beta for the chrome web store to do a proper website, but if you fancy giving it a go now that'd be neat.

Not sure if you've seen, but there's an SVG logo for jetzt in the img directory which you can use if you like. I'm not especially enthralled with it's design so if you want to make something better, please feel free.

[peteruithoven]

jetztthis.org is still available

[nomirose]

I have a website ready to PR, but I'm confused about how to PR.

We have a gh-pages branch, which seems to be a copy of master plus some additional files.

My PR includes an SVG for a new logo, some changes to the README.md, as well as updates for the HTML, and a few other things.

Where should I PR it to? Or how should I do this?

It would be neat if gh-pages was just a mirror of master or dev or whatever, so we can work on the website in the same place as the rest of the code, and only merging to gh-pages when we need to update the actual website. Thoughts?

[ds300]

ooh tricky. Well i think there are two options:

1. I could make master and gh-pages identical then submit to either
2. Submit two PRs, one to master with all the stuff that should be in master. I merge that into master and then merge master into gh-pages. Then you submit the website stuff to gh-pages.

2 sounds like too much work. I'll just do 1. It should make life simpler in the long run too. bear with me...

[ds300]

Ok it's done. PR to master.

[nomirose]

On it.