Skip to main content

Built by people who use the system too.

BEEQ grows through design reviews, implementation work, product feedback, accessibility conversations, and the small decisions that make shared systems reliable.

BEEQ is built and maintained by a cross-functional team at Endava. We bring designers, developers, accessibility advocates, and product-minded contributors together around one goal: helping teams create better digital products with less friction. We care about the details that make product work easier: shared foundations, reliable components, clear documentation, accessible patterns, and implementation guidance that reflects how teams actually build.

​
What we do

Design foundations

We maintain guidance for colour, typography, spacing, radius, stroke, shadows, and layout so teams can make consistent visual decisions.

Reusable components

We build production-ready web components that work across HTML, React, Angular, Vue, and other modern frontend stacks.

Documentation

We document how BEEQ works from both design and implementation perspectives, with examples that teams can adapt in real products.

Theming and customization

We support tokens, themes, modes, and component CSS variables so products can adapt BEEQ without drifting away from the system.

Accessibility guidance

We keep accessibility in the conversation from component APIs to usage guidance, so teams can make inclusive choices earlier.

Team support

We listen to feedback, review real product needs, and help teams find the right pattern when the answer is not obvious.

​
How we work

BEEQ is open source, source-backed, and shaped by real product use. We try to keep the system practical: if a guideline does not help someone design, build, review, or maintain a product, it probably needs to be clearer.
  • We work in the open — component development, bug fixes, and technical decisions happen on GitHub.
  • We treat source as canonical — documentation should match the current implementation, design tokens, public APIs, and accessibility behaviour.
  • We design for adoption — BEEQ should give teams a strong default without locking them into unnecessary vendor-specific patterns.
  • We improve through feedback — product teams, designers, developers, and contributors all help us see what needs to be refined next.

​
Work with us

You do not need to be on the core team to help BEEQ get better. If something is unclear, missing, hard to use, or no longer aligned with real product work, we want to hear about it.

Share feedback

Use the feedback button on any docs page or open a GitHub Issue when something needs attention.

Propose improvements

Suggest new patterns, component improvements, documentation updates, or design guidance when you see a recurring product need.

Contribute code or docs

Fix bugs, improve examples, update documentation, or help with component work. Start with the Contribution Guidelines.

Ask questions

If you are not sure where to start, contact us at beeq@endava.com. A good question is often the beginning of a better pattern.

​
Resources

GitHub

Follow the source code, issues, releases, and contribution workflow.

Storybook

Explore component states, variants, and interactive examples.

Components

Browse the component library and implementation guidance.

Contact the team

Reach out when you need help, feedback, or a conversation about BEEQ.