Skip to content

Commit 6720374

Browse files
GilbNGilbN
authored
Merge pull request #525 from themepark-dev/develop
1.15
2 parents ad5a877 + 5828302 commit 6720374

File tree

217 files changed

+52209
-52072
lines changed

Some content is hidden

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

217 files changed

+52209
-52072
lines changed

‎.gitattributes

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
* text=auto

‎.github/CONTRIBUTING.md

Lines changed: 30 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -1,30 +1,30 @@
1-
# Contributing to theme.park
2-
3-
- If you want to discuss changes, you can also bring it up in our Discord server
4-
- PR's are done against the develop branch.
5-
6-
## Bug fixes
7-
8-
- When submitting bugfixes please show a before and after screenshot of the fix, and a description of what the fix does.
9-
10-
## New theme option
11-
12-
- The current variables in use can be found in any of the CSS files in `/css/theme-options/` and `/css/community-theme-options/`
13-
14-
- New community contributed theme options will be placed in the `Community Themes` category on our docs page.
15-
16-
- Community themes are not officially supported but as long as they follow the same variable structure as the other theme options it should look fine on all applications.
17-
18-
- When contributing a new option, you must have example screeenshots of the theme being used. Preferrably at least 10 with the same image size. See examples on our [docs page](https://docs.theme-park.dev/community-themes/).
19-
20-
### Specials
21-
22-
Remember to also to change the variables in the the `Specials` section even if you dont use the application the variable refers to.
23-
24-
- `--arr-queue-color` Please refrain from using an orange/yellowish color on the variable as its confusing from a UX standpoint as the "arrs" use that color range when something is wrong in the queue.
25-
26-
## New application theme
27-
28-
- When creating a new theme for an application please test multiple theme options to make sure it looks good on all options not just your favorite.
29-
30-
- The PR must contain a screenshot of all the different theme options. Optionally you can also include screenshots with the community theme options.
1+
# Contributing to theme.park
2+
3+
- If you want to discuss changes, you can also bring it up in our Discord server
4+
- PR's are done against the develop branch.
5+
6+
## Bug fixes
7+
8+
- When submitting bugfixes please show a before and after screenshot of the fix, and a description of what the fix does.
9+
10+
## New theme option
11+
12+
- The current variables in use can be found in any of the CSS files in `/css/theme-options/` and `/css/community-theme-options/`
13+
14+
- New community contributed theme options will be placed in the `Community Themes` category on our docs page.
15+
16+
- Community themes are not officially supported but as long as they follow the same variable structure as the other theme options it should look fine on all applications.
17+
18+
- When contributing a new option, you must have example screeenshots of the theme being used. Preferrably at least 10 with the same image size. See examples on our [docs page](https://docs.theme-park.dev/community-themes/).
19+
20+
### Specials
21+
22+
Remember to also to change the variables in the the `Specials` section even if you dont use the application the variable refers to.
23+
24+
- `--arr-queue-color` Please refrain from using an orange/yellowish color on the variable as its confusing from a UX standpoint as the "arrs" use that color range when something is wrong in the queue.
25+
26+
## New application theme
27+
28+
- When creating a new theme for an application please test multiple theme options to make sure it looks good on all options not just your favorite.
29+
30+
- The PR must contain a screenshot of all the different theme options. Optionally you can also include screenshots with the community theme options.

‎.github/FUNDING.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
1-
# These are supported funding model platforms
2-
3-
github: GilbN
1+
# These are supported funding model platforms
2+
3+
github: GilbN

‎.github/ISSUE_TEMPLATE/bug_report.md

Lines changed: 51 additions & 51 deletions
Original file line numberDiff line numberDiff line change
@@ -1,51 +1,51 @@
1-
---
2-
name: Bug report
3-
about: Create a report to help us improve
4-
title: ''
5-
labels: 'bug'
6-
assignees: ''
7-
8-
---
9-
10-
**Describe the bug**
11-
A clear and concise description of what the bug is.
12-
13-
**Theme Install Method** (Don't skip)
14-
- Docker run / Compose Config
15-
- If using docker mods share your COMPLETE container logs..
16-
- Webserver subfilter Config
17-
- Stylus Config
18-
19-
**Application Info** (Don't skip)
20-
- Version
21-
- Branch
22-
- Container
23-
- Logs
24-
25-
**To Reproduce**
26-
Steps to reproduce the behavior:
27-
1. Go to '...'
28-
2. Click on '....'
29-
3. Scroll down to '....'
30-
4. See error
31-
32-
**Expected behavior**
33-
A clear and concise description of what you expected to happen.
34-
35-
**Screenshots**
36-
If applicable, add screenshots to help explain your problem.
37-
38-
39-
**Desktop (If applicable) (please complete the following information):**
40-
- OS: [e.g. iOS]
41-
- Browser [e.g. chrome, safari]
42-
- Version [e.g. 22]
43-
44-
**Smartphone (If applicable) (please complete the following information):**
45-
- Device: [e.g. iPhone6]
46-
- OS: [e.g. iOS8.1]
47-
- Browser [e.g. stock browser, safari]
48-
- Version [e.g. 22]
49-
50-
**Additional context**
51-
Add any other context about the problem here.
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: 'bug'
6+
assignees: ''
7+
8+
---
9+
10+
**Describe the bug**
11+
A clear and concise description of what the bug is.
12+
13+
**Theme Install Method** (Don't skip)
14+
- Docker run / Compose Config
15+
- If using docker mods share your COMPLETE container logs..
16+
- Webserver subfilter Config
17+
- Stylus Config
18+
19+
**Application Info** (Don't skip)
20+
- Version
21+
- Branch
22+
- Container
23+
- Logs
24+
25+
**To Reproduce**
26+
Steps to reproduce the behavior:
27+
1. Go to '...'
28+
2. Click on '....'
29+
3. Scroll down to '....'
30+
4. See error
31+
32+
**Expected behavior**
33+
A clear and concise description of what you expected to happen.
34+
35+
**Screenshots**
36+
If applicable, add screenshots to help explain your problem.
37+
38+
39+
**Desktop (If applicable) (please complete the following information):**
40+
- OS: [e.g. iOS]
41+
- Browser [e.g. chrome, safari]
42+
- Version [e.g. 22]
43+
44+
**Smartphone (If applicable) (please complete the following information):**
45+
- Device: [e.g. iPhone6]
46+
- OS: [e.g. iOS8.1]
47+
- Browser [e.g. stock browser, safari]
48+
- Version [e.g. 22]
49+
50+
**Additional context**
51+
Add any other context about the problem here.

‎.github/pull_request_template.md

Lines changed: 39 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -1,40 +1,40 @@
1-
<!--- Provide a general summary of your changes in the Title above -->
2-
3-
[themeparkurl]: https://theme-park.dev
4-
[![theme-park.dev](https://raw.githubusercontent.com/GilbN/theme.park/master/banners/tp_banner.png)][themeparkurl]
5-
6-
7-
<!--- Before submitting a pull request please check the following -->
8-
9-
<!--- If this is a fix for a typo (in code, documentation, or the README) please file an issue and let us sort it out. We do not need a PR -->
10-
<!--- Ask yourself if this modification is something the whole userbase will benefit from, if this is a specific change for corner case functionality/styling please look at making an addon instead. https://docs.theme-park.dev/themes/addons/sonarr/ -->
11-
<!--- That if the PR is addressing an existing issue include, closes #<issue number> , in the body of the PR commit message -->
12-
<!--- You have included links to any files / patches etc your PR may be using in the body of the PR commit message -->
13-
14-
------------------------------
15-
16-
- [ ] I have read the [contributing](https://github.com/GilbN/theme.park/blob/master/.github/CONTRIBUTING.md) guideline and understand that I have made the correct modifications
17-
18-
- PR's are done against the develop branch.
19-
------------------------------
20-
21-
<!--- We welcome all PR’s though this doesn’t guarantee it will be accepted. -->
22-
23-
## Bug fixes
24-
25-
- When submitting bugfixes please show a before and after screenshot of the fix, and a description of what the fix does.
26-
27-
## Description:
28-
<!--- Describe your changes in detail -->
29-
<!--- Add before and after screenshots of your changes -->
30-
31-
## Benefits of this PR and context:
32-
<!--- Please explain why we should accept this PR. If this fixes an outstanding bug, please reference the issue # -->
33-
34-
## How Has This Been Tested?
35-
<!--- Please describe in detail how you tested your changes. -->
36-
<!--- Include details of your testing environment, and the tests you ran to -->
37-
<!--- see how your change affects other areas of the code, etc. -->
38-
39-
## Source / References:
1+
<!--- Provide a general summary of your changes in the Title above -->
2+
3+
[themeparkurl]: https://theme-park.dev
4+
[![theme-park.dev](https://raw.githubusercontent.com/GilbN/theme.park/master/banners/tp_banner.png)][themeparkurl]
5+
6+
7+
<!--- Before submitting a pull request please check the following -->
8+
9+
<!--- If this is a fix for a typo (in code, documentation, or the README) please file an issue and let us sort it out. We do not need a PR -->
10+
<!--- Ask yourself if this modification is something the whole userbase will benefit from, if this is a specific change for corner case functionality/styling please look at making an addon instead. https://docs.theme-park.dev/themes/addons/sonarr/ -->
11+
<!--- That if the PR is addressing an existing issue include, closes #<issue number> , in the body of the PR commit message -->
12+
<!--- You have included links to any files / patches etc your PR may be using in the body of the PR commit message -->
13+
14+
------------------------------
15+
16+
- [ ] I have read the [contributing](https://github.com/GilbN/theme.park/blob/master/.github/CONTRIBUTING.md) guideline and understand that I have made the correct modifications
17+
18+
- PR's are done against the develop branch.
19+
------------------------------
20+
21+
<!--- We welcome all PR’s though this doesn’t guarantee it will be accepted. -->
22+
23+
## Bug fixes
24+
25+
- When submitting bugfixes please show a before and after screenshot of the fix, and a description of what the fix does.
26+
27+
## Description:
28+
<!--- Describe your changes in detail -->
29+
<!--- Add before and after screenshots of your changes -->
30+
31+
## Benefits of this PR and context:
32+
<!--- Please explain why we should accept this PR. If this fixes an outstanding bug, please reference the issue # -->
33+
34+
## How Has This Been Tested?
35+
<!--- Please describe in detail how you tested your changes. -->
36+
<!--- Include details of your testing environment, and the tests you ran to -->
37+
<!--- see how your change affects other areas of the code, etc. -->
38+
39+
## Source / References:
4040
<!--- Please include any forum posts/github links relevant to the PR -->

0 commit comments

Comments
 (0)