GutenBricks
  • 🚀 Getting Started
    • Next: Common Troubleshooting Issues
    • Next: Configure Page Template to render
    • Next: Manage Block using Template Bundles
    • 🤔Most common troubleshooting step
  • 🌟Features
    • Working with Elements
    • Variants
    • InnerBlock
    • Fine-Tune Text Editing
    • Dynamic Class
    • Code Block with Dynamic Data
    • 💡Quick Tips
      • Dynamic Short Code
      • Accordion Block using InnerBlock
    • ⚡Advanced
      • Custom Block HTML ID
      • Value Binding (coming soon)
      • Creating "comments and docs" inside a template
      • Globally Updating Block Styles
      • Block Wrapper Dynamic Class
      • Working with WPML or Polylang
  • 🏀Dynamic Data
    • GB:Meta
    • ACF
      • Setting Up ACF
      • Post Object Field (in-progress)
    • Meta Box
      • Setting Up Meta Box (In-progress)
      • Post Field (in-progress)
    • Built-in GutenBricks Dynamic Data
  • 🍰Client Experience
    • Documenting Blocks
    • Custom Block Preview
    • Custom Pop-up Text
    • Default Page Template
  • 🛠️Customizing Gutenberg
    • Gutenberg Editor Custom CSS
      • CSS Snippet: Make the block section not full height for ACSS
  • 🤹Resources
    • 👩‍💻 Developer API
      • echo:gb_current_element_id returns unique ID
      • GutenBricks Events for Gutenberg Editor
      • gb_get_field()
      • Unique IDs
      • Filter: gutenbricks_bricks_theme_name
    • 🔌 Third Party Integrations
      • ACSS integration with GutenBricks
        • ACSS 2.8.0 Section padding missing
      • ACF / Meta Box integration
    • ❤️ Our Approach and Philosophy
  • 📖 Changelog
    • Known issues and bugs
    • Current Changelog
    • Past Changelog
      • v1.1-RC (Released as v1.1.0)
      • v1.0-RC (Released as v1.0)
Powered by GitBook
On this page
  1. Resources

❤️ Our Approach and Philosophy

Our Approach

At GutenBricks, we use our own plugins in-house as well as many popular add-ons for our agency clients. So integration with these tools is not only crucial to our plugin users but also to us. When it comes to integration and building a product, we wanted to first define our position as another plugin and mindset being a crossroad of plugins.

  • We are an adapter. So we will adapt to any edge cases of integration.

  • We are part of the Bricks ecosystem. We want to protect and grow this ecosystem together through open communication and collaboration.

  • We respect Bricks Builder as our mothership and will respect its product directions and philosophy as our foundation.

PreviousACF / Meta Box integrationNextKnown issues and bugs

Last updated 10 months ago

🤹