This manual provides step-by-step instructions for managing content on our department website. The website uses Jekyll and is automatically deployed through GitHub. You will use GitHub Desktop to submit your changes.
C:\Website\)your-website-folder/
├── __news_/
├── __events_/
├── _faculty/
├── _data/staff.yml
├── assets/images/
│ ├── news/
│ ├── faculty/
│ └── staff/
assets/images/news/ folderYYYY-MM-DD-descriptive-name.jpg
2024-03-15-annual-conference.jpg_news/ folderYYYY-MM-DD-title-of-news.md
2025-11-27-mahesh-kumar-ieee-fellowship.md---
title: "Prof. Mahesh Kumar becomes IEEE Fellow"
date: 2025-11-27
image: /assets/images/faculty/mahesh-kumar.png
image_description: "Prof. Mahesh Kumar"
layout: news
classes: wide
---
Congratulations to Prof. Mahesh Kumar on becoming an **IEEE Fellow** for outstanding contributions in Power Engineering.
You can add multiple paragraphs.
Type image description clearly.
- Bullet points work too
- Second bullet point
**Bold text** and *italic text* are supported.
Follow same steps as above, but remove the image line from the header:
---
title: "Prof. Mahesh Kumar becomes IEEE Fellow"
date: 2025-11-27
layout: news
classes: wide
---
_events/YYYY-MM-DD-ms-seminar-topic.md---
title: "Exploration of Dual Issue in-order designs based on Shakti C-Class"
date: 2025-11-26
time: "3:00 PM"
venue: "CSD-308"
speaker: "Mr. MOUNA KRISHNA GADHIRAJU (EE22S082)"
guide: "Dr. Nitin Chandrachoodan"
co_guide:
category: "ms"
layout: single
---
**Abstract:**
The Shakti C-Class is an open-source processor built on the RISC-V architecture. It features a simple, in-order, single-issue, 6-stage pipeline design, while incorporating several elements typically found in superscalar processors, such as a scoreboard and deeper pipeline buffers to enhance performance. However, these features are found to be underutilized in the baseline architecture. To address this, we present a case study on upgrading the single-issue pipeline to a dual-issue pipeline with details of how each micro-architectural change affected the area and performance. We achieve a best case CoreMark score of 3.74 CM/MHz, representing a 42.2% improvement, with 7.6% of area overhead compared to the baseline design.
DO NOT MODIFY THE CONTENT BELOW IN ANY EVENT
**Event Details**
**Title:** {{ page.title }}
**Date:** {{ page.date | date: "%B %d, %Y" }} at {{ page.time }}
**Venue:** {{ page.venue }}
**Speaker:** {{ page.speaker }}
**Guide:** {{ page.guide }}
**Type:** {{ page.category | upcase }} seminar
Same as MS seminar but change: - File name:
YYYY-MM-DD-phd-seminar-topic.md -
category: phd
Same as MS/PhD seminar but change: - File name:
YYYY-MM-DD-event-topic.md -
category: other
firstname-lastname.jpg in
assets/images/faculty/
john-doe.jpg_faculty/ folderfirstname-lastname.md
john-doe.mdMake sure that the image name and avatar name are correct and identical
images/faculty/ for record. It may be
needed for news items. Do not delete them._faculty/ folderjohn-doe.md)firstname-lastname.jpg in
assets/images/staff/_data/ folder- name: "Amal Mohan PK"
position: "Technical Staff"
email: "amalmohanpk@ee.iitm.ac.in"
phone: "+91-44-2257-4400"
office: "ESB 210D [EE Office]"
photo: "amal.png"
You can edit the above file when needed
_data/staff.yml fileimages/staff/ for records| Issue | Solution |
|---|---|
| Changes not appearing on website | Wait 5 minutes, then refresh. Check GitHub Actions tab in repository. |
| Image not displaying | Check filename matches exactly. Ensure image is in correct folder. |
| Formatting looks wrong | Check that you’re using proper markdown syntax. Copy from working examples. |
| GitHub Desktop shows error | Click “Fetch origin” first, then try pushing again. |
| File not in correct location | Move file to proper folder before committing. |