search

UF-Carpentry / Coordination

Documentation and material for instructors and organizers
5 stars 3 forks source link

UF Carpentry web page #10

Closed picardis closed 6 years ago

picardis commented 6 years ago

I propose that we set up a public web page to list upcoming workshops at UF, to use as a go-to reference that allows people to keep themselves updated about what is being offered. If we refer to that link every time we advertise a specific workshop, it should consolidate and more and more people hopefully will use it to check on future events. That would provide an advertising tool to use consistently in addition to the current "local" advertising on the web pages of specific venues. Thoughts? Any opinions on whether that should come in the context of a UF Carpentries Club web page?

ha0ye commented 6 years ago

A landing page at uf-carpentry.github.io sounds like a great idea!

@justinmillar has a blogdown site set up for the R-gators group. I don't know if he has info on how many people use it or primarily rely on the email list (and facebook group?).

@mjcollin, are there questions on the pre-workshop surveys about how people heard about the workshop and how they would prefer to hear about future workshops? It will be biased towards attendees, but might be useful about which dissemination methods are more effective.

mjcollin commented 6 years ago

Does this site meet your needs or do you feel this should be at a URL that is more compact? I went with the wiki for a github repo since it's the easiest to edit and maintain for everyone. If you want a more marque site, I'd serve it under a custom domain (ufcarpentry.org?) and make it just a few pictures and a link to the wiki.

https://github.com/UF-Carpentry/Coordination/wiki

and Simona:

https://github.com/UF-Carpentry/Coordination/wiki/Upcoming

justinmillar commented 6 years ago

I agree, this is a great idea and definitely something we should put together. I had envisioned this to be a component of the r-gators site (and still do), but currently the primary purpose of that site is to distribute code and presentation materials, and to act as a repository. I think the email list is the primary advertising vehicle for that group, but that is probably a function of not promoting and supporting the site enough.

picardis commented 6 years ago

I had not thought about the github upcoming page! I keep thinking of github as a space for people involved and not to target participants. If you guys think that in addition to that it would be useful to have a simple webpage under a custom domain I can help with that, otherwise I'll use the github upcoming for future reference.

ha0ye commented 6 years ago

My opinion is that the GitHub wiki is a good working platform for us, but has too much visual noise to function well as a public-facing announcements page. I suspect something more official-looking will also help us in reaching out to parts of the UF community that are less familiar with Carpentries, too.

Discuss at upcoming board meeting?

mjcollin commented 6 years ago

Decided at board meeting that we need a public web site, the github wiki is not accessible to many people.

Appoint a web site committee to look at whether to have the two have the same content and be automatically generated from each other and how. (netlify, jekly, etc.)

Still need to keep github for our internal use.

Simona suggests a list of links to all the stuff. Punam is frustrated by the many groups and advertisement paths on campus, can we help tie them together through UFII or another site?

ha0ye commented 6 years ago

Task List

mjcollin commented 6 years ago

I registered uf-carpentry.org and ufcarpentry.org

Cactusolo commented 6 years ago

Thanks Matt! Always thinking ahead of time!

Miao

On Mar 19, 2018, at 23:00, Matthew J Collins notifications@github.com wrote:

I registered uf-carpentry.org and ufcarpentry.org

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/UF-Carpentry/Coordination/issues/10#issuecomment-374456425, or mute the thread https://github.com/notifications/unsubscribe-auth/AHczAIzotRCnxCsZXYcXMLF5BWA80KoCks5tgHDWgaJpZM4ShF88.

ha0ye commented 6 years ago

@justinmillar, I populated some info about the website. Do you have a preference for jekyll or hugo?

I have a bit more experience coding for jekyll, and I don't think we need most of the blogdown features, though this can change if @mjcollin wants an auto-updating graph on attendance numbers over time.

mjcollin commented 6 years ago

Right now the graphs just link to the raw URL for files committed to the coordination repo. You can just copy the URL in whatever system you chose and they'll stay current as I re-run code and commit new jpgs. EG:

https://github.com/UF-Carpentry/Coordination/raw/master/graphs/cumulative_part.png
ha0ye commented 6 years ago

Yeah, I think that's the way to go since I think blogdown only re-renders when changes are made to the Rmarkdown, not to the underlying data. (I got some wires crossed with the automated forecasting setup in our lab.)

justinmillar commented 6 years ago

@ha0ye I don't have a preference either way, I don't really have any experience with Jekyll but I'm happy to learn from the sites you and @mjcollin have put together.

If you host a blogdown site through Netlify it will reconstruct the website anytime something is pushed to the designated branch on the GitHub repository, so it doesn't just have to be changes to the RMarkdown files. Jekyll sites can also be hosted through Netlify, so I think either way can have an automatically updating website.

Cactusolo commented 6 years ago

Yeah, as long as it's an automatically updating website. So people only need to update one thread, and the rest will be refreshed by itself.

Miao

2018-03-22 13:36 GMT-04:00 Justin Millar notifications@github.com:

@ha0ye https://github.com/ha0ye I don't have a preference either way, I don't really have any experience with Jekyll but I'm happy to learn from the sites you and @mjcollin https://github.com/mjcollin have put together.

If you host a blogdown site through Netlify it will reconstruct the website anytime something is pushed to the designated branch on the GitHub repository, so it doesn't just have to be changes to the RMarkdown files. Jekyll sites can also be hosted through Netlify, so I think either way can have an automatically updating website.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/UF-Carpentry/Coordination/issues/10#issuecomment-375394177, or mute the thread https://github.com/notifications/unsubscribe-auth/AHczAH7MF8dPl0bRsQAMjd-1nWT6WS3aks5tg-EigaJpZM4ShF88 .

-- Dr. Miao Sun Tel: 352 (284) 0928 Email: cactus@ufl.edu Solti Lab, Florida Museum of Natural History, University of Florida Dickinson Hall, 1659 Museum Rd, PO. Box 117800, Gainesville, FL 32611-7800, USA.

ha0ye commented 6 years ago

@justinmillar and @ha0ye will coordinate a meeting time for next week (week of April 16) to discuss.

ha0ye commented 6 years ago

Ok, we have a barebones skeleton up at https://github.com/uf-carpentry/website. I'm going to close this issue and ask that all website related issues be added to that repo.