Skip to content

Judithmalachy patch 1 #139

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.

Sign up for GitHub

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 3 commits into
base: master
Choose a base branch
from
Open

Judithmalachy patch 1 #139

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c6ec7b3
Updated my CV
Jun 6, 2025
1069ddf
Update README.md
Judithmalachy Jun 6, 2025
89161e6
Update README.md
Judithmalachy Jun 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
110 changes: 71 additions & 39 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,65 +1,97 @@
# markdown-cv
# Judith Malachy

A curriculum vitae maintained in plain text and rendered to HTML and PDF using CSS.
## Contact
**Email:** [email protected]
**GitHub:** [https://github.com/JudithMalachy](https://github.com/JudithMalachy)
**LinkedIn:** [https://www.linkedin.com/in/judith-malachy-99615524a](https://www.linkedin.com/in/judith-malachy-99615524a)

For more details, see the [project page](http://elipapa.github.io/markdown-cv), or the blog post on [why I switched to markdown for my CV](http://elipapa.github.io/blog/why-i-switched-to-markdown-for-my-cv.html).
---

***
## Education

## Customization
**B.Sc. Biochemistry**
Veritas University

Simply [fork the markdown-cv repo](https://github.com/elipapa/markdown-cv)
---

![](https://help.github.com/assets/images/help/repository/fork_button.jpg)
## Skills

and edit the `index.md` file [directly in Github](https://help.github.com/articles/editing-files-in-your-repository/)
- Microsoft Office Tools (Word, Excel, PowerPoint)
- Video Editing & Graphics Design
- Problem-Solving
- Creativity
- Time Management

![](https://help.github.com/assets/images/help/repository/edit-file-edit-button.png)
---

adding your skills, jobs and education.
## Experience

![](https://help.github.com/assets/images/help/repository/edit-readme-light.png)
**Sales Executive**
*Fidelity Bank PLC*
- Provided customer support and financial product recommendations.
- Met sales targets and maintained client relationships.

## Distribution
**Data Clerk**
*Sefa Specialist Hospital*
- Managed patient records and digital data entry.
- Ensured data accuracy and confidential handling of medical information.

To transform your plain text CV into a beautiful and shareable HTML page, you have two options:
---

### I. Use Github Pages to publish it online
## Projects

1. Delete the existing `gh-pages` branch from your fork. It will only contain this webpage. You can either use git or [the Github web interface](https://help.github.com/articles/creating-and-deleting-branches-within-your-repository/#deleting-a-branch).
2. Create a new branch called `gh-pages`.
3. Head to *yourusername*.github.io/markdown-cv to see your CV live.
**Markdown CV Project**
- Wrote and formatted CV using Markdown.
- Pushed to GitHub and published as a personal website.

Any change you want to make to your CV from then on would have to be done on the `gh-pages` branch and will be immediately rendered by Github Pages.
---
## Key Achievements

### II. Build it locally and print a PDF
- Successfully completed a Git & GitHub-based CV project using Markdown.
- Led a group assignment and supported peers in understanding Git basics.
- Built and published a personal CV site using GitHub Pages.
- Applied version control best practices using branches and pull requests.

1. To [install jekyll](https://jekyllrb.com/docs/installation/), run `gem install bundler jekyll` from the command line.
3. [Clone](https://help.github.com/en/articles/cloning-a-repository) your fork of markdown-cv to your local machine.
3. Type `jekyll serve` to render your CV at http://localhost:4000.
4. You can edit the `index.md` file and see the changes live in your browser.
5. To print a PDF, press <kbd>⌘</kbd> + <kbd>p</kbd>. Print and web CSS media queries should take care of the styling.

## Styling
## Links

The included CSS will render your CV in two styles:
s
1. `kjhealy` the original default, inspired by [kjhealy's vita
template](https://github.com/kjhealy/kjh-vita).
2. `davewhipp` is a tweaked version of `kjhealy`, with bigger fonts and dates
right aligned.
- GitHub: [https://github.com/JudithMalachy](https://github.com/JudithMalachy)
- CV Website: [https://judithmalachy.github.io/my-cv](https://judithmalachy.github.io/my-cv)
- LinkedIn: [https://www.linkedin.com/in/judith-malachy-99615524a](https://www.linkedin.com/in/judith-malachy-99615524a)

To change the default style, simply change the variable in the
`_config.yml` file.
---
---

Any other styling is possible. More CSS style contributions and forks are welcome!
## Technical Reflection & Personal Process

### Author
This project pushed me through one of the most intense technical learning curves I’ve ever experienced. The task was to create a Markdown-based CV, publish it as a live webpage using GitHub Pages, and reflect on the process — but what seemed like a simple assignment turned into a deeply stressful journey.

Eliseo Papa ([Twitter](http://twitter.com/elipapa)/[Github](http://github.com/elipapa)/[Website](https://elipapa.github.io)).
### Technical Work Done

- I initialized a Git repository, committed and tracked changes using the terminal
- Created and worked on a feature branch for the new CV section
- Merged it back into `master` using a Pull Request
- Configured GitHub Pages to serve my Markdown CV as a live website
- Edited files both from the terminal and directly on GitHub to fix or update content
- Dealt with authentication and GitHub Pages setup that didn’t behave as expected

### Challenges I Faced

The process was far from smooth:

- I had **Git authentication issues** that kept blocking my push commands and delayed my progress
- The **GitHub Pages setup was confusing**, especially figuring out which URL was actually hosting my site
- At one point, I had multiple branches and was unsure which one to publish or where my real CV lived
- The terminal sometimes froze or stopped accepting commands, forcing me to cancel and start over
- I spent long hours figuring things out that were supposed to take minutes

### Personal Reflection

I was exhaused, frustrated and even considered giving up multiple times. Despite following instructions, GitHub often didn’t respond the way I expected. I felt stuck, overwhelmed, and mentally drained — but I didn’t give up.

Through persistence and support, I managed to complete every part of the assignment. I now understand Git and GitHub better, not just technically, but also the patience and resilience required to work with real-world tools. This experience reminded me that learning isn’t always smooth, but the growth comes from pushing through the frustration.

This project wasn’t just about publishing a CV. It was about proving to myself that I can stick with something difficult and come out the other side with real, practical skills.

![Eliseo Papa](https://s.gravatar.com/avatar/eae1f0c01afda2bed9ce9cb88f6873f6?s=100)

### License

[MIT License](https://github.com/elipapa/markdown-cv/blob/master/LICENSE)