Revert "Reformat frontend files"

This reverts commit 366e983.

Author: Irae Hueck Costa

.github/workflows/deploy.yml

@@ -11,6 +11,7 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
+
       - name: Set up WARP
         uses: fscarmen/warp-on-actions@v1.1
 

README.md

@@ -52,6 +52,7 @@ You will need a redis server at localhost and default port.
 
 If you want to self-host consult here: https://github.com/ihucos/counter.dev-selfhost
 
+
 ## Developing the blog
 
 The blog is based on [pelican](https://blog.getpelican.com/). The templates are in the `templates/blog` directory. Articles in the `posts` directory. To autogenerate the blog to the folder `static/blog` run `make blog`. The blog is autogenerated at every deploy.
@@ -62,7 +63,7 @@ The blog is based on [pelican](https://blog.getpelican.com/). The templates are
 
 I don't know. See https://github.com/ihucos/counter.dev/issues/71
 
-With the information that is possible for me to gather, it seems that due to the _ePrivacy Directive_ all SaaS Web Analytics - including counter.dev - needs consent. Even though most providers might claim the contrary. There is a proposal for a [new ePrivacy Regulation](https://digital-strategy.ec.europa.eu/en/policies/eprivacy-regulation) that could fix that.
+With the information that is possible for me to gather, it seems that due to the *ePrivacy Directive* all SaaS Web Analytics - including counter.dev - needs consent. Even though most providers might claim the contrary. There is a proposal for a [new ePrivacy Regulation](https://digital-strategy.ec.europa.eu/en/policies/eprivacy-regulation) that could fix that.
 
 ## Contributors
 

content/help/index.md

@@ -2,18 +2,18 @@
 
 - Integration
 
-  - General integration guide
+    - General integration guide
 
-    - {% filter helplink %}integration.md{% endfilter %}
+        - {% filter helplink %}integration.md{% endfilter %}
 
-  - Integrating counter.dev in different platforms
+    - Integrating counter.dev in different platforms
 
-    - {% filter helplink %}wordpress.md{% endfilter %}
+        - {% filter helplink %}wordpress.md{% endfilter %}
 
-    - {% filter helplink %}shopify.md{% endfilter %}
+        - {% filter helplink %}shopify.md{% endfilter %}
 
-    - {% filter helplink %}squarespace.md{% endfilter %}
+        - {% filter helplink %}squarespace.md{% endfilter %}
 
-    - {% filter helplink %}wix.md{% endfilter %}
+        - {% filter helplink %}wix.md{% endfilter %}
 
-    - {% filter helplink %}weebly.md{% endfilter %}
+        - {% filter helplink %}weebly.md{% endfilter %}

content/help/integration.md

@@ -21,7 +21,7 @@ To integrate the tracking script into your website, follow these steps:
 
 1. Log in to your account and copy the tracking code.
 2. Paste the tracking code just before the closing `</head>` tag in the HTML
-   code of your website.
+code of your website.
 3. Save the changes to your website.
 
 Once you have completed the above steps, the tracking script will start

content/help/shopify.md

@@ -5,30 +5,30 @@ track visitors and gain valuable insights into your store's performance. Follow
 the steps below to integrate Counter.dev into your Shopify store:
 
 1. Log in to your Shopify store and navigate to the Online Store > Themes
-   section.
+section.
 
 2. Click on the Actions button for the theme you want to edit and select Edit
-   code.
+code.
 
 3. In the theme editor, click on the theme.liquid file from the left-hand side
-   navigation menu to open it.
+navigation menu to open it.
 
 4. Find the closing `</head>` tag in the theme.liquid file.
 
 5. Copy the Counter.dev tracking script provided in your Counter.dev account
-   and paste it just before the closing `</head>` tag.
+and paste it just before the closing `</head>` tag.
 
 6. Save the changes to the theme.liquid file.
 
 7. Clear any caching plugins you may have installed on your Shopify store.
 
 8. Verify that the tracking code has been properly installed by visiting your
-   store and opening the developer console (usually done by pressing F12). The
-   console should not display any errors and the network tab should show that the
-   Counter.dev script has been loaded.
+store and opening the developer console (usually done by pressing F12). The
+console should not display any errors and the network tab should show that the
+Counter.dev script has been loaded.
 
 9. Log in to your Counter.dev account and check the analytics dashboard to see
-   if your Shopify store is being tracked.
+if your Shopify store is being tracked.
 
 Congratulations! You have successfully integrated the Counter.dev tracking
 script into your Shopify store and can now start tracking visitors and

content/help/squarespace.md

@@ -17,12 +17,12 @@ started:
 6. Save the changes to the Header section.
 
 7. Verify that the tracking code has been properly installed by visiting your
-   website and opening the developer console (usually done by pressing F12). The
-   console should not display any errors and the network tab should show that the
-   Counter.dev script has been loaded.
+website and opening the developer console (usually done by pressing F12). The
+console should not display any errors and the network tab should show that the
+Counter.dev script has been loaded.
 
 8. Log in to your Counter.dev account and check the analytics dashboard to see
-   if your Squarespace website is being tracked.
+if your Squarespace website is being tracked.
 
 Congratulations! You have successfully integrated the Counter.dev tracking
 script into your Squarespace website and can now start tracking visitors and

content/help/wordpress.md

@@ -10,19 +10,19 @@ WordPress site:
 2. Open the header.php file and find the closing `</head>` tag.
 
 3. Copy the Counter.dev tracking script provided in your Counter.dev account
-   and paste it just before the closing `</head>` tag.
+and paste it just before the closing `</head>` tag.
 
 4. Save the changes to the header.php file.
 
 5. Clear any caching plugins you may have installed on your WordPress site.
 
 6. Verify that the tracking code has been properly installed by visiting your
-   website and opening the developer console (usually done by pressing F12). The
-   console should not display any errors and the network tab should show that the
-   Counter.dev script has been loaded.
+website and opening the developer console (usually done by pressing F12). The
+console should not display any errors and the network tab should show that the
+Counter.dev script has been loaded.
 
 7. Log in to your Counter.dev account and check the analytics dashboard to see
-   if your WordPress website is being tracked.
+if your WordPress website is being tracked.
 
 Congratulations! You have successfully integrated the Counter.dev tracking
 script into your WordPress website and can now start tracking visitors and

content/pages/imprint.md

@@ -7,15 +7,18 @@
 
 # Imprint
 
-_Information in accordance with section 5 TMG:_
+*Information in accordance with section 5 TMG:*
 
 Irae Hueck Costa<br/>
 10829 Berlin<br/>
 E-Mail: hey@counter.dev
 
+
+
 Person responsible for content in accordance with 55 Abs. 2 RStV<br/>
 Irae Hueck Costa
 
+
 ## Accountability for content
 
 The contents of our pages have been created with the utmost care. However, we
@@ -28,6 +31,8 @@ obligations to remove or block the use of information under generally
 applicable laws remain unaffected by this as per §§ 8 to 10 of the Telemedia
 Act (TMG).
 
+
+
 ## Accountability for links
 
 Responsibility for the content of external links (to web pages of third

content/pages/privacy.md

@@ -14,26 +14,26 @@ you when you use our website.
 
 Counter collects the following data
 
-- Your username
-- An encrypted password
-- Domains which where used to access web pages containing your personalized
-  tracking script.
-- Your browser's time zone, a preference that can be changed in the account
-  settings.
+-   Your username
+-   An encrypted password
+-   Domains which where used to access web pages containing your personalized
+    tracking script.
+-   Your browser's time zone, a preference that can be changed in the account
+    settings.
 
 Your personalized tracking script aggregates the following statistical information of your users.
 
-- The day of the week (As in: _Monday_, _Tuesday_, ...)
-- Your users device (As in _Phone_, _Tablet_ or _Computer_)
-- The date of the visit
-- From which other website a visit originated.
-- The users browser (As in: _Firefox_, _Chrome_, _Microsoft Edge_, ...)
-- The hour compontent of the current time in a day
-- A country mapped to the users IP address.
-- The users operating system (As in: _Windows_ or _Mac_)
-- Information on the users screen size
-- The users preferred language
-- Pages visited
+-   The day of the week (As in: *Monday*, *Tuesday*, ...)
+-   Your users device (As in *Phone*, *Tablet* or *Computer*)
+-   The date of the visit
+-   From which other website a visit originated.
+-   The users browser (As in: *Firefox*, *Chrome*, *Microsoft Edge*, ...)
+-   The hour compontent of the current time in a day
+-   A country mapped to the users IP address.
+-   The users operating system (As in: *Windows* or *Mac*)
+-   Information on the users screen size
+-   The users preferred language
+-   Pages visited
 
 These data points are saved anonymously in our primary database aggregated on a hourly, daily,
 weekly, monthly, yearly and overall basis. Counter deletes hourly, daily,
@@ -49,11 +49,11 @@ As of the 19. Sept 2022 we introduced historical archives persisting daily data
 You directly provide Counter with most of the data we collect. We collect data
 and process data when you
 
-- Register online.
-- Write us an email.
-- Change the account settings.
-- Include your personalized tracking script in a web page which is visited by
-  other users.
+-   Register online.
+-   Write us an email.
+-   Change the account settings.
+-   Include your personalized tracking script in a web page which is visited by
+    other users.
 
 ## How do we store your data?
 
@@ -65,7 +65,6 @@ anymore, we recommend permanently deleting it in the account settings. We may
 delete your data automatically if you stop using the service for longer than one year.
 
 ## What are your data protection rights?
-
 Counter would like to make sure you are fully aware of all of your data protection rights.
 Every user is entitled to the following:
 
@@ -76,6 +75,7 @@ The right to rectification - You have the right to request that Counter correct
 you believe is inaccurate. You also have the right to request Counter to complete information
 you believe is incomplete.
 
+
 **The right to erasure** - You have the right to request that Counter erase your personal data,
 under certain conditions.
 
@@ -92,43 +92,38 @@ If you make a request, we have one month to respond to you. If you would like to
 these rights, please contact us at our email: hey@counter.dev
 
 ## What are cookies?
-
 Cookies are text files placed on your computer to collect standard Internet log information and
 visitor behavior information. When you visit our websites, we may collect information from you
 automatically through cookies or similar technology.
 
-## How do we use cookies?
 
+## How do we use cookies?
 Counter uses cookies for the following purpose:
+-  Keeping you signed in.
+-  Our content delivery network, Cloudflare, Inc. may set cookies for reasons unknown to Counter.
 
-- Keeping you signed in.
-- Our content delivery network, Cloudflare, Inc. may set cookies for reasons unknown to Counter.
 
 ## How to manage cookies
-
 You can set your browser not to accept cookies, and the above website tells you how to remove
 cookies from your browser. However some of our website features may not function
 as a result.
 
-## Privacy policies of other websites
 
+## Privacy policies of other websites
 The Counter website contains links to other websites. Our privacy policy applies only to our
 website, so if you click on a link to another website, you should read their privacy policy.
 
 ## Changes to our privacy policy
-
 Counter keeps its privacy policy under regular review and places any updates on this web page.
 This privacy policy was last updated on 18 May 2023.
 
 ## How to contact us
-
 If you have any questions about Counter's privacy policy, the data we hold on you, or you would
 like to exercise one of your data protection rights, please do not hesitate to contact us.
 
 Email us at: hey@counter.dev
 
 ## How to contact the appropriate authority
-
 Should you wish to report a complaint or if you feel that Counter has not addressed your
 concern in a satisfactory manner, you may contact the Information Commissioner's Office.
 

docs/index.html

@@ -1,4 +1,4 @@
-<!doctype html>
+<!DOCTYPE html>
 <html lang="en-US">
   <head>
     <meta charset="UTF-8" />

docs/script-testing.js

@@ -1,12 +1,17 @@
 (function () {
-    if (sessionStorage.getItem("doNotTrack") || localStorage.getItem("doNotTrack")) {
-        return;
+    if (sessionStorage.getItem('doNotTrack') || localStorage.getItem('doNotTrack')){
+        return
     }
     var id = document.currentScript.getAttribute("data-id");
     var utcoffset = document.currentScript.getAttribute("data-utcoffset");
-    var server = document.currentScript.getAttribute("data-server") || "https://t.counter.dev";
+    var server =
+        document.currentScript.getAttribute("data-server") ||
+        "https://t.counter.dev";
 
-    if (!sessionStorage.getItem("_swa") && !document.referrer.startsWith(location.protocol + "//" + location.host)) {
+    if (
+        !sessionStorage.getItem("_swa") &&
+        !document.referrer.startsWith(location.protocol + "//" + location.host)
+    ) {
         setTimeout(function () {
             sessionStorage.setItem("_swa", "1");
             fetch(
@@ -17,7 +22,7 @@
                         screen: screen.width + "x" + screen.height,
                         id: id,
                         utcoffset: utcoffset,
-                    }),
+                    })
             );
         }, 4500);
     }
@@ -26,6 +31,6 @@
         new URLSearchParams({
             id: id,
             page: window.location.pathname,
-        }),
+        })
     );
 })();

