Giter Club home page Giter Club logo

portfolio's Introduction

My Personal Portfolio ๐Ÿ“จ

This is my personal portfolio website built using HTML, CSS. The main aim of the website is showcases my skills and projects as an aspiring junior front-end developer, including my education, and previous work experience.

Table of contents ๐Ÿ“š

General info โ„น

A website of portfolio build to give small introduction about myself, work using agile methodology, html,css.

Screenshots ๐Ÿ“ท

Example screenshot

Technologies ๐Ÿ‘ฉโ€๐Ÿ’ป

  • HTML
  • CSS
  • VSC code
  • npm

Setup ๐Ÿ–ฅ

  • npm run start

Code Examples ๐Ÿ‘ฉโ€๐Ÿ’ป

<div class="contact-form">
  <form action="">
    <input type="name" placeholder="Your Name" required />
    <input type="email" placeholder="Your Email" required />
    <input type="number" placeholder="Your Mobile Number" required />
    <textarea
      name=""
      id=""
      cols="35"
      rows="10"
      placeholder="How Can I Help You"
      required
    ></textarea>
    <input type="submit" value="Send Message" class="submit" required />
  </form>
</div>
.top i {
  padding: 10px;
  border-radius: 8px;
  font-size: 15px;
  color: var(--text-color);
  background: var(--main-color);
}

Status ๐Ÿš€

Project is: Done

Inspiration ๐ŸŒŸ

  • Project code inspired by
  1. angela (app brewery)
  2. codehal you tube channel
  3. code with harry
  4. itech eazy code

Contact ๐Ÿ“ฑ

