Convert to generic presentation template with automated setup

[Copilot]

• Create placeholder script to replace template values
• Update README.md with generic placeholders
• Update index.html with generic placeholders
• Rename markdown file to generic name
• Update package.json with generic name
• Update CLAUDE.md with correct project overview
• Test setup script with multiple scenarios
• Add comprehensive usage documentation
• Verify deployment workflow compatibility
• Add detailed GitHub Pages and workflow permissions instructions
• Final verification and testing complete

Summary

This repository is now a fully functional generic presentation template. When users create a new repository from this template:

1. They run ./setup-template.sh
2. The script automatically:
   • Detects their repository name from git
   • Updates README.md with the correct GitHub Pages URL
   • Updates index.html with their chosen title
   • Renames the markdown file to match their repo name
   • Updates package.json
   • Self-deletes

All requirements met:
✅ README.md automatically updated with GitHub Pages deployment URL
✅ index.html updated with correct values
✅ Markdown file renamed to match presentation repo name
✅ Complete setup instructions including workflow permissions and GitHub Pages configuration

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Turn this into a generic presentation template</issue_title>
<issue_description>This should be a generic presentation template:

• When a new copy of this template is created:
  • The README.md should automatically be updated to point to the new github pages deployment (or have a placeholder)
  • The index.html should have the right values
  • The markdown file should be named to match the presentation repo name </issue_description>

Comments on the Issue (you are @copilot in this section)

Fixes #1

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[rfay]

@copilot continue implementing

[rfay]

@copilot This needs instructions about enabling github pages, right? Maybe also about enabling the workflow to push?

[Copilot]

@copilot This needs instructions about enabling github pages, right? Maybe also about enabling the workflow to push?

Added detailed instructions for both enabling GitHub Pages and configuring workflow permissions in commit a9ef6c3.

The documentation now includes:

• Step-by-step workflow permissions setup (Settings > Actions > General)
• GitHub Pages configuration with "GitHub Actions" source
• Troubleshooting section for common deployment issues
• Clear explanation of the three-step deployment process

Both README.md and TEMPLATE_USAGE.md have been updated with these instructions.

@copilot This needs instructions about enabling github pages, right? Maybe also about enabling the workflow to push?

Added detailed instructions for both enabling GitHub Pages and configuring workflow permissions in commit 628f8c1.

The documentation now includes:

• Step-by-step workflow permissions setup (Settings > Actions > General)
• GitHub Pages configuration with "GitHub Actions" source
• Troubleshooting section for common deployment issues
• Clear explanation of the three-step deployment process

Both README.md and TEMPLATE_USAGE.md have been updated with these instructions.

[rfay]

OK