Technical Article Package
A practical tutorial or product article with runnable code, screenshots or output evidence, and an editor-ready outline.
- 1,200-2,000 word draft
- Working repo or code sample
- Verification commands
Paid Developer Services
Practical developer content, Crawlee and Apify Actor builds, GitHub workflow automation, and evidence-based review reports. The sample project on this site shows the expected style: real code, clear tradeoffs, and reproducible verification.
Small, concrete engagements work best. Each package includes a scoped deliverable, source links, and verification notes.
A practical tutorial or product article with runnable code, screenshots or output evidence, and an editor-ready outline.
A focused Actor or crawler prototype that turns public data into structured output for review or downstream workflows.
A concise audit of a repo, issue queue, automation workflow, or contributor path with prioritized fixes and evidence.
The intake issue captures enough context to decide whether the work is real, scoped, and safe to take.
These are not checkout buttons. They open a public GitHub inquiry with the right package title so the work can be scoped before any payment details are discussed.
Best for a repo, issue queue, or workflow that needs an evidence-based outside read.
Best for developer tools that need a practical tutorial backed by working code.
Best for turning a public-data workflow into a Crawlee script or Apify Actor prototype.
These public artifacts show the expected quality bar for future paid work.