Component Guide
Component Guide
Components are the main building blocks used to assemble pages in FaceFlow.
If a page needs a structured website section such as a hero block, pricing area, FAQ, gallery, CTA section, service grid, or contact block, a Component is usually the right tool.
When To Use a Component
Use a Component when you need:
- a visible page section with its own structure
- a repeatable section that may appear on many pages
- content that should stay inside a consistent design pattern
- a section with several editable fields such as title, text, image, links, or actions
Good examples include:
- hero sections
- feature grids
- service cards
- pricing sections
- FAQs
- testimonial sections
- contact sections
- form-led conversion blocks
When Not To Use a Component
Do not use a Component when:
- the content is only a very small shared snippet
- the content belongs to one page field and does not need section structure
- you only need to reuse a short fragment such as a notice, label, or support detail
In those cases, a Variable may be the better fit.
Recommended Workflow
- Start with the page goal
- Choose the sections that support that goal
- Reuse existing Components before requesting or creating new ones
- Fill in fields carefully
- Review the order of sections on the page
- Preview before publishing
How To Choose Better Components
Ask:
- Does this section help the visitor move forward?
- Is there already a proven Component for this need?
- Does this section belong in the page journey, or is it only visual noise?
The best Component choices usually come from the page goal, not from visual preference alone.
Common Use Cases
- landing page sections
- service overviews
- pricing and comparison areas
- FAQ sections
- proof and review sections
- form-driven CTA blocks
Common Mistakes
- adding too many sections to one page
- choosing sections that repeat the same message
- creating near-duplicate Components for small content differences
- overloading one section with too much unrelated information
- forgetting to review the order and transition between sections
Team Guidance
- prefer reuse over near-duplication
- keep Component naming understandable
- choose the simplest section that fits the page goal
- treat Forms and Reviews as part of the page journey, not add-ons