KO | EN

GitLite

Minimalist Open Source Repository Search Engine

gitlite — search

#typescript #ai-agents #developer-tools #cli #codex #claude-code #dsh-plugin #mcp #react #agent #dsh #deepseek-harness

Terminal-Portfolio

★ 75 Open GitHub ↗

Terminal Style Portfolio made with HTML / CSS / JS

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

![image](https://user-images.githubusercontent.com/76687985/210350014-65e73f81-4819-44ad-a182-3b8e7f584416.png)
[see live here!](https://techspiritss.github.io/Terminal-Portfolio/)

### *Terminal Portfolio*

![Issues](https://img.shields.io/github/issues/TechSpiritSS/Terminal-Portfolio?color=brightgreen)
![Pull requests](https://img.shields.io/github/issues-pr/TechSpiritSS/Terminal-Portfolio)
![Forks](https://img.shields.io/github/forks/TechSpiritSS/Terminal-Portfolio)
![Stars](https://img.shields.io/github/stars/TechSpiritSS/Terminal-Portfolio)
![Licence](https://img.shields.io/github/license/TechSpiritSS/Terminal-Portfolio?color=orange)

---

# Why Terminal Portfolio?

## Vision

Terminal-Portfolio invites talented developers to create stunning, command-line themed portfolios to showcase their skills and work. Command-line interface is a powerful and efficient tool for developers, and this project aims to celebrate this through the creation of visually striking and intuitively designed web terminal.

## Status

I am currently using this as my default Portfolio.:sparkles:

## Docs

- [How to get started with Open Source](#how-to-get-started-with-open-source)
- [Contributing](#contributing)
  - [Ground Rules](#ground-rules)
  - [Codebase](#codebase)
    - [Technologies](#technologies)

(<a href="#readme-top">back to top</a>)

## Codebase

### Technologies

**Frontend HTML/CSS/JS**: Almost all of the code you'll touch in this codebase will be HTML, CSS or JavaScript.

## How to get started with Open Source
Here's a quick run down on how to get started with open source, first of all let's know some basic terminologies:

- Git: is a versioning system that let's you store your code and code history on your local computer preventing loses and allowing sharing of that code
- Github: is a server that let's you store the history in a database
- Open Source: A project is said to be open sourced if you can see the code on GitHub
- Fork: This is a copy that you make of a project on GitHub, it gets added to your repositories
- Repository: A project on GitHub is called a repository
- Pull Request: This is a fix for an issue proposed to be done in a project, this consists of you editing a file in the project.
- Issue: An issue is a change that should be done in a project, can be a bug, a new feature or a suggestion to a project
- Branch: A branch is a new workspace derived from the default workspace(main or master), it allows you to work on something without affecting the original code

Now you know some basic terms, let's get into how to get started with some resources to let you understand open source better:

- [Crash Course to Git and Github](https://www.youtube.com/watch?v=apGV9Kg7ics) - Video
- [A complete Guide to Open Source](https://www.youtube.com/watch?v=yzeVMecydCE) - Video
- [Guide to Open Source](https://www.freecodecamp.org/news/how-to-contribute-to-open-source-projects-beginners-guide/) - Article

(<a href="#readme-top">back to top</a>)

## Contributing

- Take a look at the existing [Issues](https://github.com/TechSpiritSS/Terminal-Portfolio/issues)
- Fork the Repo create a branch for any issue that you are working on and commit your work.
- Create a ** [Pull Request](https://github.com/TechSpiritSS/Terminal-Portfolio/pulls), which will be promptly reviewed and given suggestions for improvements by the community.
- Add screenshots or screen captures to your Pull Request to help us understand the effects of the changes that are included in your commits.

## How to make a Pull Request?

1. Start by forking the [**Terminal-Portfolio**](https://github.com/TechSpiritSS/Terminal-Portfolio) repository. Click on the <a href="https://github.com/TechSpiritSS/Terminal-Portfolio/fork"><img src="https://i.imgur.com/G4z1kEe.png" height="21" width="21"></a> symbol at the top right corner.

1. Clone your forked repository:

```bash
 git clone https://github.com/<your-github-username>/Terminal-Portfolio.git
 ```

1. Navigate to the new project directory:

```bash
    cd Terminal-Portfolio
    ```

1. Set upstream command:

```bash
    git remote add upstream https://github.com/TechSpiritSS/Terminal-Portfolio.git
    ```

1. Create a new branch:

```bash
    git checkout -b YourBranchName
    ```

*or*

```bash
    git branch YourBranchName
    git switch YourBranchName
    ```

1. Sync your fork or local repository with the origin repository:

- In your forked repository click on "Fetch upstream"
   - Click "Fetch and merge".

### Alternatively, Git CLI way to Sync forked repository with origin repository:

```bash
git fetch upstream
```

```bash
git merge upstream/main
```

### [Github Docs](https://docs.github.com/en/github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github) for Syncing

7. Make your changes to the source code.

8. Stage your changes and commit:

⚠️ **Make sure** not to commit `package.json` or `package-lock.json` file

⚠️ **Make sure** not to run the commands ```git add .``` or ```git add *```. Instead, stage your changes for each file/folder

```bash
    git add file/folder
    ```

```bash
 git commit -m "<your_commit_message>"
 ```

9. Push your local commits to the remote repository:

```bash
    git push origin YourBranchName
    ```

10. Create a [Pull Request](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request)!

(<a href="#readme-top">back to top</a>)

## Alternatively to create a Pull Request using GitHub Desktop:

1. Open GitHub Desktop and log in to your GitHub account.

2. Make sure you are on the "Current Repository" view. If not, go to "File" and select "Add Local Repository" to add your repository.

3. In the "Current Repository" view, ensure you are on the branch that you want to submit a pull request for. If you're not on the correct branch, use the "Branch" menu to switch to the correct branch.

4. Once you're on the correct branch, make your changes and commit them to the branch. You can do this by clicking the "+" button in the upper-left corner of the GitHub Desktop window, making your changes, and then entering a commit message.

5. After you've made your changes and committed them, click the "Push origin" button in the top-right corner of the GitHub Desktop window. This will push your changes to the remote repository on GitHub.

6. Now, go to the GitHub website, navigate to your fork of the repository, and you should see a button to "Compare & pull request" between your fork and the original repository, click on it.

7. On the pull request page, you can review your changes and add any additional information, such as a title and a description, that you want to include with your pull request.

8. Once you're satisfied with your pull request, click the "Create pull request" button to submit it.

**Note:** In order to create a pull request, you must have a fork of the original repository in your GitHub account and you must have made the changes in that forked repository.

## **Congratulations!** You've made your first contribution! 🙌🏼

**We heartily welcome any and all contributions that match our engineering standards! :raised_hands:**

(<a href="#readme-top">back to top</a>)

## Ground Rules

#### Contributions and discussion guidelines

All conversations and communities on Terminal Portfolio agree to GitHub's [Community Guidelines](https://help.github.com/en/github/site-policy/github-community-guidelines) and [Acceptable Use Policies](https://help.github.com/en/github/site-policy/github-acceptable-use-policies). This code of conduct also applies to all conversations that happen within our contributor community here on GitHub. We expect discussions in issues and pull requests to stay positive, productive, and respectful. **Remember**: There are real people on the other side of that screen:exclamation:

#### Reporting a bug or discussing a feature idea

If you found a technical bug on Terminal Portfolio or have ideas for features we should implement, the issue tracker is the best place to share your ideas. Make sure to follow the issue template and you should be golden! ([click here to open a new issue](https://github.com/TechSpiritSS/Terminal-Portfolio/issues/new))

#### Fixing a bug or implementing a new feature

- If you find a bug on Terminal Portfolio and open a PR that fixes it.
- If you want to implement a new feature, open an issue first to discuss what it'd look like .
- If you want to contribute but are unsure to start, we have [a "good first issue" label](https://github.com/TechSpiritSS/Terminal-Portfolio/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) which is applied to newcomer-friendly issues. Take a look at [the full list of good first issues](https://github.com/TechSpiritSS/Terminal-Portfolio/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22) and pick something you like!
- Want to fix a bug or implement an agreed-upon feature? Great, jump to the [local setup instructions](#first-time-setup)!

(<a href="#readme-top">back to top</a>)

## Open Source Programs
<a href="https://hacktoberfest.com/">
<img width="1200" alt="Hacktoberfest22-Dark" src="https://user-images.githubusercontent.com/79099734/189589410-ca17afb8-5855-4316-918a-054f27594809.png">
</a>

## Thanks to all Contributors 💪

Thanks a lot for spending your time helping Terminal Portfolio grow. Thanks a lot! Keep rocking 🍻

[![Contributors](https://contrib.rocks/image?repo=techspiritss/terminal-portfolio)](https://github.com/TechSpiritSS/Terminal-Portfolio/graphs/contributors)

## License

### MIT License, see the [LICENSE](./LICENSE) file

(<a href="#readme-top">back to top</a>)

Terminal-Portfolio

Explore Similar Repositories

Was this content helpful?

Recent Feedback

Download README