| title | permalink |
|---|---|
Internal |
/internal/ |
This page contains important information for current lab members about managing their presence on the lab website and other internal processes.
When to ADD yourself:
- When you officially join the Kording Lab as a graduate student, postdoc, research staff, or visiting scholar
- Ideally within your first week of joining the lab
- After confirming with Konrad or the lab manager that you are officially part of the lab
When to REMOVE/UPDATE yourself:
- When you graduate or complete your position in the lab
- When transitioning to alumni status (you don't delete your profile, just change your position to 'alumni')
- If you're a visiting scholar, when your visit period ends
- Navigate to the
_peoplefolder in the repository - Create a new file named
<firstname>_<lastname>.md(all lowercase, e.g.,john_smith.md)
---
name: Your Full Name
position: [choose one: gradstudent/postdoc/researchstaff/visiting/alumni]
avatar: yourphoto.jpg
twitter: yourtwitterhandle
joined: 2024
---- Add a professional photo to the
images/people/folder - Name it to match the avatar field in your header (e.g.,
yourphoto.jpg) - Recommended: square aspect ratio, at least 400x400 pixels
- Make sure the photo is professional and represents you well
- After the header, write a brief bio (2-3 paragraphs)
- Include your research interests, background, and current projects
- You can use markdown formatting for links, bold text, etc.
- Keep it professional but feel free to add personality
- If comfortable with Git:
- Commit and push your changes
- Create a pull request
- If not familiar with Git:
- Email your files to the lab manager
- Or ask any lab member for help with the Git process
- Find your file in
_people/<firstname>_<lastname>.md - Edit the content - update your bio, position, or other information
- Update your photo if needed (replace the file in
images/people/) - Commit and push your changes or ask for help
When leaving the lab:
- Edit your profile file in
_people/<firstname>_<lastname>.md - Change the position field to
alumni:position: alumni
- Add your next position to your bio (e.g., "Now at [Company/University]")
- Keep your profile - don't delete it! Alumni remain part of the lab community
- Commit and push the changes
Lab members are expected to be in the office 4 days a week unless discussed otherwise with Konrad.
This policy promotes:
- Collaboration and spontaneous discussions
- Stronger lab community and culture
- Better mentorship opportunities
- Quick problem-solving and idea exchange
Exceptions can be discussed for:
- Remote collaborations
- Data collection off-site
- Conference attendance
- Personal circumstances (discuss with Konrad)
Important Lab Policy: Any significant piece of work from the lab should be presented at exactly one conference before submitting to a journal.
This policy ensures:
- Work receives feedback from the community before publication
- Ideas are tested and refined through presentation
- Lab members gain presentation experience
- The lab maintains visibility in the research community
Guidelines:
- Choose the most appropriate conference for your work
- Coordinate with Konrad about conference selection
- Budget for conference attendance should be discussed in advance
- After presentation, incorporate feedback before journal submission
When you publish a paper:
- Edit
publications.md - Find the correct year section
- Add your publication in this format:
_Paper Title_<br> Author1, Author2, KP Kording, etc<br> Journal Name, Year ([Article](link-if-available))
- Maintain chronological order within the year
- Include all lab members who are authors
For lab news and announcements:
- Edit
_data/news.yml - Add a new entry at the top:
- date: YYYY-MM-DD details: "Your news item here. Can include <a href='link'>links</a>"
- Note: Some characters like
:need special handling - use quotes around your text
Basic Git workflow:
git pull # Get latest changes
git add . # Stage your changes
git commit -m "message" # Commit with descriptive message
git push # Push to GitHubEditing directly on GitHub:
- Navigate to the file on GitHub.com
- Click the pencil icon to edit
- Make your changes
- Commit directly or create a pull request
Before pushing changes:
jekyll serveThen visit localhost:4000 to preview
- Administrative questions: Email Thomas McDonald taomcd@seas.upenn.edu (Konrad is clueless about anything administrative)
- Git/GitHub issues: Ask any lab member familiar with Git
- Website technical issues: Contact the designated website maintainer
- Content questions: Check with Konrad or senior lab members
- Emergency updates: Contact multiple lab members to ensure quick response
- Keep profiles updated - Outdated information reflects poorly on everyone
- Use professional photos - This is a public-facing website
- Write clear commit messages - Help others understand what you changed
- Test before pushing - Use
jekyll servefor significant changes - Ask for help - Better to ask than to break something
- Regular updates - Check your profile every semester
- Lab GitHub: github.com/KordingLab
- Website Repository: github.com/KordingLab/KordingLab.github.io
- Live Website: kordinglab.com
- C4R Platform: c4r.io
This page is for internal use by Kording Lab members. If you're not a lab member but interested in joining, please see the About page for more information.