Skip to content
This repository has been archived by the owner on Oct 9, 2024. It is now read-only.

Commit

Permalink
Initial commit
Browse files Browse the repository at this point in the history
  • Loading branch information
seanshoffman committed Sep 27, 2019
1 parent ad1a3c8 commit 7ccec54
Show file tree
Hide file tree
Showing 11 changed files with 1,722 additions and 2 deletions.
1 change: 1 addition & 0 deletions .dockerignore
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
node_modules
14 changes: 14 additions & 0 deletions .gitattributes
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
# Set the default behavior, in case people don't have core.autocrlf set.
* text=auto

# Explicitly declare text files you want to always be normalized and converted
# to native line endings on checkout.
*.c text
*.h text

# Declare files that will always have CRLF line endings on checkout.
*.sln text eol=crlf

# Denote all files that are truly binary and should not be modified.
*.png binary
*.jpg binary
4 changes: 4 additions & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
node_modules/
.projects_config
npm-debug.log
.DS_Store
1 change: 1 addition & 0 deletions .nvmrc
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
9.9.0
13 changes: 13 additions & 0 deletions Dockerfile
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
FROM node:8.12-alpine

WORKDIR /src/app/

ADD ./package.json .

RUN ["npm", "install"]

COPY . .

RUN chown -R node:node /src/app

USER node
21 changes: 21 additions & 0 deletions LICENSE.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
MIT License

Copyright (c) 2016 Pluralsight

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
130 changes: 128 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,2 +1,128 @@
# sean-hp-state-test
Hello Pluralsight course created on staging
# Hello Pluralsight



## Short Description

This is a sample project to test out how Projects work at Pluralsight. For this project, you'll be creating a basic website using HTML. If you want to deploy it to a real website, we'll even walkthrough how to do that!



## Full Description

### Project Overview

Learn the basics of Pluralsight Projects with this quick introduction, and become comfortable using Git and GitHub — even if you’ve never used them before.

You'll edit a basic HTML page, as well as fork a GitHub repository and clone it down locally.

Here's what you'll build in this project:

![Screenshot](https://raw.githubusercontent.com/pluralsight-projects/HelloPluralsightProject/master/screenshot.png)

### Applications and Tools You'll Need To Complete This Project

You'll need to have access to the following tools on your local machine to complete this project.

* Git
* GitHub
* Code Editor
* Command Line / Terminal Access

Never used Git and don’t have a code editor? We have a video that walks you through all the steps you’ll need to set this up.

### Prerequisite Knowledge

Completing all of the tasks in this project requires knowledge of basic HTML. You'll also need to have a working knowledge of git to commit local changes and push them up to a GitHub repository. We'll walk you through that part, so if you haven't used Git before -- don't worry. We recommend that you should have already completed the following Pluralsight Courses:

* [HTML Fundamentals](https://app.pluralsight.com/library/courses/html-fundamentals/table-of-contents)

And have an understanding of the following topics:

* Know what an HTML tag looks like and how to add one to an existing HTML file.
* Know some of the most common tags, like `title`, `h1`, `ul`, and `li`.

If you know these, you should be all set to jump in and give this project a shot!

### Live Demo

Wondering what this project will look like when you've completed it? [Follow this link](#) to see a live version of it.



## Setting Up The Project

In order to get this working, you'll need to have [Git](https://git-scm.com/) installed on your computer, and have a GitHub account. If this is your first time setting up Git, I'd recommend checking out Pluralsight's video on How to Setup Git for Pluralsight Projects in 5 Minutes to learn what you need to know.

The very first step is to fork this repository to your personal GitHub account and clone it down locally. We'll be editing the `index.html` file in the root directory for this project.

### Associate Project with Pluralsight

After cloning this repository down, copy the ".projects_config" file from the [HelloPluralsightProject](#) and save that to this directory. This will allow your status to be reflected on the website while you're working through the project locally!

[//]: # (install: "npm install")
### Installation

Run the following command from root folder of the `HelloPluralsightProject` to install all dependencies.

```
$ npm install
```

[//]: # (test: "npm test")
[//]: # (test-watch: "npm test-watch")
### Verify Setup

In order to verify that everything is setup correctly, run the following command, which should show you a list of failing tests. This is good! Each of these tests corresponds to something we'll be working on in this project. By the end, all of the tests will pass.

```
$ npm test
```

We recommend also running the following command, which will watch for any changes to your files and then re-run the tests automatically. This makes things easier, since you'll see updates immediately when you save your files! You can run this command once, and then look back at the terminal after you've made changes to the "index.html" file.

```
$ npm test-watch
```



[//]: # (project_id: hello-pluralsight)
[//]: # (test: node_modules/.bin/mocha test/hello-pluralsight_test.js)
## Hello Pluralsight

[//]: # (task_id: @title)
### Add a Page Title

Create a `title` element with your name that's a child of the `head` element.

[//]: # (task_id: @h1)
### Add a Header Element

Add an `h1` that's a child of the `body` that says "Hello, Pluralsight!".

[//]: # (task_id: @ul)
## Create an Unordered List

Create a `ul` element that's a child of the `body` that contains at least 2 `li` elements.

[//]: # (task_id: @li)
## What Do You Want to Learn?

In each of those `li` elements, list out one thing you'd like to learn.





## Next Steps

Once all tests are passing, try pushing your master branch up to the `gh-pages` branch -- this will make your webpage available on the web! Here's a command to do that:

```
$ npm run deploy:github-pages
```

This will make your `index.html` file available at the URL:

`http://<username>.github.io/HelloPluralsightProject/`
11 changes: 11 additions & 0 deletions index.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
<!DOCTYPE html>
<html lang='en'>
<head>
<meta charset='utf-8'>
<meta http-equiv='X-UA-Compatible' content='IE=edge'>
<meta name='viewport' content='width=device-width, initial-scale=1'>
</head>
<body>

</body>
</html>
Loading

0 comments on commit 7ccec54

Please sign in to comment.