docs/script.js

@@ -1,12 +1,17 @@
 (function () {
-    if (sessionStorage.getItem("doNotTrack") || localStorage.getItem("doNotTrack")) {
-        return;
+    if (sessionStorage.getItem('doNotTrack') || localStorage.getItem('doNotTrack')){
+        return
     }
     var id = document.currentScript.getAttribute("data-id");
     var utcoffset = document.currentScript.getAttribute("data-utcoffset");
-    var server = document.currentScript.getAttribute("data-server") || "https://t.counter.dev";
+    var server =
+        document.currentScript.getAttribute("data-server") ||
+        "https://t.counter.dev";
 
-    if (!sessionStorage.getItem("_swa") && !document.referrer.startsWith(location.protocol + "//" + location.host)) {
+    if (
+        !sessionStorage.getItem("_swa") &&
+        !document.referrer.startsWith(location.protocol + "//" + location.host)
+    ) {
         setTimeout(function () {
             sessionStorage.setItem("_swa", "1");
             fetch(
@@ -17,7 +22,7 @@
                         screen: screen.width + "x" + screen.height,
                         id: id,
                         utcoffset: utcoffset,
-                    }),
+                    })
             );
         }, 4500);
     }
@@ -26,6 +31,6 @@
         new URLSearchParams({
             id: id,
             page: window.location.pathname,
-        }),
+        })
     );
 })();

static/components/_base.js

@@ -1,5 +1,7 @@
 function tagName() {
-    var tagName = new URL(document.currentScript.src).pathname.slice(1, -3).replace(/\//g, "-");
+    var tagName = new URL(document.currentScript.src).pathname
+        .slice(1, -3)
+        .replace(/\//g, "-");
     return tagName.slice(11);
 }