Editorial policy

Who writes the articles

Articles are written and reviewed by the Faizatech team, the people who build our Webflow apps. We work with Webflow forms, CMS, custom code and the Webflow APIs every day, and we write about the problems we and our users run into.

How we research and test

• Steps are followed in a real Webflow project before they are published. When an article says it was tested, it shows the month it was last checked.
• Code snippets are run in a browser on a published Webflow site before they appear in an article.
• Plan limits, prices and feature availability are checked against the vendor’s own documentation or pricing page, and we link to the source.
• We do not publish invented statistics, testimonials or case studies.

Our own apps

Faizatech sells Webflow apps. Some articles mention them where they are relevant, and those articles say so. Most articles do not mention them at all. When a native Webflow feature or another tool is the better choice for a reader, we say that plainly, including in comparisons that involve our own products.

We do not accept payment for coverage, and we do not use affiliate links.

Updates and corrections

Webflow changes often. We revisit articles when Webflow’s interface, plans or limits change, and the “Updated” date on an article only moves when its content has actually changed.

If you find something wrong or out of date, email contact@faizatech.com. We fix confirmed errors and update the article date.

Images and trademarks

Screenshots are our own. API keys and personal data are removed before publishing. Product names such as Webflow belong to their owners and are used only to describe compatibility or comparisons; their mention does not imply endorsement or affiliation.