Requests and support

Send questions, bug reports and requests to IT Digital. Every request is reviewed, and changes ship in a release listed in the changelog.

Before you ask, check Component Status, the changelog and the component’s page. The answer may already be there.

Bugs

Include as much of this as you can:

• The component, with a Storybook link. The link keeps the brand and controls you set.
• The brand, the platform, and whether you use Web Components or React.
• Any other CSS or UI libraries on the page, such as Bootstrap or Tailwind.
• The package version, your browser and the viewport width.
• What you expected and what happened, with a screenshot.
• The smallest HTML or JSX that shows the problem.

Changes

Ask for a change when a component almost works but needs something new, such as a variant or setting. Say which component, what you need it to do, where it’s used, and what you’ve already tried. A change in Neighborhood works on every site, so it’s usually better than a one-site workaround.

New components

You don’t need a design or code. Describe the problem it solves, where it will appear, and any examples or mockups. New components start as Draft, so you can try them before they’re Ready.

Package access

Each project needs a token to install the private packages. Include the project or site, its repository, and whether a build or deploy environment needs it too. Installation shows where the token goes.

AI tools access

The Neighborhood MCP server needs a server URL and an access token, and you get both together. Include your name and team, the AI client you use (Claude, Claude Code, VS Code Copilot, Cursor or Windsurf) and the project you’re using it for. If the token changes, IT Digital sends the new one to everyone who has access.

Figma plugin beta

The Figma plugin is in beta with a small group of beta testers. To join, include your name and team, the Figma files or project you’d use it in, and the brands you design for.