You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/EMBEDDING.md
+23-6Lines changed: 23 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,11 +2,14 @@
2
2
3
3
Panda Notes is MIT licensed, so teams may link to it, copy it, fork it, and adapt it for their own projects as long as the license notice stays with the software.
4
4
5
+
Paid setup is available when a team wants Panda Notes installed, configured, and handed off without doing the integration work themselves.
6
+
5
7
## Current Integration
6
8
7
-
Today, Panda Notes includes a standalone local-first console and an alpha right-click widget:
9
+
Today, Panda Notes includes a standalone local-first console and a v0.3 right-click widget:
8
10
9
11
- Send testers to the hosted app: <https://p4nd4907.github.io/panda-notes/>
12
+
- Generate a paid-install snippet: <https://p4nd4907.github.io/panda-notes/install.html>
10
13
- Try the widget demo: <https://p4nd4907.github.io/panda-notes/widget-demo.html>
11
14
- Export notes as JSON from one browser and import them into another.
12
15
- Copy a developer packet or GitHub-ready issue draft from the selected target issue.
@@ -25,7 +28,11 @@ Projects can load the widget during alpha or beta testing:
The exported JSON is compatible with the standalone console import flow.
72
86
87
+
## Paid Install Checklist
88
+
89
+
For a setup sprint, send the app URL, the target flows, tester roles, preferred delivery window, and whether the widget should use only right-click, the launcher button, the hotkey, or all three. Keep credentials and private files out of public GitHub issues; use the private intake page for scope and move secrets only through the agreed private channel.
90
+
73
91
## Still To Strengthen
74
92
75
93
- Optional screenshot or DOM snapshot hook for projects that opt in.
76
-
- Optional GitHub issue draft handoff from captured notes.
77
94
- Import helper that sends widget JSON directly into the standalone console.
78
95
- More browser coverage around cross-origin app shells and shadow DOM targets.
Copy file name to clipboardExpand all lines: docs/STRIPE.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,8 @@ Create three one-time deposit links:
12
12
13
13
The public Services page reads `public/stripe-links.json`. If a Stripe URL is present for an offer, its button goes to Stripe checkout. If a Stripe URL is blank, the button falls back to the matching GitHub intake form.
14
14
15
+
Generated Payment Links redirect buyers back to Panda Notes after checkout. The current automation routes buyers to the private intake path so the paid customer can submit service, payment reference, reply email, scope, deadline, project URL, and delivery context without posting private details to public GitHub issues.
16
+
15
17
## Dashboard Setup
16
18
17
19
1. Open Stripe Dashboard Payment Links.
@@ -70,7 +72,7 @@ Never commit `sk_test_...` or `sk_live_...` keys. `.env` and `.env.local` are ig
70
72
71
73
## Webhook Confirmation
72
74
73
-
Panda Notes includes a serverless webhook at `/api/stripe-webhook`. It verifies Stripe's `Stripe-Signature` header with `STRIPE_WEBHOOK_SECRET`, ignores unrelated event types, and creates a private `payment-confirmed` issue in the private intake repo for successful checkout events.
75
+
Panda Notes includes a serverless webhook at `/api/stripe-webhook`. It verifies Stripe's `Stripe-Signature` header with `STRIPE_WEBHOOK_SECRET`, ignores unrelated event types, and creates a private `payment-confirmed` issue in the private intake repo for successful checkout events. The private issue includes the matched offer, amount, customer email when Stripe provides it, and a ready-to-send private intake link.
74
76
75
77
Do not expose the webhook signing secret in GitHub Pages, public issues, or committed files.
0 commit comments