npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

ab-translate-old

v1.1.0

Published

Quickly create AB Tests for texts without coding via [Wix Babel](https://bo.wix.com/wix-babel-webapp/babel) & [Guineapig](https://guineapig.wix.com/home).

Downloads

3

Readme

ab-translate

Quickly create AB Tests for texts without coding via Wix Babel & Guineapig.

The process requries two simple steps:

  1. Setup - one time config for a project to support the AB Translate flow
  2. AB Test - create as many text tests as you or your Writer needs without writing a single line of code!!!!1 😱

Setup

Do this once, for each project that you want to run translations tests in

Yoshi (new stack)

  1. Install the package npm i ab-translate --save or yarn add ab-translate
  2. Configure the specs defaults in your package.json file (example):
"yoshi": {
  "petriSpecs": {
    onlyForLoggedInUsers: false, // default: true
    scopes: ['my-projects-translation-scope'] // default: [<artifactId>]
  }
}
  1. Save the petri experiments object to the window (e.g. window.__EXPERIMENTS__ = '<%= experiments %>';). Notice: make sure that you conduct the experiments for the scope in step #2
  2. In the src/i18n.js file add the following code to the backend task (example)
import abTranslate from ‘ab-translate/dist/src/abTranslate-runtime’;

backend: {
  crossDomain: true,
  parse: translations => {
    try {
      return abTranslate(window.__EXPERIMENTS__, JSON.parse(translations));
    } catch (e) {
      return translations;
    }
  }
}

Wix Grunt (old stack)

  1. Install the package npm i ab-translate --save
  2. Configure the specs defaults in your local Gruntfile.js file:
grunt.modifyTask('petriExperiments', {
  options: {
    onlyForLoggedInUsers: false, // default: true
    scopes: ['my-projects-translation-scope'] // default: [<artifactId>]
  }
});
  1. Add the Angular abTranslateProvider to your index.vm file (example)
<script src="bower_components/ab-translate.git/abTranslate.angular-runtime.bundle.min.js"></script>
  1. Transform the translations using the abTranslateProvider and the project's experimentManagerProvider (example). Notice: make sure that you conduct the experiments for the scope in step #2
angular.module('myApp', [])
  .config(function($translateProvider, abTranslateProvider, experimentManagerProvider) {
    const preferredLanguage = $translateProvider.preferredLanguage();
    const translations = $translateProvider.translations()[preferredLanguage];
    const translationsWithExperiments = abTranslateProvider.abTranslate.default(
      experimentManagerProvider.experiments,
      translations
    );
    $translateProvider.translations(preferredLanguage, translationsWithExperiments);
  });

AB Test

  1. Go to the Babel translation system
  2. Select your project in the Current Project dropdown and select the Update tab Babel Home
  3. Look for the translation key you want to create a test for and click on the Edit button Update key
  4. Click on the Create AB Test button at the bottom of the modal Create AB Test
  5. Add as many alternatives as you want Add Alternatives
  6. Click the Set button. A 🔀 sign should appear next to your key.
  7. Verify your changes and click the Commit button. Commit Changes
  8. The changes will be pushed to github and a new build will be triggered. The new AB test will be detected and will be created.
  9. In the Next GA of the project you'll be able to see the spec in Guineapig. The spec name will be in the format specs.abTranslate.<scope>.<key>.
  10. Create an experiment and use Petri Sidekick to verify the variations!

Note1: When creating the experiment verify that you open it only for the languages where the keys were updated Note2: If the experiment is paused/killed/theres a bug in the system the first alternative (String #0) will be chosen so there shouldn't be any risks with this mechanism.

Merging an Experiment

Unfurtunately, at the moment there's no Quick Merge button that allows you to select the winning text. We'll work on one once the demand will rise. In the mean time you can simply set all the alternatives to the same text, close the experiments, and finally ask your dev to remove the unnecessary keys.

Experiments in languages other than EN

Creating an experiment in other languages is possible, however there's a few things you should keep in mind:

  1. Make sure that all variations are translated otherwise you'll have some variations fallback to English
  2. When you merge a multi-lingual experiment the winner for each language might be different (in some languages A may win, while in other languages B, or C, etc). Keep that in mind when you get to that point. We hope to make your life easier with an auto-merge flow in the future :)

Credits