Contact
How to reach me, what each channel is good for, and roughly how long each one takes.
One person builds all of this, so the honest version of a contact page is not a form that promises a reply within one business day. It is a list of channels with what each is actually for.
About the code
GitHub is the right place. Issues on a package are read; so are pull requests. If something here is broken, a reproduction is worth more than a description, and a failing test is worth more than a reproduction.
The repository is private today, which means the issue tracker is not somewhere you can reach yet. Until it opens, the profile is the door: github.com/sushindustries.
About work
LinkedIn, at adamjurek22. This is the channel to use for anything with a budget or a deadline attached. Tell me what the thing is and when it needs to exist; I will tell you plainly whether I am the right person for it.
About everything else
Questions about why something here is built the way it is are usually already answered on the page for that thing, and if they are not, the assistant on this site has read all of it. It is a genuinely faster path than waiting for me, and if it gets the answer wrong, that is a bug in the documentation worth knowing about.
What I will not answer quickly
Anything that starts "quick question" and contains a screenshot of a stack trace from a codebase I cannot see. Not out of rudeness - I simply cannot help without the code, and a guess would waste both our time.