Skip to content

Drop PyOpt from the catalog and rewrite the issue-tracker copy - #21

Merged
saudzahirr merged 1 commit into
masterfrom
update-projects-and-issue-copy
Aug 18, 2026
Merged

Drop PyOpt from the catalog and rewrite the issue-tracker copy#21
saudzahirr merged 1 commit into
masterfrom
update-projects-and-issue-copy

Conversation

@saudzahirr

Copy link
Copy Markdown
Collaborator

What

  • Remove the PyOpt entry from the project catalog (src/data/site.ts).
  • Rewrite the callout at the bottom of /projects/ so it stops inviting issues for personal understanding.

Why

The old copy read:

Pick a project, read its documentation, and open an issue on github.com/eggzec if anything is unclear.

That points readers at the issue tracker whenever they don't understand something. Issue trackers are for bugs, incorrect results, documentation defects, and feature requests — not for a reader's own comprehension. The new copy says so, sends questions to repository discussions, and points patches at pull requests.

Verified

npm run build (tsc --noEmit + vite build) passes.

🤖 Generated with Claude Code

Remove the PyOpt entry from the project catalog.

The projects callout told readers to open an issue on github.com/eggzec
"if anything is unclear", which invites issues for personal understanding.
Issue trackers are for bugs, incorrect results, documentation defects and
feature requests; questions belong in discussions and patches in pull
requests. Say that instead.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@saudzahirr
saudzahirr merged commit 67a665d into master Aug 18, 2026
2 checks passed
@saudzahirr
saudzahirr deleted the update-projects-and-issue-copy branch August 18, 2026 10:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant