Support

Thanks for using Frontend Engineering. This file explains where to go for what — please pick the right channel so maintainers can help efficiently.

I have a question about frontend engineering

Open a GitHub Discussion in the Q&A category, or open an issue with the type: question label. Note that this repository documents engineering decisions and trade-offs — it is not a general help desk for debugging your app. Well-scoped questions about a specific article or trade-off get the best responses.

I found an error in an article

Open an issue using the Content correction template. Point to the exact file and describe what is wrong. Corrections are among the most valuable contributions.

I want to propose a new article

Open an issue using the Article proposal template first, so a maintainer can confirm scope before you invest time writing. See CONTRIBUTING.md.

I want to suggest an improvement to the repo itself

(Structure, tooling, workflows, templates.) Open an issue with the Improvement / idea template. Substantial changes go through an RFC — see GOVERNANCE.md.

I think I found a security problem

See SECURITY.md. Do not open a public issue.

Response expectations

This is a community project maintained by volunteers. There is no SLA. Issues and discussions are triaged on a best-effort basis, typically weekly. You can help by writing clear, self-contained reports and by reviewing others' pull requests.

Channels at a glance

I want to…	Go to
Ask a conceptual question	Discussions → Q&A or type: question issue
Report a content error	Issue → Content correction
Propose an article	Issue → Article proposal
Suggest a repo/tooling change	Issue → Improvement / idea
Report a security concern	SECURITY.md (private)