Introduction

The React Plug library provides components and hooks for personalizing applications in real-time that are easy for your marketing team to scale and maintain.

• Easy integration: personalize existing components without touching their code.
• Suspense-ready: take advantage of the latest React features to improve user experience.
• Server-side rendering: seamless integration with server-side frameworks like Next.js.
• Zero configuration: no setup steps are required.
• Type-safety: Typescript typings are included for improved development experience.
• Blazing-fast queries: double-digit millisecond latency for real-time evaluations.
• Playground integration: one-click to connect, no configuration needed.

Check out the Storybook to see some minimal examples in action, or the example folder for full code examples.

Getting Started

The following steps will walk you through installing the library and integrating it into your application.

[!TIP] If you are using Next.js, head over to the Plug Next.js library for a more integrated experience.

This guide assumes you're already familiar with some key concepts and tools around Croct, like Contextual Query Language (CQL) and the playground. If you're not, this 15-minute quickstart that will give you a hands-on overview of all the terms and tools you need to get started.

Installation

The recommended way to install the library is via NPM.

Run the following command to add the client as a dependency to your project and then install it:

npm install @croct/plug-react

Plugging in

You connect Croct to React with the <CroctProvider /> component. The <CroctProvider /> uses a regular React's <Context.Provider /> to wrap your React app and make the SDK available anywhere in your component tree.

We suggest putting the <CroctProvider /> somewhere high in your app, above any component that might be personalized, ideally in the top-level <App/> component.

import {render} from 'react-dom';
import {CroctProvider} from '@croct/plug-react';

function App() {
    return (
        <CroctProvider appId="<APP_ID>">
            <div>
                <h1>My first personalized app 🚀</h1>
            </div>
        </CroctProvider>
    );
}

render(<App/>, document.getElementById('root'));

Replace <APP_ID> with your public app ID that you can find at Workspaces > Applications > Setup. In case you don't have an account yet, you can use the sandbox application ID 00000000-0000-0000-0000-000000000000

Evaluating queries

Once your application is plugged in, you're ready to start personalizing your components using the <Personalization /> component or the useEvaluation hook.

We'll go through a simple example that shows how you can implement feature flags (also known as feature toggles) to conditionally renders a different button depending on the user's persona.

Let's first implement the use-case using the <Personalization /> component. It takes an query ( e.g. user's persona) and a render function, which tells the component how to render the UI, depending on the evaluation result.

This is what our component would look like:

import {ReactElement, Suspense} from 'react';
import {Personalization} from '@croct/plug-react';

function OnboardingPage(): ReactElement {
    return (
        <Suspense fallback="✨ Personalizing...">
            <Personalization query="user's persona is not 'developer'">
                {(isDeveloper: boolean) => isDeveloper
                    ? <a href="/docs">View docs</a>
                    : <a href="/share">Share with your developer</a>
                }
            </Personalization>
        </Suspense>
    )
}

If you don't want your component to suspend while loading, you can provide an initial state to be rendered instead:

import {ReactElement} from 'react';
import {Personalization} from '@croct/plug-react';

function OnboardingPage(): ReactElement {
    return (
        <Personalization query="user's persona is not 'developer'" initial={false}>
            {(isDeveloper: boolean) => isDeveloper
                ? <a href="/docs">View docs</a>
                : <a href="/share">Share with your developer</a>
            }
        </Personalization>
    )
}

Now, let's create a ViewDocsLink component to see the useEvaluation hook in action:

import {ReactElement, Suspense} from 'react';
import {useEvaluation} from '@croct/plug-react';

function ViewDocsLink(): ReactElement {
    const isDeveloper = useEvaluation<boolean>("user's persona is 'developer'");

    return (
        isDeveloper
            ? <a href="/docs">View docs</a>
            : <a href="/share">Share with your developer</a>
    );
}

export default function OnboardingPage(): ReactElement {
    return (
        <Suspense fallback="✨ Personalizing...">
            <ViewDocsLink/>
        </Suspense>
    )
}

If you run the application and there is no persona assigned to your profile, you will see the button for non-developers — otherwise, the button for sharing the code with developers. Check out Accessing the Plug instance for an example of how to save information in a user's profile.

Fault tolerance

