adds content

.github/CODEOWNERS

@@ -0,0 +1,5 @@
+@jcasman
+@joseph-rickert
+@hythloda
+@higgi13425
+@zabore

.github/workflows/publish.yml

@@ -0,0 +1,56 @@
+# This is a basic workflow to help you get started with Actions
+
+name: CI
+
+# Controls when the workflow will run
+on:
+  # Triggers the workflow on push or pull request events but only for the "operations" branch
+  push:
+    branches: ["operations"]
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+jobs:
+  build-deploy:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - name: Check out repository
+        uses: actions/checkout@v4
+
+      # Setup R environment
+      - name: Setup R
+        uses: r-lib/actions/setup-r@v2
+
+      - name: Install packages
+        uses: r-lib/actions/setup-r-dependencies@v2
+        with:
+          packages: |
+            any::tidyverse 
+            any::gt
+
+      - name: Install rmarkdown package
+        run: Rscript -e "install.packages('rmarkdown')"   
+
+      - name: Check rmarkdown package version
+        run: Rscript -e "packageVersion('rmarkdown')"
+
+      - name: Install rmarkdown package
+        run: Rscript -e "install.packages('lubridate')"   
+
+      - name: Check rmarkdown package version
+        run: Rscript -e "packageVersion('lubridate')"
+
+        # Setup Quarto
+      - name: Set up Quarto
+        uses: quarto-dev/quarto-actions/setup@v2
+
+      # Render and Publish
+      - name: Render and Publish
+        uses: quarto-dev/quarto-actions/publish@v2
+        with:
+          target: gh-pages
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.gitignore

@@ -0,0 +1,16 @@
+.Rproj.user
+.Rhistory
+.RData
+.Ruserdata
+
+/.quarto/
+_site
+.DS_Store
+.bundle
+.sass-cache
+node_modules
+package.json
+
+/_site/
+_site/
+.sass-cache/

Abstracts.qmd

