feat: Isomorphic Git, Diff viewer, Cache improvements, UI (#99)

- Replaced Octokit-based implementation with Isomorphic Git-based implementation.
	- This change resolves a few longstanding issues, as well as address a few frequent requests:
		- No longer dependent on Octokit, and therefore GitHub as Git host.
		- Significant performance improvements.
		- No longer suffers from GitHub API rate limits, mostly due to direct Git calls.
			- Please let us know if you still run into issue regarding rate limits.
- Added support for GitLab, Bitbucket, Gitea, Codeberg, and Self-hosted instances.
- Added new diff viewer in the Publication Center.
	- Split view (side-by-side comparison) and Unified view options.
	- Configurable default view style in Settings > UI.
	- Responsive design: defaults to split view on desktop, unified view on mobile.
	- Synced scrolling between panes in split view.
- Improved cache invalidation for dynamic content.
	- Files containing Dataview or Datacore queries are now automatically detected.
	- Dynamic files always recompile to ensure query results are up-to-date.
	- Hash comparison determines if output actually changed, preventing unnecessary updates.
- Added UI settings tab for configuring user interface preferences.
- Updated documentation.

Author: saberzero1

README.md

@@ -2,6 +2,14 @@
 
 Quartz Syncer is an [Obsidian](https://obsidian.md/) plugin for managing and publishing notes to [Quartz](https://quartz.jzhao.xyz/), the fast, batteries-included static-site generator that transforms Markdown content into fully functional websites.
 
+## Features
+
+- **Multi-provider support**: Works with GitHub, GitLab, Bitbucket, Codeberg, Gitea, and self-hosted Git instances.
+- **Plugin integrations**: Compiles [Dataview](https://blacksmithgu.github.io/obsidian-dataview/), [Datacore](https://blacksmithgu.github.io/datacore/), and [Fantasy Statblocks](https://plugins.javalent.com/statblocks) queries into static content.
+- **Smart caching**: Caches compiled files for faster subsequent publishes. Dynamic content (Dataview/Datacore queries) is automatically detected and recompiled when needed.
+- **Diff viewer**: Preview exact changes before publishing with split (side-by-side) or unified view.
+- **Selective publishing**: Choose exactly which notes to publish, update, or remove.
+
 ## Installation
 
 Install the plugin by downloading it from the Obsidian Community plugins browser in Obsidian.
@@ -15,7 +23,7 @@ Alternatively, install the plugin by downloading it from the [Release Tab](https
 >
 > For the most up-to-date information on Quartz Syncer, please refer to the [official documentation](https://saberzero1.github.io/quartz-syncer-docs/).
 
-New to Quartz Syncer? please follow the [setup guide](https://saberzero1.github.io/quartz-syncer-docs/Setup-Guide) to get started.
+New to Quartz Syncer? Please follow the [setup guide](https://saberzero1.github.io/quartz-syncer-docs/Setup-Guide) to get started.
 
 ## Usage
 
@@ -30,26 +38,28 @@ For more advanced usages of Quartz Syncer, check the [guides section](https://sa
 > [!IMPORTANT]
 > **Quartz-related questions**
 >
-> For issue or questions related to Quartz, not Quartz Syncer, please consult the [Quartz documentation](https://quartz.jzhao.xyz/) or reach out through the communication channels provided there.
+> For issues or questions related to Quartz, not Quartz Syncer, please consult the [Quartz documentation](https://quartz.jzhao.xyz/) or reach out through the communication channels provided there.
 
 If you need help with Quartz Syncer, or if you have a question, please first check the [troubleshooting section](https://saberzero1.github.io/quartz-syncer-docs/Troubleshooting/). If your question or issue is not listed, feel free to [reach out for help](https://saberzero1.github.io/quartz-syncer-docs/Troubleshooting/#i-have-a-different-issue-not-listed-here).
 
 ## Disclosures
 
 As per the [Obsidian developer policies](https://docs.obsidian.md/Developer+policies#Disclosures):
 
-- **Account requirements**: Quartz Syncer needs to access your Quartz repository on GitHub in order to be able to publish your notes. A GitHub account is therefore required, though also implictly expected, if you're using Quartz.
-- **Network use**: Quartz Syncer accesses the network to manage and publish your notes to your Quartz repository on GitHub. Quartz Syncer uses the [GitHub REST API](https://docs.github.com/en/rest) to access your Quartz repository over the network.
-- **Accessing files outside of Obsidian vaults**: Quartz Syncer only manages explictly marked *and* user-selected notes in your Quartz repository `content` folder. Quartz Syncer also fetches the current contents of this folder to compare changes against your notes. Quartz Syncer doesn't write any notes to your Obsidian vault, Quartz Syncer only writes to your Quartz repository (one-way only: from Obsidian vault to Quartz repository.) When [authentication is properly set up with a fine-grained access token](https://saberzero1.github.io/quartz-syncer-docs/Guides/Generating-an-access-token#generating-a-fine-grained-access-token), Quartz Syncer is only able to modify file contents on your Quartz repository. Quartz Syncer cannot access other repositories on the same GitHub account or organization, nor modify any other settings in your Quartz Repository.
+- **Account requirements**: Quartz Syncer needs to access your Quartz repository on a Git provider in order to publish your notes. An account on your chosen Git provider (GitHub, GitLab, Bitbucket, etc.) is required.
+- **Network use**: Quartz Syncer accesses the network to manage and publish your notes to your Quartz repository. Quartz Syncer uses Git over HTTPS to communicate with your repository.
+- **Accessing files outside of Obsidian vaults**: Quartz Syncer only manages explicitly marked *and* user-selected notes in your Quartz repository `content` folder. Quartz Syncer also fetches the current contents of this folder to compare changes against your notes. Quartz Syncer doesn't write any notes to your Obsidian vault, Quartz Syncer only writes to your Quartz repository (one-way only: from Obsidian vault to Quartz repository.)
 
 ## Acknowledgements
 
-Quartz Syncer would not have been build without the following:
+Quartz Syncer would not have been built without the following:
 
 - [Obsidian Digital Garden](https://dg-docs.ole.dev/), on top of which most of this plugin was initially built.
 - [Quartz](https://quartz.jzhao.xyz/), for the amazing and welcoming community. Come say hi in the Discord server sometimes.
+- [Isomorphic-git](https://isomorphic-git.org/), for enabling Git operations directly in JavaScript.
 - [Obsidian Linter](https://github.com/platers/obsidian-linter), for inspiring the tabbed settings UI.
 - [Dataview](https://blacksmithgu.github.io/obsidian-dataview/), for their great API integration, allowing me to properly integrate it in Quartz.
 - [Datacore](https://blacksmithgu.github.io/datacore/), for their wonderful integration despite its infancy, allowing easy integration into Quartz.
+- [Fantasy Statblocks](https://plugins.javalent.com/statblocks), for their extensible functionality and easy-to-integrate API.
 - [Obsidian Publish](https://obsidian.md/publish), for inspiring me to create a similar solution for Quartz.
 - The entire Obsidian community, for all your weird and amazing creations. Keep it up.

docs/Changelog.md

@@ -2,7 +2,7 @@
 title: Roadmap and Changelog
 description: Changelog and feature roadmap for Quartz Syncer.
 created: 2025-05-16T12:59:31Z+0200
-modified: 2025-08-07T09:11:03Z+0200
+modified: 2026-01-08T14:46:23Z+0100
 publish: true
 ---
 
@@ -24,6 +24,27 @@ publish: true
 
 ## Released
 
+### Version 1.9.0
+
+- Replaced Octokit-based implementation with Isomorphic Git-based implementation.
+	- This change resolves a few longstanding issues, as well as address a few frequent requests:
+		- No longer dependent on Octokit, and therefore GitHub as Git host.
+		- Significant performance improvements.
+		- No longer suffers from GitHub API rate limits, mostly due to direct Git calls.
+			- Please let us know if you still run into issue regarding rate limits.
+- Added support for GitLab, Bitbucket, Gitea, Codeberg, and Self-hosted instances.
+- Added new diff viewer in the Publication Center.
+	- Split view (side-by-side comparison) and Unified view options.
+	- Configurable default view style in Settings > UI.
+	- Responsive design: defaults to split view on desktop, unified view on mobile.
+	- Synced scrolling between panes in split view.
+- Improved cache invalidation for dynamic content.
+	- Files containing Dataview or Datacore queries are now automatically detected.
+	- Dynamic files always recompile to ensure query results are up-to-date.
+	- Hash comparison determines if output actually changed, preventing unnecessary updates.
+- Added UI settings tab for configuring user interface preferences.
+- Updated documentation.
+
 ### Version 1.8.10
 
 - Fixed publication center showing files outside configured root as publishable.

docs/Guides/Bitbucket Setup.md

@@ -0,0 +1,199 @@
+---
+title: Bitbucket Setup
+description: Complete guide for setting up Quartz with Bitbucket and Bitbucket Pipelines.
+created: 2026-01-08T14:00:00Z+0100
+modified: 2026-01-08T18:10:06Z+0100
+publish: true
+tags: [guides]
+---
+
+This guide covers setting up a Quartz repository on Bitbucket, configuring deployment, and connecting Quartz Syncer.
+
+> [!NOTE] Bitbucket Hosting Options
+> Bitbucket does not have a built-in static site hosting service like GitHub Pages. This guide covers deploying to external hosting services using Bitbucket Pipelines.
+
+## Create a Quartz Repository
+
+### Option 1: Import from GitHub
+
+1. Log in to Bitbucket and go to your workspace.
+2. Click **Create** > **Repository**.
+3. Click **Import repository** in the top right.
+4. Enter the Quartz URL: `https://github.com/jackyzha0/quartz.git`
+5. Set your **Repository name** (e.g., `quartz`).
+6. Click **Import repository**.
+
+### Option 2: Create and Push Manually
+
+1. Create a new repository on Bitbucket.
+2. Clone Quartz locally:
+
+   ```bash
+   git clone https://github.com/jackyzha0/quartz.git
+   cd quartz
+   ```
+
+3. Change the remote and push:
+
+   ```bash
+   git remote set-url origin https://bitbucket.org/<workspace>/<repository>.git
+   git push -u origin v4
+   ```
+
+## Configure Deployment
+
+Since Bitbucket doesn't have built-in static hosting, you'll need to deploy to an external service. Below are configurations for popular hosting options.
+
+### Option 1: Deploy to Netlify
+
+Create a file `bitbucket-pipelines.yml` in your repository root:
+
+```yaml
+image: node:22
+
+pipelines:
+  branches:
+    v4:
+      - step:
+          name: Build and Deploy to Netlify
+          caches:
+            - node
+          script:
+            - npm ci
+            - npx quartz build
+            - npm install -g netlify-cli
+            - netlify deploy --prod --dir=public --site=$NETLIFY_SITE_ID --auth=$NETLIFY_AUTH_TOKEN
+```
+
+Add these repository variables in **Repository settings** > **Pipelines** > **Repository variables**:
+
+- `NETLIFY_SITE_ID`: Your Netlify site ID
+- `NETLIFY_AUTH_TOKEN`: Your Netlify personal access token
+
+### Option 2: Deploy to Cloudflare Pages
+
+```yaml
+image: node:22
+
+pipelines:
+  branches:
+    v4:
+      - step:
+          name: Build and Deploy to Cloudflare
+          caches:
+            - node
+          script:
+            - npm ci
+            - npx quartz build
+            - npm install -g wrangler
+            - wrangler pages deploy public --project-name=$CF_PROJECT_NAME
+```
+
+Add these repository variables:
+
+- `CLOUDFLARE_API_TOKEN`: Your Cloudflare API token
+- `CLOUDFLARE_ACCOUNT_ID`: Your Cloudflare account ID
+- `CF_PROJECT_NAME`: Your Cloudflare Pages project name
+
+### Option 3: Deploy to Vercel
+
+```yaml
+image: node:22
+
+pipelines:
+  branches:
+    v4:
+      - step:
+          name: Build and Deploy to Vercel
+          caches:
+            - node
+          script:
+            - npm ci
+            - npx quartz build
+            - npm install -g vercel
+            - vercel deploy --prod --token=$VERCEL_TOKEN public
+```
+
+Add this repository variable:
+
+- `VERCEL_TOKEN`: Your Vercel access token
+
+### Enable Bitbucket Pipelines
+
+1. Go to your repository on Bitbucket.
+2. Navigate to **Repository settings** > **Pipelines** > **Settings**.
+3. Enable Pipelines.
+
+## Generate an App Password
+
+Bitbucket uses App Passwords for API authentication instead of Personal Access Tokens.
+
+1. Click your profile avatar in the bottom left and select **Personal settings**.
+2. Under **Access management**, click **App passwords**.
+3. Click **Create app password**.
+4. Enter a **Label** (e.g., `Quartz Syncer`).
+5. Under **Permissions**, select:
+   - **Repositories**: **Write** (this includes Read)
+6. Click **Create**.
+7. Copy the generated password immediately.
+
+> [!WARNING] Password Security
+> The app password is only shown once. Store it securely.
+
+## Configure Quartz Syncer
+
+1. Open Obsidian and go to **Settings** > **Community Plugins** > **Quartz Syncer**.
+2. In the **Git** settings tab:
+   - **Remote URL**: `https://bitbucket.org/<workspace>/<repository>.git`
+   - **Branch**: `v4` (or your Quartz branch)
+   - **Provider**: Bitbucket
+   - **Authentication Type**: Username & Token/Password
+   - **Username**: `x-token-auth` (when using an App Password)
+   - **Access Token**: The app password you generated
+
+A green checkmark indicates a successful connection.
+
+> [!TIP] Username Options
+> You can use either `x-token-auth` or your Bitbucket username. Using `x-token-auth` is the standard method for App Passwords.
+
+## Bitbucket Server (Self-Hosted)
+
+If you're using Bitbucket Server (Data Center):
+
+1. Replace `bitbucket.org` with your Bitbucket Server URL.
+2. Generate an HTTP Access Token:
+   - Go to **Profile** > **Manage account** > **HTTP access tokens**
+   - Create a token with **Repository write** permission
+3. Use your Bitbucket Server username in the Username field.
+
+## Alternative: Direct Hosting Service Integration
+
+Instead of using Bitbucket Pipelines, you can connect your hosting service directly to Bitbucket:
+
+### Netlify
+
+1. Log in to Netlify.
+2. Click **Add new site** > **Import an existing project**.
+3. Select Bitbucket and authorize.
+4. Select your Quartz repository.
+5. Configure build settings:
+   - **Build command**: `npx quartz build`
+   - **Publish directory**: `public`
+
+### Cloudflare Pages
+
+1. Log in to Cloudflare Dashboard.
+2. Go to **Workers & Pages** > **Create application** > **Pages**.
+3. Connect to Git and select Bitbucket.
+4. Select your repository and configure:
+   - **Build command**: `npx quartz build`
+   - **Build output directory**: `public`
+
+### Vercel
+
+1. Log in to Vercel.
+2. Click **Add New** > **Project**.
+3. Import from Bitbucket.
+4. Configure:
+   - **Build Command**: `npx quartz build`
+   - **Output Directory**: `public`