We strongly recommend specifying the fallback property in client-side rendered applications to ensure your app behaves the same way regardless of the personalization. In this way, the UI will still be fully functional even in maintenance windows. Specifying a fallback is required for server-side rendering (SSR).

The following example shows how you can specify a fallback behaviour for the docs link:

import {ReactElement, Fragment, Suspense} from 'react';
import {Personalization, useEvaluation} from '@croct/plug-react';

function ViewDocsLink(): ReactElement {
    const isDeveloper = useEvaluation<boolean>("user's persona is 'developer'", {fallback: false});

    return <Fragment>{isDeveloper && <a href="/docs">View docs</a>}</Fragment>
}

export default function OnboardingPage(): ReactElement {
    return (
        <Suspense fallback="✨ Personalizing...">
            {/* Using the <Personalization /> component */}
            <Personalization query="user's persona is 'developer'" fallback={false}>
                {(isDeveloper: boolean) => (
                    <Fragment>
                        {isDeveloper && <a href="/docs">View docs</a>}
                    </Fragment>
                )}
            </Personalization>

            {/* Using useEvaluation hook */}
            <ViewDocsLink/>
        </Suspense>
    )
}

For a full list of the available options, please refer to the API documentation.

Using slots

Evaluating query is a flexible and powerful way to customize your UI. However, for components whose content changes too often, this approach can be overkill. For those cases, we encourage you to use the Slots feature instead. Using slots gives your team the flexibility to change the content or personalization rules whenever needed without touching the component code.

To render a slot, all you need to do is provide the id you configured in your Croct workspace. Based on the slot's personalization rules and the user's context, the component will decide which content show to that user. Notice that there's no logic on the client-side, meaning that your marketing or product team can freely change the slot content as they need without requiring an update to your React app.

For the next example, we assume that you have already defined a slot with id home-banner in your Croct workspace with the following structure:

type HomeBannerContent = {
    title: string,
    subtitle: string,
    cta: {
        label: string,
        link: string,
    },
};

To render the content of the slot, you can either use the <Slot /> component or the useContent hook.

Here's how to use the <Slot /> component:

import {ReactElement, Suspense} from 'react';
import {Slot} from '@croct/plug-react';

type HomeBannerContent = {
    title: string,
    subtitle: string,
    cta: {
        label: string,
        link: string,
    },
};

export default function OnboardingPage(): ReactElement {
    return (
        <Suspense fallback="✨ Personalizing content...">
            <Slot id="home-banner">
                {({
                    title,
                    subtitle,
                    cta
                }: HomeBannerContent) => (
                    <div>
                        <strong>{title}</strong>
                        <p>{subtitle}</p>
                        <a href={cta.link}>{cta.label}</a>
                    </div>
                )}
            </Slot>
        </Suspense>
    )
}

To avoid the component from suspending while loading, you can provide an initial state to be rendered instead:

import {ReactElement} from 'react';
import {Slot} from '@croct/plug-react';

type HomeBannerContent = {
    title: string,
    subtitle: string,
    cta: {
        label: string,
        link: string,
    },
};

export default function OnboardingPage(): ReactElement {
    return (
        <Slot id="home-banner" initial={null}>
            {(props: HomeBannerContent | null) => (
                props === null
                    ? '✨ Personalizing...'
                    : (
                        <div>
                            <strong>{props.title}</strong>
                            <p>{props.subtitle}</p>
                            <a href={props.cta.link}>{props.cta.label}</a>
                        </div>
                    )
            )}
        </Slot>
    )
}

And here's an example using the useContent hook:

import {ReactElement, Suspense} from 'react';
import {useContent} from '@croct/plug-react';

type HomeBannerContent = {
    title: string,
    subtitle: string,
    cta: {
        label: string,
        link: string,
    },
};

function HomeBanner(): ReactElement {
    const {
        title,
        subtitle,
        cta
    } = useContent<HomeBannerContent>('home-banner');

    return (
        <div>
            <strong>{title}</strong>
            <p>{subtitle}</p>
            <a href={cta.link}>{cta.label}</a>
        </div>
    )
}

export default function HomePage(): ReactElement {
    return (
        <Suspense fallback="Personalizing content...">
            <HomeBanner/>
        </Suspense>
    )
}