@@ -0,0 +1,71 @@
+## Call for Abstracts
+
+We are seeking Abstracts for:
+
+-   Lightning talks (10 min, Thursday or Friday Jun2-13) Can pre-record so that you can be live on chat to answer questions
+-   Regular talks (20 min, Thursday or Friday June 12-13) Can pre-record so that you can be live on chat to answer questions
+-   Demos - (1 hour demo of an approach or a package, Wednesday June 11) Done live, preferably interactive
+-   Workshops - 2-3 hours on a topic, on Monday or Tuesday June 9-10, usually with a website and a repo, participants can choose to code along. Usually 5-10 min breaks each hour.
+-   Posters for the poster session on Wednesday June 11. Can include live (virtual) demos of an app or a package.
+
+An abstract proposal should describe a presentation of methodology, a study or project, or an example or case study relevant to one (or more) of our fields of interest, with R-based tools having a substantial role in the work.  The content of the presentation should be of interest to the R/Medicine community.
+
+[Dates to Remember]{.underline}
+
+**CFP Closes:**  Monday, April 28 at 11:59 PM EDT
+
+**CFP Notifications:**  **May 5**
+
+**Schedule Announcement:**  **May 9**
+
+**Pre-Recorded Video Submission:  June 2**
+
+**R/Medicine 2024 Conference:**  Monday, June 9  to  Friday, June 13
+
+[Important Notes]{.underline}
+
+All speakers are required to adhere to our [Code of Conduct](Attend.qmd). We also highly recommend that speakers take our online [Inclusive Speaker Orientation Course](https://training.linuxfoundation.org/linux-courses/open-source-compliance-courses/inclusive-speaker-orientation).
+
+[The Chat]{.underline}
+
+R/Medicine has a strong tradition of **active** discussion in a virtual chat **during** virtual presentations, and this discussion is much better if the presenter or a co-presenter is **active** in the chat, sharing relevant links and answering questions during the presentation. If you are planning to be a solo presenter for a talk on Thursday or Friday, plan to prerecord your talk to submit by June 3, and to attend (virtually) in person to actively participate in the chat. If you have relevant links in your presentation, put them in a document ahead of time so that you can easily drop them into the chat when appropriate. If you have a co-presenter, decide who will present and who will chat (or take turns at a natural switching point).
+
+*Panel submissions* must include the names of all participants in the initial submission in order to be considered.  The Linux Foundation does not accept submissions with all-male panels, in an effort to increase speaker diversity.
+
+*Complimentary Passes* For Speakers: One complimentary pass for the event will be provided for the accepted primary speaker and a co-speaker. For panel sessions, each panelist will receive a complimentary pass. 
+
+**Avoid** sales or marketing pitches and discussion of unlicensed or potentially closed-source technologies in your proposal. Talks of this nature are almost always rejected because they diminish the integrity of our events and are rarely well-received by conference attendees.
+
+All accepted speakers are required to submit their presentation slides (and prerecorded presentation videos) by June 2, prior to the event.
+
+Poster sessions can be a static rectangular graphic, and can include a 'share window' where you can do short demos for folks who (virtually) walk up to your poster.
+
+**Preparing to Submit Your Proposal**
+
+We do not intend to provide strict instructions on how to prepare your proposal; however, we hope you will review the following guidelines to help you prepare the best submission possible.  To get started, here are three questions you should consider before submitting your proposal:
+
+1.  What are you hoping to get from your presentation?
+
+2.  What do you expect the audience to gain from your presentation?
+
+3.  How will your presentation help better the R Medicine ecosystem?
+
+There are many ways to give a presentation about projects and technologies without focusing on company-specific efforts.
+
+Remember the questions above when writing your proposal, and think of ways to make it interesting for attendees as you share your experiences, educate the community about a method or an issue, or generate interest in a project.
+
+**First Time Submitting? Don't Feel Intimidated**
+
+Linux Foundation events are an excellent place for getting to know the community and sharing your ideas and the work you are doing.  We strongly encourage first-time speakers to submit talks for our events.  If you aren't sure about your abstract, reach out to us and we will be happy to provide advice on your proposal.
+
+**How To Give a Great Tech Talk**
+
+If your talk is accepted, we want to help you give the best presentation possible.  To do this, we have listed two videos on how to give a great tech talk:
+
+Your Perfect Tech Talk: <https://www.youtube.com/watch?v=AzVr_nsKoZs>
+
+A general MIT lecture on How to Speak: <https://www.youtube.com/watch?v=Unzc731iCUY>
+
+To submit a proposal:
+
+[Fill out this form](https://forms.gle/5hcCf1KQxuLwwp2C8)

Attend.qmd

@@ -0,0 +1,46 @@
+## Code of Conduct
+
+The R Consortium and its working groups are dedicated to providing a harassment-free experience for participants at all of our events, whether they are held in person or virtually. R Consortium events are working conferences intended for professional networking and collaboration within the open source community. They exist to encourage the open exchange of ideas and expression and require an environment that recognizes the inherent worth of every person and group. While at R Consortium events or related ancillary or social events, any participants, including members, speakers, attendees, volunteers, sponsors, exhibitors, booth staff and anyone else, should not engage in harassment in any form.
+
+This Code of Conduct may be revised at any time by The R Consortium and the terms are non-negotiable. Your registration for or attendance at any R Consortium event, whether it’s held in person or virtually, indicates your agreement to abide by this policy and its terms.
+
+### Expected Behavior
+
+All event participants, whether they are attending an in-person event or a virtual event, are expected to behave in accordance with professional standards, with both this Code of Conduct as well as their respective employer’s policies governing appropriate workplace behavior and applicable laws.
+
+### Unacceptable Behavior
+
+Harassment will not be tolerated in any form, whether in person or virtually, including, but not limited to, harassment based on sex, gender, sexual orientation, disability, physical appearance, body size, race, age, religion or any other status protected by laws in which the conference or program is being held. Harassment includes the use of abusive, offensive or degrading language, intimidation, stalking, harassing photography or recording, inappropriate physical contact, sexual imagery and unwelcome sexual advances or requests for sexual favors. Any report of harassment at one of our events, whether in person or virtual, will be addressed immediately. Participants asked to stop any harassing behavior are expected to comply immediately. Anyone who witnesses or is subjected to unacceptable behavior should notify a conference organizer at once.
+
+Exhibitors should not use sexualized images, activities, or other material in their booths and must refrain from the use of sexualized clothing, uniforms, costumes, or otherwise creating a sexualized environment. Speakers should not use sexual language, images, or any language or images that would constitute harassment as defined above in their talks.
+
+Individuals who participate (or plan to participate) in R Consortium events, whether its an in-person event or a virtual event, should conduct themselves at all times in a manner that comports with both the letter and spirit of this policy prohibiting harassment and abusive behavior, whether before, during or after the event.  This includes statements made in social media postings, on-line publications, text messages, and all other forms of electronic communication.
+
+### Consequences of Unacceptable Behavior
+
+If a participant engages in harassing behavior, whether in person or virtually, the conference organizers may take any action they deem appropriate depending on the circumstances, ranging from issuance of a warning to the offending individual to expulsion from the conference with no refund. The R Consortium reserves the right to exclude any participant found to be engaging in harassing behavior from participating in any further R Consortium events, working groups, trainings or other activities.
+
+If a participant (or individual wishing to participate in an R Consortium event, in-person and/or virtual), through postings on social media or other online publications or another form of electronic communication, engages in conduct that violates this policy, whether before, during or after a R Consortium  event, the R Consortium  may take appropriate corrective action, which could include imposing a temporary or permanent ban on an individual’s participation in future R Consortium events, events, working groups, trainings or other activities.
+
+### What To Do If You Witness or Are Subject To Unacceptable Behavior
+
+If you are being harassed, notice that someone else is being harassed, or have any other concerns relating to harassment, please contact a member of the conference staff immediately. You are also encouraged to contact abuse\@r-consortium.org.
+
+### Incident Response
+
+Our staff has taken incident response training and responds to harassment reports quickly and thoroughly. As referenced above, if a participant engages in harassing behavior, whether in-person or virtually, the conference organizers may take any action they deem appropriate, ranging from issuance of a warning to the offending individual to expulsion from the conference with no refund, depending on the circumstances. The R Consortium reserves the right to exclude any participant found to be engaging in harassing behavior from participating in any further R Consortium events, working groups, trainings or other activities.
+
+Conference staff will also provide support to victims, including, but not limited to:
+
+-   **Providing an Escort**
+
+-   **Contacting Hotel/Venue Security or Local Law Enforcement**
+
+-   **Briefing Key Event Staff For Response/Victim Assistance**
+
+-   **And otherwise assisting those experiencing harassment to ensure that they feel safe for the duration of the conference.**
+
+### Pre-Event Concerns
+
+If you are planning to attend an upcoming event, whether in-person or virtually and have concerns regarding another individual who may be present, please contact conduct\@r-consortium.org. Precautions will be taken to ensure your comfort and safety, including, but not limited to providing an escort, prepping onsite event staff, keeping victim and harasser from attending the same talks/social events and providing onsite contact cell phone numbers for immediate contact.
+

Competition.qmd

@@ -0,0 +1,3 @@
+## Competition
+
+### TBD

Contact.qmd

@@ -0,0 +1,23 @@
+## Contact the R/Medicine Team
+
+### Code of Conduct
+
+If you have general questions about the code of conduct, please write to conduct\@r-consortium.org
+
+If you are reporting abuse, please write to abuse\@r-consortium.org
+
+### The Conference
+
+If you have general questions about the conference please write to r-medicine-conf\@r-consortium.org
+
+### Sponsorships
+
+If you would like to know about sponsorship opportunities, please write to sponsorship\@r-consortium.org
+
+### Speakers
+
+If you are speaking at R/Medicine and need help or information please write to speakers\@r-consortium.org
+
+### General Queries
+
+For all other questions not covered by the topics above, please write to admin\@r-consortium.org

Events.qmd

@@ -0,0 +1,19 @@
+---
+title: "Past R/Medicine Conferences"
+listing:
+  id: events-listing
+  contents:
+    - "events-metadata.yml"
+  type: grid
+  fields: [date, title, image]
+  sort: "date desc"
+  image-height: 100%
+  template: event-listing.ejs
+page-layout: full
+title-block-banner: "#330033"
+title-block-banner-color: "white"
+title-block-style: default
+---
+
+::: {#events-listing}
+:::

Program.qmd

@@ -0,0 +1,13 @@
+---
+title: "R/Medicine Schedule"
+# author: "Rich Iannone"
+# date: "5/10/2024"
+format: 
+  html:
+    code-fold: false
+    echo: false
+---
+
+**Speakers: Please see additional instructions and deadlines in the [speaker guide](speaker_info.qmd).**
+
+### TBD

README.md

@@ -1 +1,47 @@
-# RMedicine_2025
+# RMedicine_website
+
+This is Quarto-based and updates and supersedes the website [here:](https://events.linuxfoundation.org/r-medicine/)
+
+## Contributing to this website
+
+This website is being built live, bit-by-bit by members of the R/Medicine organizing committee and other volunteer contributors. The idea is to get information about the conference up as soon as it comes in. It is unlikely that the website will not be finalized until shortly before the conference. If you follow the progress of the website you will likely see information go up initially with modest formatting and little aesthetic charm. It is our hope that subsequent contributions will produce something worth saving for next year. This is an exercise in what the Japanese call ["Kaizen"](https://kaizen.com/what-is-kaizen/) or continuous improvement.
+
+### The workflow for making contributions
+
+#### 1. Clone this website
+
+#### 2. Select the appropriate branch
+
+From your cloned (local) copy of the repository select a branch that is appropriate for your contribution. If you click on the pull-down branch button in the upper left hand corner of the first main [GitHub page](https://github.com/RConsortium/RMedicine_website) for this website you will see a number of branches.
+
+You will see that there are branches that correspond to each page listed on the tab bar at the top of the website:
+
+| Website Page    | Corresponding Branch |
+|-----------------|----------------------|
+| Home            | home                 |
+| Register        | register             |
+| Program         | program              |
+| Code of Conduct | Code_of_Conduct      |
+| Competition     | competition          |
+| Contact us      | Contact_us           |
+| Past Events     | Past_events          |
+
+Do not select the "operations" branch for anything. This is the main branch that drives the GitHub Actions code that publishes the website at https://rconsortium.github.io/RMedicine_website/.
+
+#### 3. Do a Pull Request
+
+Do a pull request from your local copy to make sure branch is in sync with the website branch
+
+#### 4. Commit your changes
+
+Make your changes locally save them and commit them. Be sure to make your commit message descriptive of the work you did.
+
+#### 5. Open a pull request
+
+If your changes are accepted they will be merged by a website administrator
+
+Note: to look at the website locally you can execute it in your terminal:
+
+```         
+quarto preview
+```