Editorial priorities
- Answer the learner's question before promoting the app.
- Use ordinary examples that a learner could plausibly say or encounter.
- Explain meaning and sentence function before presenting large ending tables.
- Show contrasts where more than one form is possible.
- State limitations instead of promising fluency, guaranteed rankings, or universal rules.
- Keep articles accessible without requiring an account.
Authorship and responsibility
The visible author is responsible for topic selection, research direction, English explanation, examples, organization, and the decision to publish or update the page.
Authorship is not the same as native-speaker review or academic qualification. The author profile states relevant responsibilities and limitations.
Source hierarchy
A citation supports the factual claim drawn from it; it does not transfer authority to unrelated examples or marketing claims.
| Question | Preferred evidence |
|---|---|
| Grammar and usage | Polish educational platforms, academic grammars, university materials, and established dictionaries |
| Pronunciation | phonetic descriptions, university or educational materials, and reviewed native recordings |
| Official life in Poland | current government or institutional sources |
| Product behavior | the current application, code, and verified interface |
| Search landscape | current search results and the pages ranking for the intended query |
| Learner difficulty | repeated user questions, support feedback, and clearly identified community evidence |
Polish-language review labels
| Status | Meaning |
|---|---|
| Draft | Structure or examples are still being developed. |
| Source-checked | The explanation was compared with cited references and automated consistency checks. |
| Independent native-teacher review pending | No named qualified reviewer has completed the final Polish-language pass. |
| Reviewed by [name] | The named reviewer checked the agreed scope and approved being credited. |
| Corrected | A substantive issue was fixed and the modified date was updated. |
Use of AI assistance
AI tools may assist with research organization, first-draft structure, code, consistency checks, tables, and alternative explanations. AI output is not treated as a linguistic authority or a substitute for a qualified human reviewer.
Polish examples produced or transformed with AI remain subject to source checking, automated audits, and the visible human-review status. The site should not describe AI-generated speech as a native recording.
- No invented reviewer identities, credentials, quotations, or learner testimonials.
- No citations to sources that do not support the associated claim.
- No silent replacement of uncertainty with absolute wording.
- No claim that an AI system has completed independent native-speaker review.
Examples, translations, and alternatives
Examples are written for a stated learner meaning and should sound plausible in the given context. A translation is an explanation of that use, not a claim that the two sentences match in every context.
When Polish allows alternatives, the guide should explain the difference in meaning, aspect, emphasis, politeness, or register instead of presenting one answer as universally exclusive.
Audio policy
| Audio type | Required treatment |
|---|---|
| Reviewed human recording | Identify it as reviewed only after the Polish script and file have been approved. |
| Browser text-to-speech | Label it as a browser voice and do not imply a native recording. |
| Unreviewed generated audio | Do not publish it as authoritative pronunciation. |
| Missing audio | Provide readable text and do not block access to the explanation. |
Corrections and update dates
Readers can report errors at [email protected]. Reports should include the URL, exact text, proposed correction, and reasoning or source when available.
Substantive corrections update the page's visible modified date, sitemap date, and Article structured data. Styling-only changes do not need to imply that the linguistic content was re-reviewed.
Commercial boundaries
- A guide should remain useful if the reader never creates an account.
- Product comparisons describe learning jobs and limitations rather than declaring a universal winner.
- Pricing and access claims must match the current product or be omitted.
- Affiliate relationships or paid placements must be disclosed near the relevant recommendation.
- App calls to action must not interrupt access to the article's core answer.
Accessibility and user experience
- Use real heading hierarchy, table captions, semantic links, and keyboard-accessible controls.
- Keep long guides navigable with a table of contents and stable anchors.
- Allow tables to scroll without forcing the whole page to overflow.
- Do not make audio the only way to access an example.
- Use descriptive link text instead of raw paths or vague repeated calls to click.
FAQ
Are Zapiekanka articles written by a native Polish speaker?
No blanket claim is made. Noah Levy is not a native Polish speaker; each article states whether independent native-teacher review is still pending or completed.
Does Zapiekanka use AI to create content?
AI may assist with drafts, structure, code, and consistency checks. It is not treated as a linguistic authority or a substitute for qualified human review.
How can I report a Polish error?
Email [email protected] with the page URL, exact text, proposed correction, and reasoning or source if available.
What does source-checked mean?
The explanation was compared with cited educational, academic, dictionary, institutional, or product evidence and passed internal consistency checks.
Is all Zapiekanka audio recorded by native speakers?
No. Pages clearly distinguish browser Polish speech from reviewed human recordings, and no native-recording claim is made where one does not exist.