Browse Source

Remove JS and re-arange files

* Remove Javascript
* Move files about
* Add Makefile
* Add Privacy & ToS
* Add favicon
* Make index.html static
* Add requirements.txt
Juan Canham 1 month ago
34 changed files with 211 additions and 303 deletions
  1. +1
  2. +0
  3. +1
  4. +39
  5. +66
  6. +7
  7. +51
  8. BIN
  9. +0
  10. +0
  11. +0
  12. +0
  13. +21
  14. +0
  15. BIN
  16. BIN
  17. BIN
  18. +24
  19. +1
  20. +0
  21. +0
  22. +0
  23. +0
  24. +0
  25. +0
  26. +0
  27. +0
  28. +0
  29. +0
  30. +0
  31. +0
  32. +0
  33. +0
  34. +0

+ 1
- 2
.gitignore View File

@@ -1,2 +1 @@

+ 0
- 172 View File

@@ -1,172 +0,0 @@
# Contributing to simple-dash

Looking to contribute something to simple-dash? **Here's how you can help.**

Please take a moment to review this document in order to make the contribution
process easy and effective for everyone involved.

Following these guidelines helps to communicate that you respect the time of
the developers managing and developing this open source project. In return,
they should reciprocate that respect in addressing your issue or assessing
patches and features.

## Using the issue tracker

