Working…
Community

Submit Data or Contribute

PROTAC Builder improves through clear examples, accurate documentation, component updates, reproducible workflows, and coordinated feedback across the connected Schurer Lab tool ecosystem.

This page explains what kinds of contributions are helpful, what information to include, how to coordinate cross-tool updates, and how to contact the project team without turning contribution requests into guesswork.

Issues and broken links Examples and docs Component updates Cross-tool coordination
Open GitHub repository ↗ Contact the project team View release notes Read methods

How to contribute

Issues

Report a bug or broken link

Report broken pages, missing images, incorrect external links, unexpected builder behavior, query-parameter preload issues, or API documentation mismatches.

Open GitHub issue ↗
Examples

Suggest a workflow example

Request new builder launch examples, warhead-first walkthroughs, recruiter-first workflows, viral target patterns, batch workflows, or downstream handoff examples.

View examples
Components

Suggest component updates

Propose warhead examples, linker templates, recruiter additions, attachment-atom notes, or cross-tool data consistency fixes.

Open component hubs
Docs

Improve documentation

Request FAQ clarifications, Methods page updates, API docs edits, schema notes, or download-manifest improvements.

Read FAQ
Ecosystem

Coordinate ecosystem updates

Flag cross-tool updates spanning PROTAC Builder, Warhead Hunter, E3 Ligandalyzer, V-LiSEMOD, screenshots, or shared workflow pages.

Explore ecosystem

What you can submit

Report an issue

  • Broken page or route
  • Broken image or figure link
  • External ecosystem link issue
  • Unexpected builder behavior
  • Query-parameter preload mismatch
  • API doc or schema mismatch
Open GitHub issue ↗

Suggest examples or documentation

  • New builder launch examples
  • Warhead-first, recruiter-first, or viral-target walkthroughs
  • Batch or API workflow examples
  • FAQ clarifications
  • Methods page improvements
  • Download-manifest or schema notes
View examples View case studies Read methods

Contribute component data

  • Warhead examples
  • Linker templates or families
  • E3 recruiter examples
  • Attachment-atom notes
  • Supporting references or IDs
  • Cross-tool consistency fixes
Open component hubs

Coordinate ecosystem updates

  • Warhead Hunter links or screenshots
  • E3 Ligandalyzer links or recruiter references
  • V-LiSEMOD links or viral-target workflow framing
  • Shared cross-tool handoff examples
Explore ecosystem map

What to include in a useful submission

Bug reports

Page URL
Steps to reproduce
Expected behavior
Actual behavior
Screenshot if relevant
Browser or device if relevant
Error message or console output if available

Data or component suggestions

Component type: warhead, linker, recruiter, example, or workflow
Structure identifier, SMILES, or source ID if available
Supporting reference or source
Suggested attachment atom or context if relevant
Notes on uncertainty
Whether it relates to Warhead Hunter, E3 Ligandalyzer, V-LiSEMOD, or PROTAC Builder

API or batch issues

Endpoint or route
Request payload
Response or error
Expected output
Minimal reproducible example
Version or date

Documentation suggestions

Page or route to update
What felt unclear
Suggested wording or structure
Any supporting examples

What not to submit

Please do not submit private patient data, confidential company data, unpublished proprietary structures without the right to share them, secrets, API keys, tokens, passwords, unsafe wet-lab protocols, unsupported activity claims, or large datasets without coordination.

Data and attribution expectations

  • Public contributions should include source information when possible.
  • Component suggestions should distinguish evidence from assumptions.
  • Published references, PDB IDs, database IDs, and tool-generated results should be cited or linked when relevant.
  • If a contribution is speculative, label it as speculative.
  • Do not upload restricted or confidential content.

Contact the project team

For coordinated updates, cross-tool questions, or contribution planning, contact the project team. Use the contact button if you need to discuss documentation updates, ecosystem synchronization, or more structured contribution paths than a public issue thread allows.
Contact the project team

Connected contribution areas

Internal

FAQ

Review common questions and clarify where users may need better guidance.

Read FAQ
Internal

Methods

Review the documented workflow scope, assumptions, and limits.

Read methods
Internal

Release Notes

Review what shipped in Version 1 and which improvements are already documented.

View release notes
Internal

API Builder

Review scriptable builder workflows and payload-preparation surfaces.

Open API Builder
Internal

API Docs

Check whether a public route, schema, or example still matches the documented behavior.

Open API docs
Internal

Batch Workflows

Review the current batch-generation and reproducibility guidance.

Read batch workflows
Internal

Database Schema

Review public-facing data and schema notes that may need updates.

Read schema notes
Internal

Case Studies

Suggest richer workflow walkthroughs or clearer case-study framing.

View case studies
Internal

Component Hubs

Review or improve how the site connects warheads, linkers, and recruiters.

Explore component hubs

Ready to contribute?

Open GitHub repository ↗ Contact the project team View release notes Explore component hubs