Skip to content

Commit fee995f

Browse files
committed
Started docs
1 parent 43a07de commit fee995f

45 files changed

Lines changed: 4926 additions & 2524 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎SpotifyAPI.Docs/.gitignore‎

Lines changed: 20 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,20 @@
1-
docs/.vuepress/dist
2-
node_modules/
1+
# Dependencies
2+
/node_modules
3+
4+
# Production
5+
/build
6+
7+
# Generated files
8+
.docusaurus
9+
.cache-loader
10+
11+
# Misc
12+
.DS_Store
13+
.env.local
14+
.env.development.local
15+
.env.test.local
16+
.env.production.local
17+
18+
npm-debug.log*
19+
yarn-debug.log*
20+
yarn-error.log*

‎SpotifyAPI.Docs/README.md‎

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
# Website
2+
3+
This website is built using [Docusaurus 2](https://v2.docusaurus.io/), a modern static website generator.
4+
5+
### Installation
6+
7+
```
8+
$ yarn
9+
```
10+
11+
### Local Development
12+
13+
```
14+
$ yarn start
15+
```
16+
17+
This command starts a local development server and open up a browser window. Most changes are reflected live without having to restart the server.
18+
19+
### Build
20+
21+
```
22+
$ yarn build
23+
```
24+
25+
This command generates static content into the `build` directory and can be served using any static contents hosting service.
26+
27+
### Deployment
28+
29+
```
30+
$ GIT_USER=<Your GitHub username> USE_SSH=true yarn deploy
31+
```
32+
33+
If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the `gh-pages` branch.

‎SpotifyAPI.Docs/docs.cmd‎

Lines changed: 0 additions & 28 deletions
This file was deleted.

‎SpotifyAPI.Docs/docs/.vuepress/config.js‎

Lines changed: 0 additions & 51 deletions
This file was deleted.

‎SpotifyAPI.Docs/docs/doc1.md‎

Lines changed: 202 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,202 @@
1+
---
2+
id: doc1
3+
title: Style Guide
4+
sidebar_label: Style Guide
5+
---
6+
7+
You can write content using [GitHub-flavored Markdown syntax](https://github.github.com/gfm/).
8+
9+
## Markdown Syntax
10+
11+
To serve as an example page when styling markdown based Docusaurus sites.
12+
13+
## Headers
14+
15+
# H1 - Create the best documentation
16+
17+
## H2 - Create the best documentation
18+
19+
### H3 - Create the best documentation
20+
21+
#### H4 - Create the best documentation
22+
23+
##### H5 - Create the best documentation
24+
25+
###### H6 - Create the best documentation
26+
27+
---
28+
29+
## Emphasis
30+
31+
Emphasis, aka italics, with _asterisks_ or _underscores_.
32+
33+
Strong emphasis, aka bold, with **asterisks** or **underscores**.
34+
35+
Combined emphasis with **asterisks and _underscores_**.
36+
37+
Strikethrough uses two tildes. ~~Scratch this.~~
38+
39+
---
40+
41+
## Lists
42+
43+
1. First ordered list item
44+
1. Another item ⋅⋅\* Unordered sub-list.
45+
1. Actual numbers don't matter, just that it's a number ⋅⋅1. Ordered sub-list
46+
1. And another item.
47+
48+
⋅⋅⋅You can have properly indented paragraphs within list items. Notice the blank line above, and the leading spaces (at least one, but we'll use three here to also align the raw Markdown).
49+
50+
⋅⋅⋅To have a line break without a paragraph, you will need to use two trailing spaces.⋅⋅ ⋅⋅⋅Note that this line is separate, but within the same paragraph.⋅⋅ ⋅⋅⋅(This is contrary to the typical GFM line break behaviour, where trailing spaces are not required.)
51+
52+
- Unordered list can use asterisks
53+
54+
* Or minuses
55+
56+
- Or pluses
57+
58+
---
59+
60+
## Links
61+
62+
[I'm an inline-style link](https://www.google.com)
63+
64+
[I'm an inline-style link with title](https://www.google.com "Google's Homepage")
65+
66+
[I'm a reference-style link][arbitrary case-insensitive reference text]
67+
68+
[I'm a relative reference to a repository file](../blob/master/LICENSE)
69+
70+
[You can use numbers for reference-style link definitions][1]
71+
72+
Or leave it empty and use the [link text itself].
73+
74+
URLs and URLs in angle brackets will automatically get turned into links. http://www.example.com or <http://www.example.com> and sometimes example.com (but not on Github, for example).
75+
76+
Some text to show that the reference links can follow later.
77+
78+
[arbitrary case-insensitive reference text]: https://www.mozilla.org
79+
[1]: http://slashdot.org
80+
[link text itself]: http://www.reddit.com
81+
82+
---
83+
84+
## Images
85+
86+
Here's our logo (hover to see the title text):
87+
88+
Inline-style: ![alt text](https://github.com/adam-p/markdown-here/raw/master/src/common/images/icon48.png 'Logo Title Text 1')
89+
90+
Reference-style: ![alt text][logo]
91+
92+
[logo]: https://github.com/adam-p/markdown-here/raw/master/src/common/images/icon48.png 'Logo Title Text 2'
93+
94+
---
95+
96+
## Code
97+
98+
```javascript
99+
var s = 'JavaScript syntax highlighting';
100+
alert(s);
101+
```
102+
103+
```python
104+
s = "Python syntax highlighting"
105+
print(s)
106+
```
107+
108+
```
109+
No language indicated, so no syntax highlighting.
110+
But let's throw in a <b>tag</b>.
111+
```
112+
113+
```js {2}
114+
function highlightMe() {
115+
console.log('This line can be highlighted!');
116+
}
117+
```
118+
119+
---
120+
121+
## Tables
122+
123+
Colons can be used to align columns.
124+
125+
| Tables | Are | Cool |
126+
| ------------- | :-----------: | -----: |
127+
| col 3 is | right-aligned | \$1600 |
128+
| col 2 is | centered | \$12 |
129+
| zebra stripes | are neat | \$1 |
130+
131+
There must be at least 3 dashes separating each header cell. The outer pipes (|) are optional, and you don't need to make the raw Markdown line up prettily. You can also use inline Markdown.
132+
133+
| Markdown | Less | Pretty |
134+
| -------- | --------- | ---------- |
135+
| _Still_ | `renders` | **nicely** |
136+
| 1 | 2 | 3 |
137+
138+
---
139+
140+
## Blockquotes
141+
142+
> Blockquotes are very handy in email to emulate reply text. This line is part of the same quote.
143+
144+
Quote break.
145+
146+
> This is a very long line that will still be quoted properly when it wraps. Oh boy let's keep writing to make sure this is long enough to actually wrap for everyone. Oh, you can _put_ **Markdown** into a blockquote.
147+
148+
---
149+
150+
## Inline HTML
151+
152+
<dl>
153+
<dt>Definition list</dt>
154+
<dd>Is something people use sometimes.</dd>
155+
156+
<dt>Markdown in HTML</dt>
157+
<dd>Does *not* work **very** well. Use HTML <em>tags</em>.</dd>
158+
</dl>
159+
160+
---
161+
162+
## Line Breaks
163+
164+
Here's a line for us to start with.
165+
166+
This line is separated from the one above by two newlines, so it will be a _separate paragraph_.
167+
168+
This line is also a separate paragraph, but... This line is only separated by a single newline, so it's a separate line in the _same paragraph_.
169+
170+
---
171+
172+
## Admonitions
173+
174+
:::note
175+
176+
This is a note
177+
178+
:::
179+
180+
:::tip
181+
182+
This is a tip
183+
184+
:::
185+
186+
:::important
187+
188+
This is important
189+
190+
:::
191+
192+
:::caution
193+
194+
This is a caution
195+
196+
:::
197+
198+
:::warning
199+
200+
This is a warning
201+
202+
:::

‎SpotifyAPI.Docs/docs/old.md‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
---
2+
id: old
3+
title: Old Guide
4+
sidebar_label: Old Guide
5+
---
6+
7+
You can write content using [GitHub-flavored Markdown syntax](https://github.github.com/gfm/)

‎SpotifyAPI.Docs/docs/web/examples.md‎

Lines changed: 0 additions & 7 deletions
This file was deleted.

0 commit comments

Comments
 (0)