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

grunt-template-publisher

v0.2.3

Published

uploads a Jimdo template to the Jimdo designs api.

Downloads

17

Readme

grunt-template-publisher

uploads a Jimdo template to the Jimdo designs api.

Getting Started

This plugin requires Grunt ~0.4.5

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-template-publisher --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-template-publisher');

The "template_publisher" task

Authentication

In order to Authenticate with the designs API you need a OAuth access token. The plugin will take care of getting one, but you have to provide a username and a password.

You can provide your username via the environment DMP_USER or specifiy it in the config (see the next section). When not given the plugin will promt you to enter it.

You can provide the password via the environment DMP_PASSWORD. When not given the plugin will promt you to enter it.

Overview

In your project's Gruntfile, add a section named template_publisher to the data object passed into grunt.initConfig(). Don't forget to change the design_id to the considering one of your template.

grunt.initConfig({
  publish: {
    options: {
      username: '[email protected]',
      design_id: 316,
      image_folder: 'gfx'
    }
  }
});

Activate a design version

When calling the grunt task, you can append --activate to the call and it will automatically activate the design version.

Options

options.username

optional Type: String

Your Jimdo design API username. You will be prompted to enter your username along with the password when not given.

options.design_id

Type: Integer

The Jimdo Designs API design id. Assigend when you created the template.

options.image_folder

optional Type: String

The local image folder, all files found in there, will be uploaded to the API.

options.endpoint

Type: String Default value: https://api.dmp.jimdo-server.com

The Designs API endpoint to use, defaults to the live system. But you can also use your development app.

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Release History

(Nothing yet)