Skip to content

Commit 2128bae

Browse files
committed
Add installation instructions and update docs
1 parent 1b02ad1 commit 2128bae

File tree

4 files changed

+38
-17
lines changed

4 files changed

+38
-17
lines changed

LICENSE.txt

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
The MIT License (MIT)
22

3-
Copyright (c) 2020 Liang Jun
3+
Copyright (c) 2020 afterdusk
44

55
Permission is hereby granted, free of charge, to any person obtaining a copy
66
of this software and associated documentation files (the "Software"), to deal

README.md

+34-13
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,24 @@
11
# namecard
2+
### *namecard* is a markdown-driven, single page CV
23

3-
Welcome to your new Jekyll theme! In this directory, you'll find the files you need to be able to package up your theme into a gem. Put your layouts in `_layouts`, your includes in `_includes`, your sass files in `_sass` and any other assets in `assets`.
4+
![namecard](/assets/namecard.png)
45

5-
To experiment with this code, add some sample content and run `bundle exec jekyll serve` – this directory is setup just like a Jekyll site!
6+
**markdown-driven**: all of the content and most of the styling on the site can be edited with markdown, which is flexible and easy to use
67

7-
TODO: Delete this and the text above, and describe your gem
8+
**single page**: a single page is concise and doesn't overwhelm visitors - see the [*KISS*](https://en.wikipedia.org/wiki/KISS_principle) principle
9+
10+
## Usage
11+
12+
Usage instructions and theme options are available at https://github.com/afterdusk/use-namecard, an example site using *namecard*. I highly recommend cloning the repository and editing the content from the template instead of performing an install on an existing repo.
813

914
## Installation
15+
There are two ways of installing Jekyll themes:
16+
17+
### 1. Gem Installation
18+
---
19+
Note that this approach will not work with GitHub Pages build and deploy. If you are using this approach and want to deploy with GitHub Pages, you will have to build your site locally and only push the output `_site` folder.
20+
21+
---
1022

1123
Add this line to your Jekyll site's `Gemfile`:
1224

@@ -24,26 +36,35 @@ And then execute:
2436
2537
$ bundle
2638
27-
Or install it yourself as:
39+
Or install it yourself with:
2840
2941
$ gem install namecard
3042
31-
## Usage
43+
### 2. GitHub Pages Remote Theme
44+
If you plan to deploy with GitHub Pages, this is the far simpler approach of adding the theme to your site. Add the following line to your site's `_config.yml`:
3245

33-
TODO: Write usage instructions here. Describe your available layouts, includes, sass and/or assets.
46+
```yaml
47+
remote_theme: afterdusk/namecard
48+
```
3449

35-
## Contributing
50+
In your `Gemfile`, ensure the following lines are commented out:
51+
```ruby
52+
# gem "namecard"
53+
# gem "jekyll", "~> 3.8.5"
54+
```
3655

37-
Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/hello. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
56+
And uncomment the line:
57+
```ruby
58+
gem "github-pages", "~> 204", group: :jekyll_plugins
59+
```
3860

39-
## Development
61+
Note: Make sure a version number is included in the above line
4062

41-
To set up your environment to develop this theme, run `bundle install`.
63+
You can then [test the site locally](https://help.github.com/en/github/working-with-github-pages/testing-your-github-pages-site-locally-with-jekyll) before [deploying to GitHub pages](https://help.github.com/en/github/working-with-github-pages/creating-a-github-pages-site-with-jekyll).
4264

43-
Your theme is setup just like a normal Jekyll site! To test your theme, run `bundle exec jekyll serve` and open your browser at `http://localhost:4000`. This starts a Jekyll server using your theme. Add pages, documents, data, etc. like normal to test your theme's contents. As you make modifications to your theme and to your content, your site will regenerate and you should see the changes in the browser after a refresh, just like normal.
65+
## Contributing
4466

45-
When your theme is released, only the files in `_layouts`, `_includes`, `_sass` and `assets` tracked with Git will be bundled.
46-
To add a custom directory to your theme-gem, please edit the regexp in `namecard.gemspec` accordingly.
67+
Bug reports, suggestions and pull requests are welcome on GitHub at https://github.com/afterdusk/namecard. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
4768

4869
## License
4970

assets/namecard.png

112 KB
Loading

namecard.gemspec

+3-3
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,10 @@
33
Gem::Specification.new do |spec|
44
spec.name = "namecard"
55
spec.version = "0.1.0"
6-
spec.authors = ["Liang Jun"]
7-
spec.email = ["[email protected]"]
6+
spec.authors = ["afterdusk"]
7+
spec.email = ["[email protected]"]
88

9-
spec.summary = "Markdown driven, single page CV targeted at developers"
9+
spec.summary = "Markdown driven, single page CV"
1010
spec.homepage = "https://www.github.com/afterdusk/namecard"
1111
spec.license = "MIT"
1212

0 commit comments

Comments
 (0)