-
Notifications
You must be signed in to change notification settings - Fork 7
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
Create A Static Website For The Project #7
Comments
I have set up a simple GitHub Pages site (basically a copy of the README) in a |
Hey, @DarthFloopy thanks for the initiative - as you said, I've added a new branch to the repository. Please raise a pull request. |
Hmm... GitHub Pages uses a |
@DarthFloopy Github by default serves the
Does that sound good? Let me know your thoughts. The aim of this PR is to help you understand gh-pages and related steps, so hosting it yourself will help. |
That sounds like it might work. My However, at this time I don't think I am ready to do a lot more work on this. Hopefully, you can do something with what I have done already. (If you need me to make a PR or do something else like that, I can certainly do that.) Let me know if there's anything else you need me to do. |
@DarthFloopy Hey, I'm thankful for you working on this issue and serving the README.md. I should have mentioned in the issue itself that we can already serve the README.md file and hence serving it should be avoided. My bad, apologies. Do you think it'll be wise to deploy your branch which does the same instead of using the default README.md serving? Maybe, if you are comfortable, we could look towards doing some changes and improvements as you get time and then merge it and redeploy. |
A static website with information about the project; examples, demos, how to set up, etc. The website would be hosted over Github pages.
Most of the information for the website can be taken from the README.md, however, the focus of the issue is creating a static website and not the actual content (which will be filled in by the maintainers).
The text was updated successfully, but these errors were encountered: