1<!doctype html> 2<html lang="en"> 3 4<head> 5 <meta charset="utf-8"> 6 <meta http-equiv="x-ua-compatible" content="ie=edge"> 7 <meta name="viewport" content="width=device-width, initial-scale=1"> 8 <!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags --> 9 <title>basil.js // about</title> 10 <meta name="description" content="basil.js website"> 11 <meta name="author" content="Fabian Morón Zirfas"> 12 <link rel="stylesheet" href="/assets/css/styles.css"> 13</head> 14<!-- 15 the filtering of the titles for a body class is a little cumbersome. 16 If we have some special characters in the title we will have to filter it here 17 --> 18<body class="about"> 19 <div class="wrapper"> 20 <aside> 21 <a href="/"> 22 <div class="logo" id="logo"></div> 23 </a> 24 <div class="nav-o-meter"> 25 <ul class="bars"> 26 <li></li> 27 <li></li> 28 <li></li> 29 </ul> 30 </div> 31 <nav class="main-menu"> 32 <ul> 33 <!-- 34 loop all pages 35 exclude all entry layouts 36 include all default and the reference 37 exclude the root path 38 --> 39 40 41 <li class="menu-item active"><a href="/about/" 42 class="textgrow menu-link">about</a></li> 43 44 45 <li class="menu-item "><a href="/download/" 46 class="textgrow menu-link">download</a></li> 47 48 49 <li class="menu-item "><a href="/reference/" 50 class="textgrow menu-link">reference</a></li> 51 52 53 <li class="menu-item "><a href="/tutorials/" 54 class="textgrow menu-link">tutorials</a></li> 55 56 57 <li class="menu-item "><a href="/support/" 58 class="textgrow menu-link">support</a></li> 59 60 <li class="menu-item"><a href="https://basiljs.discourse.group/" target="_blank" 61 class="textgrow menu-link">forum</a></li> 62 63 64 <li class="menu-item "><a href="/gallery/" 65 class="textgrow menu-link">gallery</a></li> 66 67 68 69 </ul> 70 <div class="tweet"> 71 <div class="message"></div> 72 <div class="tweettime"></div> 73 <div class="twitter-link"><a href="https://twitter.com/basil_js" class="textgrow menu-link">@basil_js</a></div> 74 </div> 75 <div class="sponsors-text"> 76 Sponsors 77 </div> 78 <div class="logo"> 79 <a href="https://www.fhnw.ch/hgk/ivk"><img src="/assets/images/fhnw-logo.svg" alt="FHNW logo and link"></a> 80 </div> 81 <div class="logo"> 82 <a href="https://www.netlify.com/"><img src="/assets/images/netlify-logo-light-simple.svg" alt="Netlify logo"></a> 83 </div> 84 </nav> 85</aside> 86 <div class="main"> 87 <div id="content" class="wrapppper"> 88 <img src="/assets/images/aboutpage.jpg" alt="some examples what can be done with basil"><p><a href="https://www.fhnw.ch/de/die-fhnw/hochschulen/hgk">Academy of Art and Design Basel</a> 89<a href="http://thebaselschoolofdesign.ch">Visual Communication Institute / The Basel School of Design</a>, 90Basel, Switzerland</p> 91 92<p>A project initiated in <a href="https://web.fhnw.ch/hgk/projekte/interaktion/">Medium</a>.</p> 93 94<p>Current development: <a href="https://benedikt-gross.de">Benedikt GroÃ</a>, <a href="https://fabianmoronzirfas.me">Fabian Morón Zirfas</a>, <a href="https://teddavis.org">Ted Davis</a>, <a href="http://timorychert.de">Timo Rychert</a> 95Previous contributions: <a href="https://bescreen.de/">be:screen GmbH</a>, <a href="https://kennethfrederick.de">Ken Frederick</a>, <a href="https://www.philippadrian.com/">Philipp Adrian</a>, <a href="https://47nord.de">Stefan Landsbek</a> 96Initiated by: <a href="https://benedikt-gross.de">Benedikt GroÃ</a>, <a href="https://ludwigzeller.de">Ludwig Zeller</a>, <a href="https://teddavis.org">Ted Davis</a></p> 97 98<p>The basil.js project began in 2012, with an initiative to bring our visual communication students into generative design using their environment of choice, Adobe InDesign. For years, Adobeâs ExtendScript Toolkit enabled scripting every aspect of their software suite, however it was intended for developers with advanced programming knowledge. We invited Benedikt Groà for a workshop after learning about <a href="https://benedikt-gross.de/projects/diploma-generative-systeme-posters">his own explorations</a>, which led to a warning of how much code would be required for students to simply draw a rectangle. Realizing this could be simplified to address designers, he began developing a <a href="https://processing.org">Processing</a> inspired library that included useful functions from <a href="http://processingjs.org">processing.js</a>. We quickly realized the potential of this work and spent the following nine months developing a library that brings automation and scripting into layout (basil)! Released free as in speech under an MIT License on Feburary 28th 2013, weâve been excited to see its reach and usage throughout the design community. Over the past years, basil.js has enabled designers to bridge InDesignâs offering of precise typography within multi-page documents with data-driven and generative contents.</p> 99 100<p>While weâre continously impressed with publications making use of basil.js, thereâs always more to develop. Over the past few years weâve been fixing small bugs and adding missing features to a develop branch thatâs had tremendous contributions, particularly from <a href="https://github.com/trych">Timo Rychert</a> and <a href="https://github.com/fabianmoronzirfas">Fabian Morón Zirfas</a>. Most exciting for version 2.0, released <strong>__</strong>___ 2019, is the removal of <strong>b.</strong> from all basil.js functions! We had initially used it to avoid running into any ExtendScript namespace issues, but with it now safely removed, sketches can be hot-swapped between <a href="https://p5js.org">p5.js</a> and basil.js for exploring both real-time and multi-page generative designs.</p> 101 102<p>Used basil.js? 103Weâd love to see it! <a href="">Submit projects</a> to our <a href="">gallery</a>.</p> 104 105<p>Found a bug or missing feature? 106Make an issue on our <a href="">GitHub</a> and/or <a href="">contribute code</a>.</p> 107 108 </div> 109 <div class="line"></div> 110 <div class="line"></div> 111 <div class="line"></div> 112 </div> 113 <div class="guidelines"></div> 114 <footer> 115 <div class="impressum"> 116 117 </div> 118</footer> 119 </div> 120 121
121<script src="/assets/js/vendors~main.bundle.js" type="text/javascript" defer></script>
121 122 123
123<script src="/assets/js/main.bundle.js" type="text/javascript"></script>
123 124 </body> 125 126</html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.