You can specify the version of the slot by passing a versioned ID in the form id@version. For example, passing home-banner@1 will fetch the content for the home-banner slot in version 1. Not specifying a version number is the same as passing home-banner@latest, which will load the latest version of the slot.

✅ Best practice
It's strongly recommended to specify a slot version for production deployments. That way, you ensure the front end will always receive content with the expected schema while your team can freely evolve the content's schema in parallel.

Fault tolerance

The following example shows how you can specify a fallback state for the home-banner slot:

import {ReactElement, Suspense} from 'react';
import {Slot, useContent} from '@croct/plug-react';

type HomeBannerContent = {
    title: string,
    subtitle: string,
    cta: {
        label: string,
        link: string,
    },
};

const fallbackBanner: HomeBannerContent = {
    title: 'Default title',
    subtitle: 'Default subtitle',
    cta: {
        label: 'Try now',
        link: 'https://croct.com',
    }
};

function HomeBanner(): ReactElement {
    const {
        title,
        subtitle,
        cta
    } = useContent<HomeBannerContent>('home-banner', {fallback: fallbackBanner});

    return (
        <div>
            <strong>{title}</strong>
            <p>{subtitle}</p>
            <a href={cta.link}>{cta.label}</a>
        </div>
    )
}

export default function HomePage(): ReactElement {
    return (
        <Suspense fallback="Personalizing content...">
            {/* Using the <Slot /> component */}
            <Slot id="home-banner" fallback={fallbackBanner}>
                {({
                    title,
                    subtitle,
                    cta
                }: HomeBannerContent) => (
                    <div>
                        <strong>{title}</strong>
                        <p>{subtitle}</p>
                        <a href={cta.link}>{cta.label}</a>
                    </div>
                )}
            </Slot>

            {/* Using the useContent hook */}
            <HomeBanner/>
        </Suspense>
    )
}

Again, we strongly recommend always providing a value for the fallback property. For a full list of the available options, please refer to the API documentation.

💡 ProTip

In the previous examples, you may have noticed that we specified the content type in the userFetch call and in the <Slot /> component's render function to have the benefit of strong typing.

For an even more robust approach, you can also declare the type of all available slots in a single declaration file using module augmentation as follows:

// slots.d.ts
import {HomeBanner} from './HomePage';

declare module '@croct/plug/slot' {
    interface SlotMap {
        'home-banner': HomeBanner;
    }
}

If you use an IDE with Typescript code completion support, you will get autocomplete suggestions for slot IDs and content properties as a bonus:

Server-side rendering

You can use the same components and hooks on the server-side by simply providing an initial state which is used to pre-render on the server - the personalization happens transparently on the client during the initial render. That means it's SEO friendly and can be cached with no performance overhead.

Notice that the methods exposed by the Plug work only on the client-side. Therefore, if you are using useCroct, the operations have to be executed inside the useEffect hook or client-side callbacks, such as onClick or onChange , for example.

Accessing the Plug instance

This library is built on top of the PlugJS. You can access the Plug instance through the useCroct hook to track events, login and logout users, and more.

In the following example we use the useCroct to get the Plug instance and set an attribute to the user profile:

import {ReactElement, useCallback} from 'react';
import {useCroct} from '@croct/plug-react';