The [issue tracker]( is
the preferred channel for [bug reports](#bug-reports), [features requests](#feature-requests)
and [submitting pull requests](#pull-requests), but please respect the following

* Please **do not** derail or troll issues. Keep the discussion on topic and
respect the opinions of others.

## Issues and labels

Our bug tracker utilizes several labels to help organize and identify issues. Here's what they represent and how we use them:

- `bug` - Issues for a potential bug in simple-dash.
- `docs` - Issues for improving or updating our documentation.
- `feature` - Issues asking for a new feature to be added, or an existing one to be extended or modified.
- `help wanted` - Issues we need or would love help from the community to resolve.
- `question` - General purpose question about simple-dash.

For a complete look at our labels, see the [project labels page](

## Bug reports

A bug is a _demonstrable problem_ that is caused by the code in the repository.
Good bug reports are extremely helpful, so thanks!

Guidelines for bug reports:

0. **Validate and lint your code** — [validate your HTML](
and [lint your HTML]( to ensure your
problem isn't caused by a simple error in your own code.

1. **Use the GitHub issue search** — check if the issue has already been

2. **Check if the issue has been fixed** — try to reproduce it using the
latest `master` or development branch in the repository.

3. **Isolate the problem** — ideally create a live example.
[This jsfiddle]( is a helpful tools.

A good bug report shouldn't leave others needing to chase you up for more
information. Please try to be as detailed as possible in your report. What is
your environment? What steps will reproduce the issue? What browser(s) and OS
experience the problem? Do other browsers show the bug differently? What
would you expect to be the outcome? All these details will help people to fix
any potential bugs.


> Short and descriptive example bug report title
> A summary of the issue and the browser/OS environment in which it occurs. If
> suitable, include the steps required to reproduce the bug.
> 1. This is the first step
> 2. This is the second step
> 3. Further steps, etc.
> `<url>` - a link to the reduced test case
> Any other information you want to share that is relevant to the issue being
> reported. This might include the lines of code that you have identified as
> causing the bug, and potential solutions (and your opinions on their
> merits).

## Feature requests

Feature requests are welcome. But take a moment to find out whether your idea
fits with the scope and aims of the project. It's up to *you* to make a strong
case to convince the project's developers of the merits of this feature. Please
provide as much detail and context as possible.

## Pull requests

Good pull requests—patches, improvements, new features—are a fantastic
help. They should remain focused in scope and avoid containing unrelated

**Please ask first** before embarking on any significant pull request (e.g.
implementing features, refactoring code, porting to a different language),
otherwise you risk spending a lot of time working on something that the
project's developers might not want to merge into the project.

Please adhere to the [coding guidelines](#code-guidelines) used throughout the
project (indentation, accurate comments, etc.) and any other requirements
(such as test coverage).

Adhering to the following process is the best way to get your work
included in the project:

1. [Fork]( the project, clone your fork,
and configure the remotes:

# Clone your fork of the repo into the current directory
git clone<your-username>/simple-dash.git
# Navigate to the newly cloned directory
cd simple-dash
# Assign the original repo to a remote called "upstream"
git remote add upstream

2. If you cloned a while ago, get the latest changes from upstream:

git checkout master
git pull upstream master

3. Create a new topic branch (off the main project development branch) to
contain your feature, change, or fix:

git checkout -b <topic-branch-name>

4. Commit your changes in logical chunks. Please adhere to these [git commit
message guidelines](
or your code is unlikely be merged into the main project. Use Git's
[interactive rebase](
feature to tidy up your commits before making them public.

5. Locally merge (or rebase) the upstream development branch into your topic branch:

git pull [--rebase] upstream master

6. Push your topic branch up to your fork:

git push origin <topic-branch-name>

7. [Open a Pull Request](
with a clear title and description against the `master` branch.

**IMPORTANT**: By submitting a patch, you agree to allow the project owners to
license your work under the terms of the [MIT License]( (if it
includes code changes).

## Code guidelines

- Readability
- Need semicolons
- strict mode
- "Attractive"

## License

By contributing your code, you agree to license your contribution under the [MIT License](

+ 1
- 1 View File

@@ -1,6 +1,6 @@
MIT License

Copyright (c) 2017 kutyla-philipp
Copyright (c) 2017 Juan Canham

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

+ 39
- 0
Makefile View File

@@ -0,0 +1,39 @@
.PHONY: help all local deploy install clean build test sync post-test
linkchecker=linkchecker --check-extern

@echo 'all: local deploy'
@echo 'local: install clean build'
@echo 'deploy: test sync post-test'

all: local deploy
local: install build
deploy: test sync post-test

pip install -r requirements.txt

rm -r dist/* || true

build: clean
cp -v *.html *.jpg *.ico dist/
cp -rv css/ webfonts/ dist/
for file in ToS Privacy; do markdown_py $${file}.md > dist/$${file} ; done

$(linkchecker) dist/index.html

rsync -vr --delete dist/ $(TARGET)

$(linkchecker) https://$(SITENAME)
wget http://${SITENAME} -O /dev/null

+ 66
- 0 View File

@@ -0,0 +1,66 @@
# Privacy Policy

## Policy

Your privacy is important to Me. It is my policy to respect your privacy regarding any information I collect from you across my websites,, and other sites I own (*, * &

By using my websites, you hereby consent to our Privacy Policy and agree to its terms.

I only ask for personal information when I need it to provide a service to you. I collect it by fair and lawful means, with your knowledge and consent.

I only retain collected information for as long as necessary to:

* Provide, operate, and maintain my websites
* Improve and personalize my websites
* Understand and analyze how you use my websites
* Communicate with you directly, to provide you with updates and other information relating to the website

What data I store, I'll protect within commercially acceptable means to prevent loss and theft, as well as unauthorised access, disclosure, copying, use or modification.

Personally identifying information is only shared with third parties:

* as required to operate the site (such as authentication (if you are using this feature))
* when required to by law

Personally identifying information is only shared publicly as per your personal controls.

If you have any questions about how I handle user data and personal information, feel free to contact me.

## Types of information stored

### Cookies

Like any other website, Website Name uses ‘cookies'. These cookies are used to store information including visitors' preferences, and the pages on the website that the visitor accessed or visited. The information is used to optimize the users' experience by customizing our web page content.

You can choose to disable cookies through your individual browser options. To know more detailed information about cookie management with specific web browsers, it can be found at the browsers' respective websites.

### Logs

My websites follows a standard procedure of using log files. These files log visitors when they visit websites. All hosting companies do this and a part of hosting services' analytics. The information collected by log files include internet protocol (IP) addresses, browser type, Internet Service Provider (ISP), date and time stamp, referring/exit pages, and possibly the number of clicks. These are not linked to any information that is personally identifiable. The purpose of the information is for analyzing trends, administering the site, and gathering technical demographic information.

## Modification

If I revise the Terms of Service I will attempt give notice to all users via any registered emails at least 7 days prior to changes.
If you are unhappy with any changes, all account data will be availible for export.

## Specific Laws

### CCPA Privacy Policy (Do Not Sell My Personal Information)

Under the CCPA, among other rights, California consumers have the right to:

* Request that a business that collects a consumer's personal data disclose the categories and specific pieces of personal data that a business has collected about consumers.
* Request that a business delete any personal data about the consumer that a business has collected. - This can be done by deleting your account in any of the services

To make a request, please contact me

### GDPR Privacy Policy (Data Protection Rights)

I would like to make sure you are fully aware of all of your data protection rights. Every user is entitled to the following:

* The right to access – You have the right to request copies of your personal data.
* The right to data portability – You have the right to request that I transfer the data that I have collected to another organization, or directly to you, under certain conditions.
* The right to rectification – You have the right to request that I correct any information you believe is inaccurate. You also have the right to request that I complete the information you believe is incomplete.
* The right to erasure – You have the right to request that I erase your personal data, under certain conditions. - This can be done by deleting your account in any of the services

To make a request, please contact me

+ 7
- 14 View File

@@ -1,23 +1,16 @@
[![Mentioned in Awesome-Selfhosted](](
# simple-dash

Try the Demo here:
# simpler-dash

A simple, fully responsive Dashboard to forward to the services of your choice! Ideal for Desktop and mobile usage!
Add all of your services, whether you host them yourself or not and display them as neat Icons from the FontAwesome libary.
simple-dash is made to be as simple and minimalistic as possible. (The goal was to create a dashboard even my mom could use!) :)
Based on:
simple-dash is made to be as simple and minimalistic as possible.

Now without Javascript

Based on:

This project uses:
- Font Awesome
- Trianglify

## Screenshots
![Homepage Desktop](example_img/homepage-desktop.jpg?raw=true)
![Homepage Mobile](example_img/homepage-mobile.jpg?raw=true)

## To Use
Copy the config.sample.json file and rename to config.json. Be sure to update the fields as you see appropriate.
Update index.html manually. Choose icons from [Font Awesome](

## Configure Homepage
- 'items' => The menu will scale to the amount of items you want to display. Insert any link you'd like, or {{cur}} for the current URL of the page. Choose icons from [Font Awesome](

+ 51
- 0 View File

@@ -0,0 +1,51 @@
# Websites Terms and Conditions of Use

0. Tl;DR
Use my site, if you want, but don't sue me.

1. Terms
By accessing My Websites (, & *, you are agreeing to be bound by these Websites Terms and Conditions of Use and agree that you are responsible for the agreement with any applicable local laws.

2. Use License
Permission is granted to temporarily download one copy of the materials on My Websites for personal, non-commercial transitory viewing only. This is the grant of a license, not a transfer of title.
Additionally almost all of My Websites are availible under an open source license

3. Disclaimer
All the materials on My Websites are provided “as is”.
I makes no warranties, may it be expressed or implied, therefore negates all other warranties.
Furthermore, I does not make any representations concerning the accuracy or reliability of the use of the materials on any sites linked to my websites.

4. Limitations
I will not be hold accountable for any damages that will arise with the use or inability to use the materials on My Websites.
Some jurisdiction does not allow limitations on implied warranties or limitations of liability for incidental damages, these limitations may not apply to you.

5. Revisions and Errata
The materials appearing on My Websites may include technical, typographical, or photographic errors.
I will not promise that any of the materials in my websites are accurate, complete, or current.
I may change the materials contained on its Websites at any time without notice.
I does not make any commitment to update the materials.

6. Links
I has not reviewed all of the sites linked to its Websites and is not responsible for the contents of any such linked site.
The presence of any link does not imply endorsement by me of the site.
The use of any linked website is at the user's own risk.

7. Site Terms of Use Modifications
If I revise the Terms of Service I will attempt give notice to all users via any registered emails at least 7 days prior to changes.
By using my websites, you are agreeing to be bound by the current version of these Terms and Conditions of Use.
If you are unhappy with any changes, all account data will be availible for export

8. Governing Law
Any claim related to My Websites shall be governed by the laws of the United Kingdom without regards to its conflict of law provisions.

9. Termination
I reserve the right to delete your data or account as I see fit.
Prior to deleting an account, I will attempt give users 7 days notices via a registered email or other communication method.
When possible all data will be availible for export

10. Modification of Public Data
I reserve the right to modify any publicly displayed content on My Websites.

11. Modification of Private Data
I connit to only modifying private date, such to fix bugs on My Websites or to delete data to comply with legal requirements

background.jpg View File

Before After
Width: 1280  |  Height: 854  |  Size: 1006KB

+ 0
- 1
File diff suppressed because it is too large
View File

+ 0
- 20
config.json View File

@@ -1,20 +0,0 @@
"title" : "Simple Dash",
"items" : [
"alt" : "Github",
"icon" : "fab fa-github",
"link" : ""
"alt" : "Twitter",
"icon" : "fab fa-twitter",
"link" : ""
"alt" : "Docker Hub",
"icon" : "fab fa-docker",
"link" : ""

+ 0
- 20
config.sample.json View File

@@ -1,20 +0,0 @@
"title" : "Your Homepage Title",
"items" : [
"alt" : "Github",
"icon" : "fab fa-github",
"link" : ""
"alt" : "Twitter",
"icon" : "fab fa-twitter",
"link" : ""
"alt" : "Docker Hub",
"icon" : "fab fa-docker",
"link" : ""

common/css/fontawesome-all.min.css → css/fontawesome-all.min.css View File

common/css/main.css → css/main.css View File

@@ -2,22 +2,20 @@ html, body {
height: 100%;
width: 100%;
margin: 0;
text-rendering: optimizeLegibility;
font-family: sans-serif;
text-align: center;
background-image: url('../background.jpg');
background-repeat: no-repeat;
background-size: cover;
body {
z-index: 1;
background-position: center;
background-attachment: fixed;

.github-corner {
opacity: 0.4;
.github-corner:hover {
opacity: 1;

#wrapper {
height: 100%;
height: 92%;
display: grid;
#itemlist {
@@ -32,7 +30,7 @@ body {
@media only screen and (min-width: 800px) {
#itemlist {
grid-template-columns: repeat(6, 1fr);
grid-template-columns: repeat(4, 1fr);

@@ -46,9 +44,6 @@ body {
margin: 0 auto;

/* link colors */
#itemlist a {
color: #fff;
@@ -56,3 +51,16 @@ body {
#itemlist a:hover {
color: #c4c4c4;

#footer {
position: absolute;
bottom: 0;
width: 100%;

p {color: Cyan;}

a {
color: LightCyan;

+ 0
- 0
dist/.gitkeep View File

example_img/homepage-desktop.jpg View File

Before After
Width: 1280  |  Height: 720  |  Size: 182KB

example_img/homepage-mobile.jpg View File

Before After
Width: 720  |  Height: 1280  |  Size: 149KB

favicon.ico View File

Before After

+ 24
- 60
index.html View File

@@ -1,75 +1,39 @@
<!DOCTYPE html>

<html xmlns="">
<title>Juan Canham Services</title>

<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no">
<link rel="stylesheet" type="text/css" href="common/css/fontawesome-all.min.css" />
<link rel="stylesheet" type="text/css" href="common/css/main.css" />
<meta charset="utf-8"/>
<link rel="stylesheet" type="text/css" href="css/fontawesome-all.min.css" />
<link rel="stylesheet" type="text/css" href="css/main.css" />
<link rel="shortcut icon" type="image/x-icon" href="favicon.ico" />

<body id="homepage">

<!-- Fork me on GitHub -->
<a href="" class="github-corner" aria-label="View source on GitHub"><svg width="50" height="50" viewBox="0 0 250 250" style="fill:#151513; color:#fff; position: absolute; top: 0; border: 0; right: 0;" aria-hidden="true"><path d="M0,0 L115,115 L130,115 L142,142 L250,250 L250,0 Z"></path><path d="M128.3,109.0 C113.8,99.7 119.0,89.6 119.0,89.6 C122.0,82.7 120.5,78.6 120.5,78.6 C119.2,72.0 123.4,76.3 123.4,76.3 C127.3,80.9 125.5,87.3 125.5,87.3 C122.9,97.6 130.6,101.9 134.4,103.2" fill="currentColor" style="transform-origin: 130px 106px;" class="octo-arm"></path><path d="M115.0,115.0 C114.9,115.1 118.7,116.5 119.8,115.4 L133.7,101.6 C136.9,99.2 139.9,98.4 142.2,98.6 C133.8,88.0 127.5,74.4 143.8,58.0 C148.5,53.4 154.0,51.2 159.7,51.0 C160.3,49.4 163.2,43.6 171.4,40.1 C171.4,40.1 176.1,42.5 178.8,56.2 C183.1,58.6 187.2,61.8 190.9,65.4 C194.5,69.0 197.7,73.2 200.1,77.6 C213.8,80.2 216.3,84.9 216.3,84.9 C212.7,93.1 206.9,96.0 205.4,96.6 C205.1,102.4 203.0,107.8 198.3,112.5 C181.9,128.9 168.3,122.5 157.7,114.1 C157.9,116.9 156.7,120.9 152.7,124.9 L141.0,136.5 C139.8,137.7 141.6,141.9 141.8,141.8 Z" fill="currentColor" class="octo-body"></path></svg></a><style>.github-corner:hover .octo-arm{animation:octocat-wave 560ms ease-in-out}@keyframes octocat-wave{0%,100%{transform:rotate(0)}20%,60%{transform:rotate(-25deg)}40%,80%{transform:rotate(10deg)}}@media (max-width:500px){.github-corner:hover .octo-arm{animation:none}.github-corner .octo-arm{animation:octocat-wave 560ms ease-in-out}}</style>
<!-- end Fork me on GitHub -->

<div id="wrapper">
<div id="itemlist">
<a title="Loading..."><i class="fa-spin fas fa-spinner fa-fw"></i></a>
<a href="" title="CV"><i class="fa fa-address-card fa-fw"></i></a>
<a href="" title="Gitea"><i class="fab fa-git-alt fa-fw"></i></a>
<a href="" title="NextCloud"><i class="fa fa-cloud fa-fw"></i></a>
<!-- <a href="" title="Drone (CI)"><i class="fa fa-robot fa-fw"></i></a> -->
<a href="" title="Github"><i class="fab fa-github fa-fw"></i></a>

<script src="common/js/trianglify.min.js"></script>
var request = new XMLHttpRequest();
request.overrideMimeType("application/json");"GET", 'config.json');
request.onload = function () {
if (request.status >= 200 && request.status < 400) {
var config = JSON.parse(this.response);
document.title = config.title;

var itemlistHTML = '';
for (var i = 0; i < config.items.length; i++) {
var item = config.items[i];
itemlistHTML += '<a href="''" title="'+item.alt+'"><i class="'+item.icon+' fa-fw"></i></a>';
document.getElementById("itemlist").innerHTML = itemlistHTML;
} else {
var error_text = "Error: "+request.status;
document.title = error_text;

function addTriangleTo(target) {
var dimensions = target.getClientRects()[0];
var pattern = Trianglify({
width: dimensions.width,
height: dimensions.height
});['background-image'] = 'url(' + pattern.png() + ')';['background-size'] = 'cover';['-webkit-background-size'] = 'cover';['-moz-background-size'] = 'cover';['-o-background-size'] = 'cover';

var resizeTimer;
window.addEventListener("resize", function () {
resizeTimer = setTimeout(function() {
}, 400);

<footer class="footer">
<div class="container">
<a href="Privacy">Privacy Policy</a>
<a href="ToS">Terms of Service</a>
<a href="">Source Code</a>
<a href="">image</a>
by <a href="">@eberhardgross</a>

+ 1
- 0
requirements.txt View File

@@ -0,0 +1 @@

common/webfonts/fa-brands-400.eot → webfonts/fa-brands-400.eot View File

common/webfonts/fa-brands-400.svg → webfonts/fa-brands-400.svg View File

common/webfonts/fa-brands-400.ttf → webfonts/fa-brands-400.ttf View File

common/webfonts/fa-brands-400.woff → webfonts/fa-brands-400.woff View File

common/webfonts/fa-brands-400.woff2 → webfonts/fa-brands-400.woff2 View File

common/webfonts/fa-regular-400.eot → webfonts/fa-regular-400.eot View File

common/webfonts/fa-regular-400.svg → webfonts/fa-regular-400.svg View File

common/webfonts/fa-regular-400.ttf → webfonts/fa-regular-400.ttf View File

common/webfonts/fa-regular-400.woff → webfonts/fa-regular-400.woff View File

common/webfonts/fa-regular-400.woff2 → webfonts/fa-regular-400.woff2 View File

common/webfonts/fa-solid-900.eot → webfonts/fa-solid-900.eot View File

common/webfonts/fa-solid-900.svg → webfonts/fa-solid-900.svg View File

common/webfonts/fa-solid-900.ttf → webfonts/fa-solid-900.ttf View File

common/webfonts/fa-solid-900.woff → webfonts/fa-solid-900.woff View File

common/webfonts/fa-solid-900.woff2 → webfonts/fa-solid-900.woff2 View File