@silexlabs/silex-plugin-11ty v0.0.41
Silex CMS
This is a Silex plugin to make Eleventy layouts visually with integration of any GraphQL API, allowing for a streamlined, code-free development process
Links
- User docs
- Developer docs
- Eleventy / 11ty
- Silex free/libre website builder
- Discussion about this plugin
- Issue with ideas and links to compatible CMSs
Features
- Visual design interface for Eleventy layouts
- Integration with GraphQL APIs for visula design on real data
- Expression builders for content, visibility conditions and loops
- Automatic generation of Eleventy-specific data files and front matter
- Support for localization and internationalization
- Live preview of data-driven designs
- Customizable SEO settings for collection pages
- Mock data capabilities for offline design testing
Add a gif or a live demo of your plugin here
Installation
This is how to use the plugin in your Silex instance or JS project
Add as a dependency
$ npm i --save @silexlabs/silex-plugin-11tyAdd to Silex client config:
// silex-client.js
import Eleventy from './js/silex-plugin-11ty/client.js'
export default function(config, options) {
  config.addPlugin(Eleventy, {
    dataSources: [{
      id: 'countries',
      type: 'graphql',
      name: 'Countries',
      url: 'https://countries.trevorblades.com/graphql',
      method: 'POST',
      headers: {
        'Content-Type': 'application/json',
      },
    }],
    // ... Other options for @silexlabs/grapesjs-data-source plugin - see https://github.com/silexlabs/grapesjs-data-source
    dir: {
      input: 'pages/',
      css: 'css',
    },
    // ... Other options for @silexlabs/silex-plugin-11ty plugin - see below
  })
}And expose the plugin to the front end:
// silex-server.js
const StaticPlugin = require('@silexlabs/silex/dist/plugins/server/plugins/server/StaticPlugin').default
const node_modules = require('node_modules-path')
console.log('node_modules', node_modules('@silexlabs/silex-plugin-11ty'))
module.exports = function(config, options) {
  config.addPlugin(StaticPlugin, {
    routes: [
      {
        route: '/js/silex-plugin-11ty/',
        path: node_modules('@silexlabs/silex-plugin-11ty') + '/@silexlabs/silex-plugin-11ty/dist/',
      },
    ],
  })
}Then start Silex with
npx @silexlabs/silex --client-config=silex-client.js --server-config=`pwd`/silex-server.js11ty configuration
Install required 11ty packages:
$ npm install  @11ty/eleventy @11ty/eleventy-fetch @11ty/eleventy-imgYou need to add a .eleventy.js file to your project, with the following content:
const { EleventyI18nPlugin } = require("@11ty/eleventy");
const Image = require("@11ty/eleventy-img");
  
module.exports = function(eleventyConfig) {
  // Serve CSS along with the site
  eleventyConfig.addPassthroughCopy({"silex/hosting/css/*.css": "css"});
  // For the fetch plugin
  eleventyConfig.watchIgnores.add('**/.cache/**')
  // i18n plugin
  eleventyConfig.addPlugin(EleventyI18nPlugin, {
    // any valid BCP 47-compatible language tag is supported
    defaultLanguage: "en", 
  });
  // Image plugin
  eleventyConfig.addShortcode("image", async function(src, alt, sizes) {
    let metadata = await Image(src, {
      widths: [300, 600],
      formats: ["avif", "jpeg"]
    });
    let imageAttributes = {
      alt,
      sizes,
      loading: "lazy",
      decoding: "async",
    };
    // You bet we throw an error on a missing alt (alt="" works okay)
    return Image.generateHTML(metadata, imageAttributes);
  });
};Options
You can pass an object containing all options of the GrapesJs DataSource plugin
Here are additional options specific to this plugin:
| Option | Description | Default | 
|---|---|---|
| fetchPlugin | Options to pass to 11ty fetch plugin | { duration: '1d', type: 'json' } | 
| imagePlugin | Enable filters which assume that your eleventy site has the 11ty image plugin installed | false | 
| i18nPlugin | Enable filters which assume that your eleventy site has the 11ty i18n plugin installed | false | 
| dir | An object with options to define 11ty directory structure | {} | 
| dir.input | Directory for 11ty input files, Silex will publish your site in this folder | (empty string) | 
| dir.silex | Directory for Silex files, Silex will publish your site in this folder. This is relative to the inputdirectory | silex | 
| dir.html | Directory for HTML files, Silex will generate HTML files (your site pages) in this folder. This is relative to the silexdirectory | (empty string) | 
| dir.assets | Directory for assets files, Silex will copy your assets (images, css, js, ...) to this folder when you publish your site. This is relative to the silexdirectory | assets | 
| dir.css | Directory for CSS files, Silex will generate CSS files to this folder when you publish your site. This is relative to the assetsdirectory | css | 
| urls | An object with options to define your site urls | {} | 
| urls.css | Url of the folder containing the CSS files, Silex will use this to generate links to the CSS files. | css | 
| urls.assets | Url of the folder containing the assets files, Silex will use this to generate links to the assets files. | assets | 
Dev notes
Hidden states
- States with hidden property set to true
- Not rendered in the HTML page as liquid
- Not visible in the properties panel
- Visible in completion of expressions
Public states
- In the UI they are represented by a list in the properties panel "states" section
- In the HTML page they are rendered as "assign" liquid blocks before the element
- You get these states with getState(id, true)
- They are typically properties custom states the user need to create expressions, e.g. to use in the append filter
Private states
- In the UI they are represented in the properties panel as element's properties
- In the HTML page they are rendered as liquid blocks in place of the element, for loops, echo, if, etc.
- You get these states with getState(id, false)
- They are typically properties of the element, like "innerHTML", "src", "href", etc.
Development
Clone the repository
$ git clone https://github.com/silexlabs/silex-plugin-11ty.git
$ cd silex-plugin-11tyInstall dependencies
$ npm iBuild and watch for changes
$ npm run build:watchStart the dev server on port 3000 with watch and debug
$ npm run devPublish a new version
$ npm test
$ npm run lint:fix
$ git commit -am "new feature"
$ npm version patch
$ git push origin main --follow-tagsLicense
MIT
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago