Skip to content

Create detailed OSC members and staff page #39

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Gnotic
Copy link

@Gnotic Gnotic commented Jun 3, 2025

This pull request adds a draft quarto file for the more detailed members page for OSC members. Both html and css are contained within the single quarto file.

@Gnotic Gnotic requested a review from NeuroShepherd June 3, 2025 09:12
@Gnotic Gnotic changed the title Added draft OSC members page (see #35) Added draft OSC members page (see #32) Jun 3, 2025
@NeuroShepherd NeuroShepherd changed the title Added draft OSC members page (see #32) Create detailed OSC members and staff page Jun 4, 2025

<div class="member-mission">
<h2>Mission Statement</h2>
<p> I am principal investigator for Psychological Methods and Assessment at the Department of Psychology. The reproducibility of research findings is a core criterion of science, which however, has been challenged by the failure of recent large-scale replication projects. To foster open science practices, I teamed up with colleagues and established our department's "Open Science Committee" in 2015. The outcomes of this committee include an open science paragraph which we included in all recent professorship job descriptions, adding transparency criteria to the department's performance-based funding system, or introducing modules on preregistrations, open data, and reproducible scripts as mandatory components in undergraduate courses.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Self: add markdown=1 to allow in-tag markdown formatting

```{=html}
<style>

.member-profile {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Self: move css here to a separate members.css file, and then import that into the general styles.css file

Comment on lines +285 to +302
<div class="member-socials">
<a href="https://bsky.app/profile/lmu-osc.bsky.social" title="Bluesky" target="_blank" class="social-link">
<i class="bi bi-bluesky"></i>
</a>

<a href="https://www.linkedin.com/in/felixschoenbrodt" title="LinkedIn" target="_blank" class="social-link">
<i class="bi bi-linkedin"></i>
</a>

<a href="https://github.com/nicebread" title="GitHub" target="_blank" class="social-link">
<i class="bi bi-github"></i>
</a>

<a href="https://orcid.org/0000-0002-8282-3910" title="Orchid" target="_blank" class="social-link">
<i class="bi bi-flower1"></i>
</a>

</div>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generalize the socials to a loop which can look roughly like this:

---
title: "Profile Page"
format: html
params:
  socialLinks:
    - href: "https://bsky.app/profile/lmu-osc.bsky.social"
      title: "Bluesky"
      iconClass: "bi bi-bluesky"
    - href: "https://www.linkedin.com/in/felixschoenbrodt"
      title: "LinkedIn"
      iconClass: "bi bi-linkedin"
    - href: "https://github.com/nicebread"
      title: "GitHub"
      iconClass: "bi bi-github"
    - href: "https://orcid.org/0000-0002-8282-3910"
      title: "Orchid"
      iconClass: "bi bi-flower1"
---
<div class="member-socials" id="socialLinksContainer"></div>

<script type="application/javascript">
  const socialLinks = {{ params.socialLinks | json }};

  const container = document.getElementById("socialLinksContainer");

  socialLinks.forEach(link => {
    const a = document.createElement("a");
    a.href = link.href;
    a.title = link.title;
    a.target = "_blank";
    a.className = "social-link";

    const i = document.createElement("i");
    i.className = link.iconClass;

    a.appendChild(i);
    container.appendChild(a);
  });
</script>

Comment on lines +272 to +283
<div class="contact-item">
<i class="bi bi-envelope"></i>
<a href="mailto:[email protected]">[email protected]</a>
</div>
<div class="contact-item">
<i class="bi bi-globe"></i>
<a href="https://nicebread.de target="_blank">Personal Website</a>
</div>
<div class="contact-item">
<i class="bi bi-globe"></i>
<a href="https://www.osc.uni-muenchen.de/index.html target="_blank">Faculty Website</a>
</div>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generalize the contact items to a loop too? This allows multiple emails and websites then

Comment on lines +319 to +324
<div class="interests-container">
<div class="interest-tag">Open Science</div>
<div class="interest-tag">Psychology</div>
<div class="interest-tag">Psychological Methods</div>
<div class="interest-tag">Data Sharing</div>
</div>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generalize as a for loop with a research interests parameter in the yaml

Comment on lines +327 to +338
<div class="publications-list">
<div class="publication-item">
<div class="publication-year">2024</div>
<div class="publication-content">
<h3>"Machine Learning Applications in Organizational Behavior"</h3>
<p class="publication-authors">Smith, J., Johnson, A., & Williams, R.</p>
<p class="publication-journal"><em>Journal of Applied Research</em>, 42(3), 256-278</p>
<div class="publication-links">
<a href="#" class="pub-link"><i class="bi bi-box-arrow-up-right"></i> DOI</a>
</div>
</div>
</div>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generalize to for loop. TBD how the information should be collected--manual entry or somehow access an existing citation file somewhere? Or find another solution?

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 this pull request may close these issues.

2 participants