Deploying to gh-pages from @ 13f1a56 🚀

log4brains/_next/data/zNzqV0LqH0wYLriOaTCvc/adr/20240603-use-plausible-for-website-analytics.json

@@ -0,0 +1 @@
+{"pageProps":{"projectName":"Github Decision Records","currentAdr":{"slug":"20240603-use-plausible-for-website-analytics","package":null,"title":"Use Plausible for website analytics","status":"accepted","supersededBy":null,"tags":["analytics"],"deciders":[],"body":{"enhancedMdx":"\n## Context and Problem Statement\n\nWe need to choose an analytics solution for all our websites. The main options we are considering are Google Analytics and Plausible. We need to evaluate these options and make a decision.\n\n## Decision Drivers\n\n- Ease of implementation (time to implement)\n- Data privacy and compliance\n- Feature set\n- Performance\n\n## Considered Options\n\n- Google Analytics\n- Plausible\n\nA PoC was done with the Astro blog website, unfortunately Google Analytics was not working within the time limit and Plausible worked straight out of the box.\n\n## Decision Outcome\n\nChosen option: \"Plausible\", because it provides a lightweight and privacy-focused analytics solution that was the fastest to implement.\n\n### Positive Consequences\n\n- Improved data privacy and compliance\n- Lightweight and fast-loading analytics script\n\n### Negative Consequences\n\n- Limited feature set compared to Google Analytics\n- Less integration options with other tools\n- Paid plans only.\n\n## Links\n\n- [Plausible website](https://plausible.io/)\n- [Google Analytics website](https://analytics.google.com/)"},"creationDate":"2024-06-03T19:23:21.000Z","lastEditDate":"2024-06-03T19:23:21.000Z","lastEditAuthor":"WayneGoosen","publicationDate":"2024-06-03T21:59:59.000Z","file":{"relativePath":"docs/adr/20240603-use-plausible-for-website-analytics.md","absolutePath":"/home/runner/work/adr/adr/docs/adr/20240603-use-plausible-for-website-analytics.md"},"repository":{"provider":"github","viewUrl":"https://github.com/WayneGoosen/adr/blob/master/docs/adr/20240603-use-plausible-for-website-analytics.md"}},"l4bVersion":"1.0.1"},"__N_SSG":true}

log4brains/_next/data/zNzqV0LqH0wYLriOaTCvc/index.json

@@ -0,0 +1 @@
+{"pageProps":{"projectName":"Github Decision Records","adrs":[{"slug":"20240410-use-log4brains-to-manage-the-adrs","package":null,"title":"Use Log4brains to manage the ADRs","status":"accepted","creationDate":"2024-04-20T13:02:34.000Z","publicationDate":"2024-04-09T21:59:59.000Z"},{"slug":"blog/20240410-deploy-blog-using-astro","package":"blog","title":"Deploy blog using Astro","status":"accepted","creationDate":"2024-04-21T11:43:32.000Z","publicationDate":"2024-04-21T21:59:59.000Z"},{"slug":"20240603-use-plausible-for-website-analytics","package":null,"title":"Use Plausible for website analytics","status":"accepted","creationDate":"2024-06-03T19:23:21.000Z","publicationDate":"2024-06-03T21:59:59.000Z"}],"markdown":"<!-- This file is the homepage of your Log4brains knowledge base. You are free to edit it as you want -->\n# Architecture knowledge base\n\nWelcome 👋 to the architecture knowledge base for Wayne Goosen's GitHub profile.\nYou will find here all the Architecture Decision Records (ADR) for all projects.\n\n## An Experiment with Architecture Decision Records\n\nThis repository employs Log4Brains to publish all Architectural Decision Records (ADRs) within it.\n\nThe experiment: Use ADRs to keep track of all decisions made across projects within my GitHub profile. If a project grows significantly, move all relevant ADRs to its own repository.\n\n### Why?\n\n1. To maintain a log of all decisions for historical and recall purposes. It's easy to forget WHY a certain approach was taken.\n2. For visibility... Decisions in software development are trade-offs that depend on the situation and context. This will help in understanding certain decisions.\n3. To practice crafting ADRs. This thought-provoking process will ideally lead to better decision-making.\n4. To instill a level of professionalism in side projects.\n\n### Structure\n\nThere are two distinct levels of ADRs:\n- Global: Decisions that impact all repositories.\n- Repository specific: Decisions exclusive to a particular project or product within a repository.\n\nThe repository-specific ones are added as 'packages' within the Log4Brains structure. You can identify these by the package name next to the title within the user interface.\n\n## ADRs\n\n### Definition and purpose\n\n> An Architectural Decision (AD) is a software design choice that addresses a functional or non-functional requirement that is architecturally significant.\n> An Architectural Decision Record (ADR) captures a single AD, such as often done when writing personal notes or meeting minutes; the collection of ADRs created and maintained in a project constitutes its decision log.\n\nAn ADR is immutable: only its status can change (i.e., become deprecated or superseded). That way, you can become familiar with the whole project history just by reading its decision log in chronological order.\nMoreover, maintaining this documentation aims at:\n\n- 🚀 Improving and speeding up the onboarding of a new team member\n- 🔭 Avoiding blind acceptance/reversal of a past decision (cf [Michael Nygard's famous article on ADRs](https://cognitect.com/blog/2011/11/15/documenting-architecture-decisions.html))\n- 🤝 Formalizing the decision process of the team\n\n### Usage\n\nThis website is automatically updated after a change on the `master` branch of the project's Git repository.\nIn fact, the developers manage this documentation directly with markdown files located next to their code, so it is more convenient for them to keep it up-to-date.\nYou can browse the ADRs by using the left menu or the search bar.\n\nThe typical workflow of an ADR is the following:\n\n![ADR workflow](/l4b-static/adr-workflow.png)\n\nThe decision process is entirely collaborative and backed by pull requests.\n\n### More information\n\n- [Log4brains documentation](https://github.com/thomvaill/log4brains/tree/master#readme)\n- [What is an ADR and why should you use them](https://github.com/thomvaill/log4brains/tree/master#-what-is-an-adr-and-why-should-you-use-them)\n- [ADR GitHub organization](https://adr.github.io/)\n","l4bVersion":"1.0.1"},"__N_SSG":true}