export default function DeveloperButton(): ReactElement {
    const croct = useCroct();
    const setPersona = useCallback(
        () => croct.user.edit()
            .set('custom.persona', 'developer')
            .save(),
        [croct],
    );

    return (<button onClick={setPersona}>I'm a developer</button>);
}

Component API reference

This reference documents all components available in the library.

<CroctProvider />

The <CroctProvider /> component leverages React's Context API to make a configured Plug instance available throughout a React component tree.

Properties

The component takes the followings properties:

| Option | Type | Required | Default Value | Description | |--------------------------|--------------|----------|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | appId | string | Yes | None | The ID of the application you set up on Croct. | | debug | boolean | No | false | If true, turns on debug mode, which logs helpful messages to the console. | | track | boolean | No | true | If true, enables the automatic event tracking on initialization. | | clientId | string | No | None | The ID of the client using the application. | | token | string|null | No | None | The JWT token issued by Croct. If null, clears any token specified on previous calls. | | userId | string | No | None | The ID of the user logged into the application. Internally, the SDK will issue a token using the specified ID as the subject claim of the token. The token and userId options are mutually exclusive. | | tokenScope | string | No | global | Defines how the SDK should synchronize the token across multiple tabs, see token scopes for more details. | | eventMetadata | JSON | No | None | Any additional information that may be useful to include as part of the event metadata. A common use case is to record the version of the application for future reference. | | logger | object | No | None | A custom logger to handle log messages. By default, all logs are suppressed. | | urlSanitizer | function | No | None | A function to sanitize URLs that allows removing sensitive information from URLs, such as tokens, that should not be sent to the platform. | | baseEndpointUrl | string | No | None | The base URL to use for the API calls. By default, the SDK will use the production endpoint. | | cidAssignerEndpointUrl | string | No | None | The URL to use for the client ID assignment. By default, the SDK will use the production endpoint. |

Code Sample

Here's a simple example showing how to initialize the Plug instance:

import {CroctProvider} from '@croct/plug-react';

function App() {
    return (
        <CroctProvider appId="<APP_ID>">
            <div>
                <h1>My first personalized app 🚀</h1>
            </div>
        </CroctProvider>
    );
}

Replace "<APP_ID>" with your public app ID that you can find at Workspaces > Applications > API Keys.

<Personalization />

The <Personalization /> component evaluates and renders a CQL query.

Properties

The component takes the followings properties:

| Option | Type | Required | Description | |--------------|----------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | query | string | Yes | The CQL query to evaluate. | | children | Function | Yes | A callback to render the result. | | fallback | Result | No | A value to render when the evaluation fails. If not specified, the hook will throw an exception in case of failures. | | initial | Result | SSR only | A value to render while loading, required for server-side rendering. If not specified, the rendering will suspend. | | timeout | number | No | The maximum evaluation time in milliseconds. Once reached, the evaluation will fail. | | attributes | JSON | No | A map of attributes to inject in the evaluation context. For example, passing the attributes {cities: ['New York', 'San Francisco']} you can reference them in queries like context's cities include location's city. | | cacheKey | string | No | An identifier that allows keeping the cached result separate from other cached items. By default, the cache key is formed from the query and attributes. | | expiration | number | No | The cache expiration time in milliseconds, extended on every render. If negative, the cache never expires. By default, the cache lifespan is set to 60000 (1 minute). |

Code Sample

Here's a simple example showing how to evaluate the user's persona:

import {ReactElement} from 'react';
import {Personalization} from '@croct/plug-react';

function PersonaBadge(): ReactElement {
    return (
        <Personalization query="user's persona or else 'unknown'">
            {persona => (<span>{persona}</span>)}
        </Personalization>
    );
}

<Slot />

The <Slot /> component fetches and renders a slot.

Properties

The component takes the followings properties:

| Option | Type | Required | Description | |-------------------|----------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | id | string | Yes | The ID of the slot to fetch. | | children | Function | Yes | A callback to render the result. | | fallback | Result | No | A value to render when the fetch fails. If not specified, the hook will throw an exception in case of failures. | | preferredLocale | string | No | The preferred locale to fetch. If not specified or not available, the hook will fetch the default locale. | | initial | Result | SSR only | A value to render while loading, required for server-side rendering. If not specified, the rendering will suspend. | | cacheKey | string | No | An identifier that allows keeping the cached result separate from other cached items. By default, the cache key is formed from the query and attributes. | | expiration | number | No | The cache expiration time in milliseconds, extended on every render. If negative, the cache never expires. By default, the cache lifespan is set to 60000 (1 minute). |

Code Sample

Here's a simple example showing how to render a banner in a slot:

import {ReactElement} from 'react';
import {Slot} from '@croct/plug-react';

function HeroBanner(): ReactElement {
    return (
        <Slot id="hero">
            {({
                title,
                subtitle
            }) => (
                <div>
                    <h1>{title}</h1>
                    <p>{subtitle}</p>
                </div>
            )}
        </Slot>
    );
}

Hook API reference

This reference documents all hooks available in the library.

useCroct

The useCroct hook provides access to the Plug instance.

Signature

The hook has the following signature:

useCroct(): Plug

Code Sample

Here's a simple example showing how anonymize a user:

import {ReactElement, useCallback} from 'react';
import {useCroct} from '@croct/plug-react';

function LogoutButton(): ReactElement {
    const croct = useCroct();
    const anonymize = useCallback(() => croct.anonymize(), [croct]);

    return <button type="button" onClick={anonymize}>Logout</button>
}

useEvaluation

The useEvaluation hook evaluates a CQL query.

Signature

The hook has the following signature:

 function useEvaluation<Result extends JsonValue>(query: string, options: Options = {}): Result

These are the currently supported options:

| Option | Type | Description | |--------------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | fallback | Result | The value returned when the evaluation fails. If not specified, the hook will throw an exception in case of failures. | | timeout | number | The maximum evaluation time in milliseconds. Once reached, the evaluation will fail. | | attributes | JSON | The map of attributes to inject in the evaluation context. For example, passing the attributes {cities: ['New York', 'San Francisco']} you can reference them in querys like context's cities include location's city. | | cacheKey | string | An identifier that allows keeping the cached result separate from other cached items. By default, the cache key is formed from the query and attributes. | | expiration | number | The cache expiration time in milliseconds, extended on every render. If negative, the cache never expires. By default, the cache lifespan is set to 60000 (1 minute). |

Code Sample

Here's a simple example showing how to evaluate the user's persona:

import {ReactElement} from 'react';
import {useEvaluation} from '@croct/plug-react';

function PersonaBadge(): ReactElement {
    const persona = useEvaluation<string>("user's persona or else 'unknown'", {fallback: 'unknown'});

    return <span>{persona}</span>
}

useContent

The useContent hook fetches the content of a slot.

Signature

The hook has the following signature:

function useContent(slotId: string, options: Options = {}): JsonObject

These are the currently supported options:

| Option | Type | Description | |-------------------|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | fallback | Content | The content returned when the fetch fails. If not specified, the hook will throw an exception in case of failures. | | preferredLocale | string | The preferred locale to fetch. If not specified or not available, the hook will fetch the default locale. | | cacheKey | string | An identifier that allows keeping the cached content separate from other cached items. By default, the cache key is formed from the slot ID. | | expiration | number | The cache expiration time in milliseconds, extended on every render. If negative, the cache never expires. By default, the cache lifespan is set to 60000 (1 minute). |

Code Sample

Here's a simple example showing how to fetch the content for a banner:

import {ReactElement} from 'react';
import {useContent} from '@croct/plug-react';

type HomeBannerContent = {
    title: string,
    subtitle: string,
    cta: {
        label: string,
        link: string,
    },
};

export default function HeroBanner(): ReactElement {
    const {
        title,
        subtitle
    } = useContent<HomeBannerContent>('hero');

    return (
        <div>
            <h1>{title}</h1>
            <p>{subtitle}</p>
        </div>
    );
}

Standalone function reference

This reference documents all standalone functions available in the library.

evaluate

The evaluate function evaluates a CQL query on the server-side and returns the result.

Signature

The function has the following signature:

function evaluate(query: string, options: EvaluationOptions): Promise<JsonValue>

These are the currently supported options:

| Option | Type | Required | Description | |----------------------------|--------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | apiKey | string | Yes | The private API key of the application. This is a private key that should never be exposed to the client-side. | | baseEndpointUrl | string | No | The base URL of the Evaluation API. Defaults to the production endpoint. | | fallback | JSON | No | The value returned when the evaluation fails. If not specified, the function will throw an exception in case of failures. | | timeout | number | No | The maximum evaluation time in milliseconds. Once reached, the evaluation will fail. | | clientId | string | No | A UUID v4 that uniquely identifies the client across multiple evaluations. You should generate this identifier on your server-side using a random, cryptographically secure generator and ensure it doesn't change throughout the user journey (e.g. store in cookies). If not specified, the evaluation will run in an anonymous context. | | clientIp | string | No | The IP address of the client to determine the location. The IP is only used to determine the location and then discarded. | | userAgent | string | No | The user agent of the client to determine the device. | | userToken | string | No | The token that uniquely identifies the user. You can use this to provide consistent experiences across multiple channels. | | context | JSON | No | The evaluation context. | | context.timeZone | string | No | The time zone of the client. | | context.campaign | JSON | No | The marketing campaign that brought the user to the application. | | context.campaign.name | string | No | The name of the campaign. | | context.campaign.source | string | No | The source of the campaign. For example, "google", "newsletter", "facebook". | | context.campaign.medium | string | No | The marketing medium. For example, "cpc", "banner", "ads". | | context.campaign.term | string | No | The campaign keywords. For example, "smartphone online sale". | | context.campaign.content | string | No | The campaign content. For example, "top-banner", "cta", "sidebar". | | context.page | JSON | No | The page the user is currently viewing. | | context.page.url | string | Yes | The URL of the page. | | context.page.title | string | No | The title of the page. | | context.page.referrer | string | No | The URL of the page that referred the user to the current page. | | context.attributes | JSON | No | The map of attributes to inject in the evaluation context. For example, passing the attributes {cities: ['New York', 'San Francisco']} you can reference them in querys like context's cities include location's city. | | extra | JSON | No | Additional options to pass to the fetch function. |

Code Sample

Here's a simple example showing how to evaluate a CQL query:

import {evaluate} from '@croct/plug/api';

const result = await evaluate("user's persona", {
    apiKey: process.env.CROCT_API_KEY,
});

fetchContent

The fetchContent function fetches the content for a slot on the server-side and returns the result.

Signature

The function has the following signature:

function fetchContent(slotId: string, options: FetchOptions): Promise<{content: JsonValue}>

These are the currently supported options:

| Option | Type | Required | Description | |----------------------------|---------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | apiKey | string | Yes | The private API key of the application. This is a private key that should never be exposed to the client-side. | | baseEndpointUrl | string | No | The base URL of the Content API. Defaults to the production endpoint. | | fallback | JSON | No | The value returned when the fetch fails. If not specified, the function will throw an exception in case of failures. | | static | boolean | No | Whether to fetch the static content. If not specified, the function will fetch the dynamic content. | | timeout | number | No | The maximum fetch time in milliseconds. Once reached, the fetch will fail. | | previewToken | string | No | The token that enables preview mode. | | preferredLocale | string | No | The preferred locale to fetch. If not specified or not available, the hook will fetch the default locale. | | clientId | string | No | A UUID v4 that uniquely identifies the client across multiple evaluations. You should generate this identifier on your server-side using a random, cryptographically secure generator and ensure it doesn't change throughout the user journey (e.g. store in cookies). If not specified, the evaluation will run in an anonymous context. | | clientIp | string | No | The IP address of the client to determine the location. The IP is only used to determine the location and then discarded. | | userAgent | string | No | The user agent of the client to determine the device. | | userToken | string | No | The token that uniquely identifies the user. You can use this to provide consistent experiences across multiple channels. | | context | JSON | No | The evaluation context. | | context.timeZone | string | No | The time zone of the client. | | context.campaign | JSON | No | The marketing campaign that brought the user to the application. | | context.campaign.name | string | No | The name of the campaign. | | context.campaign.source | string | No | The source of the campaign. For example, "google", "newsletter", "facebook". | | context.campaign.medium | string | No | The marketing medium. For example, "cpc", "banner", "ads". | | context.campaign.term | string | No | The campaign keywords. For example, "smartphone online sale". | | context.campaign.content | string | No | The campaign content. For example, "top-banner", "cta", "sidebar". | | context.page | JSON | No | The page the user is currently viewing. | | context.page.url | string | Yes | The URL of the page. | | context.page.title | string | No | The title of the page. | | context.page.referrer | string | No | The URL of the page that referred the user to the current page. | | context.attributes | JSON | No | The map of attributes to inject in the evaluation context. For example, passing the attributes {cities: ['New York', 'San Francisco']} you can reference them in querys like context's cities include location's city. | | extra | JSON | No | Additional options to pass to the fetch function. |

Support

If this documentation has not answered all your questions, don't worry. Here are some alternative ways to get help from the Croct community.

Stack Overflow

Someone else from the community may have already asked a similar question or may be able to help with your problem.

The Croct team will also monitor posts with the "croct" tag. If there aren't any existing questions that help, please ask a new one.

GitHub

If you have what looks like a bug, or you would like to make a feature request, please open a new issue on GitHub.

Before you file an issue, a good practice is to search for issues to see whether others have the same or similar problems. If you are unable to find an open issue addressing the problem, then feel free to open a new one.

Slack Channel

Many people from the Croct community hang out on the Croct Slack Group. Feel free to join us and start a conversation.

License

This project is released under the MIT License.