Name
Preethi Tapati (https://github.com/PreethiTapati)

Instructions for use

Getting Started
  1. git clone [email protected]:HackYourFutureBelgium/template-markdown.git
  2. cd template-markdown
  3. npm install

Code Quality Checks

  • npm run format: Makes sure all the code in this repository is well-formatted (looks good).
  • npm run lint:ls: Checks to make sure all folder and file names match the repository conventions.
  • npm run lint:md: Will lint all of the Markdown files in this repository.
  • npm run lint:css: Will lint all of the CSS files in this repository.
  • npm run validate:html: Validates all HTML files in your project.
  • npm run spell-check: Goes through all the files in this repository looking for words it doesn't recognize. Just because it says something is a mistake doesn't mean it is! It doesn't know every word in the world. You can add new correct words to the ./.cspell.json file so they won't cause an error.
  • npm run accessibility -- ./path/to/file.html: Runs an accessibility analysis on all HTML files in the given path and writes the report to /accessibility_report

Continuous Integration (CI)

When you open a PR to main/master in your repository, GitHub will automatically do a linting check on the code in this repository, you can see this in the./.github/workflows/lint.yml file.

If the linting fails, you will not be able to merge the PR. You can double check that your code will pass before pushing by running the code quality scripts locally.

Repo Setup

  • Give each member write access to the repo (if it's a group project)
  • Turn on GitHub Pages and put a link to your website in the repo's description
  • Turn on GitHub Actions
  • In General Section > check Discussions
  • In the Branches section of your repo's settings make sure the master/main branch must:
    • "Require a pull request before merging"
    • "Require approvals"
    • "Dismiss stale pull request approvals when new commits are pushed"
    • "Require status checks to pass before merging"
    • "Require branches to be up to date before merging"
    • "Do not allow bypassing the above settings"

portfolio's People

Contributors

preethitapati avatar

Watchers

 avatar

portfolio's Issues

Planning: Portfolio

1. Setup: GitHub

  • created this issue
  • assigned myself
  • moved the issue to the project board and added it to the appropriate
    column

2. Setup: local

  • pulled the most recent code from main/master
  • created a new feat-branch-name branch for my feature

3. Before pushing my branch:

  • pulled the most recent code from main/master to my feature branch
  • ran code quality checks
  • formatted the code
  • fixed all linting mistakes

4.After pushing my branch:

  • created a new PR linked to this issue
  • make sure all of the checks passed
  • assigned someone to review and merge my PR (if the task is ready)
  • moved the issue to the appropriate column in the project board to review
    it (if the task is ready)

add home:portfolio

Description

Steps

  • Setup: GitHub

    • created this issue
    • assigned myself
    • moved the issue to the project board and added it to the appropriate
      column
  • Setup: local

    • pulled the most recent code from main/master
    • created a new home branch for my feature
  • Before pushing my branch:

    • pulled the most recent code from main/master to my feature branch
    • ran code quality checks
    • formatted the code
    • fixed all linting mistakes
  • After pushing my branch:

    • created a new PR linked to this issue
    • make sure all of the checks passed
    • assigned someone to review and merge my PR (if the task is ready)
    • moved the issue to the appropriate column in the project board to review
      it (if the task is ready)

add contact-me: portfolio

Description

Steps

  • Setup: GitHub

    • created this issue
    • assigned myself
    • moved the issue to the project board and added it to the appropriate
      column
  • Setup: local

    • pulled the most recent code from main/master
    • created a new contact-me branch for my feature
  • Before pushing my branch:

    • pulled the most recent code from main/master to my feature branch
    • ran code quality checks
    • formatted the code
    • fixed all linting mistakes
  • After pushing my branch:

    • created a new PR linked to this issue
    • make sure all of the checks passed
    • assigned someone to review and merge my PR (if the task is ready)
    • moved the issue to the appropriate column in the project board to review
      it (if the task is ready)

add skills:portfolio

Description

Steps

  • Setup: GitHub

    • created this issue
    • assigned myself
    • moved the issue to the project board and added it to the appropriate
      column
  • Setup: local

    • pulled the most recent code from main/master
    • created a new skills branch for my feature
  • Before pushing my branch:

    • pulled the most recent code from main/master to my feature branch
    • ran code quality checks
    • formatted the code
    • fixed all linting mistakes
  • After pushing my branch:

    • created a new PR linked to this issue
    • make sure all of the checks passed
    • assigned someone to review and merge my PR (if the task is ready)
    • moved the issue to the appropriate column in the project board to review
      it (if the task is ready)

nav bar: portfolio

Description

Steps

  • Setup: GitHub

    • created this issue
    • assigned myself
    • moved the issue to the project board and added it to the appropriate
      column
  • Setup: local

    • pulled the most recent code from main/master
    • created a new nav-bar branch for my feature
  • Before pushing my branch:

    • pulled the most recent code from main/master to my feature branch
    • ran code quality checks
    • formatted the code
    • fixed all linting mistakes
  • After pushing my branch:

    • created a new PR linked to this issue
    • make sure all of the checks passed
    • assigned someone to review and merge my PR (if the task is ready)
    • moved the issue to the appropriate column in the project board to review
      it (if the task is ready)

add retrospective: portfolio

Description

Steps

  • Setup: GitHub

    • created this issue
    • assigned myself
    • moved the issue to the project board and added it to the appropriate
      column
  • Setup: local

    • pulled the most recent code from main/master
    • created a new retrospective branch for my feature
  • Before pushing my branch:

    • pulled the most recent code from main/master to my feature branch
    • ran code quality checks
    • formatted the code
    • fixed all linting mistakes
  • After pushing my branch:

    • created a new PR linked to this issue
    • make sure all of the checks passed
    • assigned someone to review and merge my PR (if the task is ready)
    • moved the issue to the appropriate column in the project board to review
      it (if the task is ready)

add responsiveness: portfolio

Description

Steps

  • Setup: GitHub

    • created this issue
    • assigned myself
    • moved the issue to the project board and added it to the appropriate
      column
  • Setup: local

    • pulled the most recent code from main/master
    • created a new responsive ness branch for my feature
  • Before pushing my branch:

    • pulled the most recent code from main/master to my feature branch
    • ran code quality checks
    • formatted the code
    • fixed all linting mistakes
  • After pushing my branch:

    • created a new PR linked to this issue
    • make sure all of the checks passed
    • assigned someone to review and merge my PR (if the task is ready)
    • moved the issue to the appropriate column in the project board to review
      it (if the task is ready)

add projects-section: portfolio

Description

Steps

  • Setup: GitHub

    • created this issue
    • assigned myself
    • moved the issue to the project board and added it to the appropriate
      column
  • Setup: local

    • pulled the most recent code from main/master
    • created a new projects branch for my feature
  • Before pushing my branch:

    • pulled the most recent code from main/master to my feature branch
    • ran code quality checks
    • formatted the code
    • fixed all linting mistakes
  • After pushing my branch:

    • created a new PR linked to this issue
    • make sure all of the checks passed
    • assigned someone to review and merge my PR (if the task is ready)
    • moved the issue to the appropriate column in the project board to review
      it (if the task is ready)

end section: portfolio

Description

Steps

  • Setup: GitHub

    • created this issue
    • assigned myself
    • moved the issue to the project board and added it to the appropriate
      column
  • Setup: local

    • pulled the most recent code from main/master
    • created a new end branch for my feature
  • Before pushing my branch:

    • pulled the most recent code from main/master to my feature branch
    • ran code quality checks
    • formatted the code
    • fixed all linting mistakes
  • After pushing my branch:

    • created a new PR linked to this issue
    • make sure all of the checks passed
    • assigned someone to review and merge my PR (if the task is ready)
    • moved the issue to the appropriate column in the project board to review
      it (if the task is ready)

add about-me section:portfolio

Description

Steps

  • Setup: GitHub

    • created this issue
    • assigned myself
    • moved the issue to the project board and added it to the appropriate
      column
  • Setup: local

    • pulled the most recent code from main/master
    • created a new about-me branch branch for my feature
  • Before pushing my branch:

    • pulled the most recent code from main/master to my feature branch
    • ran code quality checks
    • formatted the code
    • fixed all linting mistakes
  • After pushing my branch:

    • created a new PR linked to this issue
    • make sure all of the checks passed
    • assigned someone to review and merge my PR (if the task is ready)
    • moved the issue to the appropriate column in the project board to review
      it (if the task is ready)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.