-
Notifications
You must be signed in to change notification settings - Fork 34
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
Documentation: Develop landing pages that enable the community to easily find up-to-date information on a WSSSPE topic #59
Comments
First thing that comes to mind is to use this repo, add one markdown file per topic in a directory. |
I think I was one of the people that originally suggested this topic. Whilst I think that collaboratively editing the Markdown files in GitHub is a good way of ensuring they're easy for WSSSPE contributors to edit, I think that having them in a directory in GitHub isn't a good way of publishing them to the wider community, particularly those who are coming from outside the software part of the community. So perhaps we should have an automated way of publishing them to a website? |
We could put them in a "gh-pages" branch of this repo then they'll go to a web page on github.io automagically, as per https://pages.github.com/ . Or we could use WordPress or something -- I was just trying to keep us in software-engineering land. |
GitHub webpages work for me. |
I still like to have it on GitHub. For software developers it shouldn't be Sandra Gesing http://www3.nd.edu/~sgesingOn Mon, Sep 28, 2015 at 11:32 AM, Dan Gunter [email protected]
|
The GitHub page seems like a great way to set up a nice landing page that is connected to the WSSSPE community. (Also, Jekyll is pretty easy/fun to use... it runs my personal website.) |
we (@erinmr and I) independently came up with the same idea (a jekyll site or github pages) ;) |
We could also use netlify https://www.netlify.com/ (or a competitor) |
Develop landing pages on the WSSSPE website (or elsewhere) that enable the community to easily find up-to-date information on a WSSSPE topic (e.g., software credit, scientific software metrics, testing scientific software)
The text was updated successfully, but these errors were encountered: