griffinforms

Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Forum: Plugins
    In reply to: [GriffinForms - Form Builder with Multi-Step and Registration Forms] Can GriffinForms support per-form styles and migration from WPForms/Forminator?
    Plugin Author griffinforms

    (@griffinforms)

    5 months, 1 week ago

    Hi @janicgoode

    Just wanted to updated you, since GriffinForms 2.0.0.0 we added a Theme system that directly addresses your “per‑form style” and consistency requirements.

    Per‑form styles:
    – Yes. Each form can use its own theme so you can apply different styling per client/site/form without custom CSS.
    – Themes cover field spacing/typography, input styling, buttons, and form-level states (errors + success messages) so the whole form stays visually consistent.
    – We also support moving themes between sites via a theme import/export workflow.

    Error message appearance:
    – Error styling is handled by the active theme, so errors look consistent across all field types and match the rest of the form’s design.

    Performance:
    – GriffinForms is built to stay lightweight. Themes are generated in a predictable way so you don’t have to fight WordPress theme CSS overrides.

    Label visibility / simple UI control:
    – Many “hide labels / show placeholders / tweak layout” needs can be handled through form builder settings (and when you do use CSS, it stays straightforward because theme output is consistent).

    Migration from WPForms / Forminator:
    – We are still planning migration workflows. Hopefully, it will be available soon.

    Thanks again for checking out GriffinForms!

    Forum: Plugins
    In reply to: [GriffinForms - Form Builder with Multi-Step and Registration Forms] Can GriffinForms support per-form styles and migration from WPForms/Forminator?
    Plugin Author griffinforms

    (@griffinforms)

    11 months, 1 week ago

    Hi Janic,

    Thanks so much for exploring GriffinForms, and apologies for the delayed response—just catching up now.

    To answer your questions:

    Per-form style overrides:
    Each form container has a unique class like griffinforms-form28-container (where 28 is the form ID). This allows easy targeting via CSS for per-form customization. A UI based customization feature is on our roadmap.

    Custom error message styling:
    GriffinForms uses Bootstrap alert classes for error messages. You can override the styling with your own CSS as needed.

    Fast form rendering:
    Yes, GriffinForms is built with performance in mind. It uses optimized markup and minimal frontend dependencies for fast loading.

    Label control:
    GriffinForms supports both internal field names (for admin use) and public-facing labels. Public-facing labels are optional—can be left blank or hidden via settings or CSS (e.g., .form-label { display: none; }).

    Form migration:
    At the moment, there is no built-in migration tool for WPForms or Forminator. Forms need to be recreated manually. However, migration support is on our roadmap.

    GriffinForms is still in its early stages, and we’re actively improving it based on user feedback. We have several exciting features planned for the coming weeks. Your input is incredibly valuable as we grow.

    Thanks again for your interest. Feel free to reach out anytime with more questions or suggestions.

Viewing 2 replies - 1 through 2 (of 2 total)