LinuxSuRen / LinuxSuRen/markdown-portfolio

Getting Started with GitHub

Open
#1 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

## Welcome to your repository!

In this repository [:book:](https://help.github.com/articles/github-glossary/#repository), you’ll learn how to write with Markdown [:book:](https://help.github.com/articles/github-glossary/#markdown), a simple and widely used markup language for formatting text. Here, you’ll start building a static webpage for your customized portfolio.

### What is Markdown?

Markdown is a lightweight syntax for communicating on GitHub, and many other websites. You can format words as **bold** or _italic_, add images, and create lists. Markdown is regular text combined with a few non-alphabetic symbols, such as `#` or `*`. You can use Markdown with the formatting toolbar in issues [:book:](https://help.github.com/articles/github-glossary/#issues) and pull requests [:book:](https://help.github.com/articles/github-glossary/#pull-request), or you can type the syntax.

You can use Markdown most places around GitHub:

- Comments in issues and pull requests (like this one!)
- Files with the `.md` or `.markdown` extension
- Sharing snippets of text in [Gists](https://help.github.com/en/articles/about-gists)

For more information, see “[Writing on GitHub](https://help.github.com/categories/writing-on-github/)” in the _GitHub Help_.

Let's get started!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue body is a GitHub and Markdown introduction, but it names no repository file, test, or entry point to change. First locate where this tutorial content is stored; completion cannot be confirmed until the issue specifies the intended documentation change and its acceptance criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
markdown
Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.