Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Website issues #147

Open
Tracked by #160
ljacqu opened this issue Aug 5, 2017 · 8 comments · May be fixed by #160
Open
Tracked by #160

Website issues #147

ljacqu opened this issue Aug 5, 2017 · 8 comments · May be fixed by #160

Comments

@ljacqu
Copy link
Contributor

ljacqu commented Aug 5, 2017

Great to see the site back up again—I'd like to report a few issues I've noticed while browsing the site.

@DTrejo
Copy link
Collaborator

DTrejo commented Aug 5, 2017

blerg :/

@ljacqu would you be open to helping with a pull request to fix these? I'm not asking you to make one right now, I'm just curious if you'd be open to helping.

@ljacqu
Copy link
Contributor Author

ljacqu commented Aug 5, 2017

Absolutely! Some of them I don't think I can help, but I can definitely contribute some. I'll open a pull request tomorrow.

@DTrejo
Copy link
Collaborator

DTrejo commented Aug 5, 2017 via email

@ljacqu
Copy link
Contributor Author

ljacqu commented Aug 6, 2017

I won't be able to submit a PR today but I've started doing some copy-editing. At a later time I'll get the website running locally and I'll try to take care of more technical stuff, such as the encoding issue. Cheers :)

@DTrejo
Copy link
Collaborator

DTrejo commented Aug 6, 2017 via email

@ljacqu
Copy link
Contributor Author

ljacqu commented Aug 10, 2017

Thanks! A pull request will follow on Sunday that will address the points in the issue description ;3
Edit: https://wtfjs.com/wtfs/2010-04-16-build-your-own-wtfjs is this still up-to-date to run the website locally?

@DTrejo
Copy link
Collaborator

DTrejo commented Aug 10, 2017 via email

@ljacqu ljacqu mentioned this issue Aug 12, 2017
@shaedrich
Copy link
Contributor

Looks like everythink except your third bullet point have been addressed in the now merged PR. Furtunately, this has been addressed in #160

@shaedrich shaedrich linked a pull request Apr 11, 2023 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants