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
feat: add ScriptHammer.com link to footer, document manifest issue
- Footer now links to ScriptHammer.com for template reference
- Added Issue #12 to FORKING-FEEDBACK.md documenting that manifest.json
is generated and requires updating scripts/generate-manifest.js
rather than the manifest file directly
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: FORKING-FEEDBACK.md
+62-1Lines changed: 62 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ This document captures issues encountered when forking the ScriptHammer template
4
4
5
5
## Summary
6
6
7
-
Forking ScriptHammer required updating **200+ files** with hardcoded references. The Docker-first architecture also created friction with git hooks. Additionally, tests require Supabase mocking, description assertions need updating, **the basePath secret in deploy.yml breaks GitHub Pages for forks** (Issue #10), and **production crashes without Supabase GitHub secrets** (Issue #11).
7
+
Forking ScriptHammer required updating **200+ files** with hardcoded references. The Docker-first architecture also created friction with git hooks. Additionally, tests require Supabase mocking, description assertions need updating, **the basePath secret in deploy.yml breaks GitHub Pages for forks** (Issue #10), **production crashes without Supabase GitHub secrets** (Issue #11), **the footer template link needs manual update** (Issue #12), and **the PWA manifest description is generated at build time** (Issue #13).
- Document Supabase setup as a required step in the fork workflow
321
321
- Or modify `src/lib/supabase/client.ts` to return a disabled mock client instead of throwing, allowing the app to run in "offline mode" without Supabase
322
322
323
+
### 12. Footer Template Link Needs Manual Update
324
+
325
+
**Problem:** The footer says "Open source template available" but doesn't link anywhere. Forkers need to manually add a link back to the template source.
326
+
327
+
**Current Code** (`src/components/Footer.tsx`):
328
+
329
+
```tsx
330
+
<pclassName="text-base-content/40 mt-1 text-xs">
331
+
Open source template available
332
+
</p>
333
+
```
334
+
335
+
**Suggested Fix:** The template should include the link by default:
336
+
337
+
```tsx
338
+
<pclassName="text-base-content/40 mt-1 text-xs">
339
+
Open source template available at{''}
340
+
<a
341
+
href="https://scripthammer.com"
342
+
target="_blank"
343
+
rel="noopener noreferrer"
344
+
className="link-hover link"
345
+
>
346
+
ScriptHammer.com
347
+
</a>
348
+
</p>
349
+
```
350
+
351
+
### 13. PWA Manifest Description is Generated, Not Static
352
+
353
+
**Problem:** After rebranding, the `public/manifest.json` keeps reverting to the old template description even after editing it directly.
354
+
355
+
**Root Cause:**`public/manifest.json` is **generated** by `scripts/generate-manifest.js` during the prebuild process. Line 53 has a hardcoded description:
356
+
357
+
```javascript
358
+
description:`${projectConfig.projectName} - Modern Next.js template with PWA, theming, and interactive components`,
359
+
```
360
+
361
+
**Files that need description updates for rebranding:**
0 commit comments