Skip to content

Commit

Permalink
Merge pull request #525 from themepark-dev/develop
Browse files Browse the repository at this point in the history
1.15
  • Loading branch information
GilbN authored Dec 17, 2023
2 parents ad5a877 + 5828302 commit 6720374
Show file tree
Hide file tree
Showing 217 changed files with 52,209 additions and 52,072 deletions.
1 change: 1 addition & 0 deletions .gitattributes
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
* text=auto
60 changes: 30 additions & 30 deletions .github/CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -1,30 +1,30 @@
# Contributing to theme.park

- If you want to discuss changes, you can also bring it up in our Discord server
- PR's are done against the develop branch.

## Bug fixes

- When submitting bugfixes please show a before and after screenshot of the fix, and a description of what the fix does.

## New theme option

- The current variables in use can be found in any of the CSS files in `/css/theme-options/` and `/css/community-theme-options/`

- New community contributed theme options will be placed in the `Community Themes` category on our docs page.

- 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.

- 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/).

### Specials

Remember to also to change the variables in the the `Specials` section even if you dont use the application the variable refers to.

- `--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.

## New application theme

- 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.

- The PR must contain a screenshot of all the different theme options. Optionally you can also include screenshots with the community theme options.
# Contributing to theme.park

- If you want to discuss changes, you can also bring it up in our Discord server
- PR's are done against the develop branch.

## Bug fixes

- When submitting bugfixes please show a before and after screenshot of the fix, and a description of what the fix does.

## New theme option

- The current variables in use can be found in any of the CSS files in `/css/theme-options/` and `/css/community-theme-options/`

- New community contributed theme options will be placed in the `Community Themes` category on our docs page.

- 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.

- 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/).

### Specials

Remember to also to change the variables in the the `Specials` section even if you dont use the application the variable refers to.

- `--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.

## New application theme

- 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.

- The PR must contain a screenshot of all the different theme options. Optionally you can also include screenshots with the community theme options.
6 changes: 3 additions & 3 deletions .github/FUNDING.yml
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
# These are supported funding model platforms

github: GilbN
# These are supported funding model platforms

github: GilbN
102 changes: 51 additions & 51 deletions .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -1,51 +1,51 @@
---
name: Bug report
about: Create a report to help us improve
title: ''
labels: 'bug'
assignees: ''

---

**Describe the bug**
A clear and concise description of what the bug is.

**Theme Install Method** (Don't skip)
- Docker run / Compose Config
- If using docker mods share your COMPLETE container logs..
- Webserver subfilter Config
- Stylus Config

**Application Info** (Don't skip)
- Version
- Branch
- Container
- Logs

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.


**Desktop (If applicable) (please complete the following information):**
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]

**Smartphone (If applicable) (please complete the following information):**
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]

**Additional context**
Add any other context about the problem here.
---
name: Bug report
about: Create a report to help us improve
title: ''
labels: 'bug'
assignees: ''

---

**Describe the bug**
A clear and concise description of what the bug is.

**Theme Install Method** (Don't skip)
- Docker run / Compose Config
- If using docker mods share your COMPLETE container logs..
- Webserver subfilter Config
- Stylus Config

**Application Info** (Don't skip)
- Version
- Branch
- Container
- Logs

**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behavior**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.


**Desktop (If applicable) (please complete the following information):**
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]

**Smartphone (If applicable) (please complete the following information):**
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]

**Additional context**
Add any other context about the problem here.
78 changes: 39 additions & 39 deletions .github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -1,40 +1,40 @@
<!--- Provide a general summary of your changes in the Title above -->

[themeparkurl]: https://theme-park.dev
[![theme-park.dev](https://raw.githubusercontent.com/GilbN/theme.park/master/banners/tp_banner.png)][themeparkurl]


<!--- Before submitting a pull request please check the following -->

<!--- 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 -->
<!--- 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/ -->
<!--- That if the PR is addressing an existing issue include, closes #<issue number> , in the body of the PR commit message -->
<!--- You have included links to any files / patches etc your PR may be using in the body of the PR commit message -->

------------------------------

- [ ] 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

- PR's are done against the develop branch.
------------------------------

<!--- We welcome all PR’s though this doesn’t guarantee it will be accepted. -->

## Bug fixes

- When submitting bugfixes please show a before and after screenshot of the fix, and a description of what the fix does.

## Description:
<!--- Describe your changes in detail -->
<!--- Add before and after screenshots of your changes -->

## Benefits of this PR and context:
<!--- Please explain why we should accept this PR. If this fixes an outstanding bug, please reference the issue # -->

## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->

## Source / References:
<!--- Provide a general summary of your changes in the Title above -->

[themeparkurl]: https://theme-park.dev
[![theme-park.dev](https://raw.githubusercontent.com/GilbN/theme.park/master/banners/tp_banner.png)][themeparkurl]


<!--- Before submitting a pull request please check the following -->

<!--- 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 -->
<!--- 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/ -->
<!--- That if the PR is addressing an existing issue include, closes #<issue number> , in the body of the PR commit message -->
<!--- You have included links to any files / patches etc your PR may be using in the body of the PR commit message -->

------------------------------

- [ ] 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

- PR's are done against the develop branch.
------------------------------

<!--- We welcome all PR’s though this doesn’t guarantee it will be accepted. -->

## Bug fixes

- When submitting bugfixes please show a before and after screenshot of the fix, and a description of what the fix does.

## Description:
<!--- Describe your changes in detail -->
<!--- Add before and after screenshots of your changes -->

## Benefits of this PR and context:
<!--- Please explain why we should accept this PR. If this fixes an outstanding bug, please reference the issue # -->

## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran to -->
<!--- see how your change affects other areas of the code, etc. -->

## Source / References:
<!--- Please include any forum posts/github links relevant to the PR -->
Loading

0 comments on commit 6720374

Please sign in to comment.