[{"_1":2,"_156":-5,"_157":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_135":136},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_85":-5,"_86":87,"_126":-5,"_127":11,"_128":17,"_129":11,"_130":-5,"_131":11,"_132":-5,"_133":134},"canonicalUrl","https://hub.docker.com/r/hankhendrix/meme-generator/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","hankhendrix","reponame","meme-generator","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":-5,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":65,"_66":67,"_68":11,"_69":29,"_70":71,"_76":17,"_77":78,"_82":29,"_83":84},"categories",[],"content_types",[40],"image","date_registered","2016-03-23T04:11:27.765524Z","description","Write your's today!","is_private","last_updated","2016-04-10T21:39:52.986703Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.distribution.manifest.v1+prettyjws","name","pull_count",445,"repository_type","star_count",2,"status",1,"status_description","active","source","collaborator_count",0,"full_description","![](https://cloud.githubusercontent.com/assets/110953/7877439/6a69d03e-0590-11e5-9fac-c614246606de.png)\n## Polymer Starter Kit\n\n> A starting point for building web applications with Polymer 1.0\n\n### Included out of the box: (test)\n\n* [Polymer](https://www.polymer-project.org/), [Paper](https://elements.polymer-project.org/browse?package=paper-elements), [Iron](https://elements.polymer-project.org/browse?package=iron-elements) and [Neon](https://elements.polymer-project.org/browse?package=neon-elements) elements\n* [Material Design](http://www.google.com/design/spec/material-design/introduction.html) layout\n* Routing with [Page.js](https://visionmedia.github.io/page.js/)\n* Unit testing with [Web Component Tester](https://github.com/Polymer/web-component-tester)\n* Optional offline setup through [Platinum](https://elements.polymer-project.org/browse?package=platinum-elements) Service Worker elements\n* End-to-end Build Tooling (including [Vulcanize](https://github.com/Polymer/vulcanize))\n* [Recipes](/docs/README.md/) for ES2015 support, Polymer performance, using Chrome Dev Editor, Deploying to GitHub Pages, Deploying to Firebase, Mobile Chrome Apps and lint tools.\n\n### Demo\nSee latest Polymer Starter Kit Demo (from master) at https://polymerelements.github.io/polymer-starter-kit/\n\n### Tutorials\n\nCheck out the Polymer Starter Kit tutorials on [polymer-project.org](https://www.polymer-project.org):\n\n* [Set up the PSK](https://www.polymer-project.org/1.0/docs/start/psk/set-up.html)\n* [Create a page](https://www.polymer-project.org/1.0/docs/start/psk/create-a-page.html)\n* [Deploy the PSK to the web](https://www.polymer-project.org/1.0/docs/start/psk/deploy.html)\n\n## Getting Started\n\nTo take advantage of Polymer Starter Kit you need to:\n\n1. Get a copy of the code.\n2. Install the dependencies if you don't already have them.\n3. Modify the application to your liking.\n4. Deploy your production code.\n\n### Get the code\n\n[Download](https://github.com/polymerelements/polymer-starter-kit/releases/latest) and extract Polymer Starter Kit to where you want to work. The project comes in two flavours - Light and Full.\n\n**Beginners**: Try Polymer Starter Kit Light. This doesn't require any extra dependencies nor knowledge of modern front-end tooling. This option is good for prototyping if you haven't build a Polymer app before.\n\n**Intermediate - Advanced**: Use the full version of Polymer Starter Kit. This comes with all the build tools you'll need for testing and productionising your app so it's nice and lean. You'll need to run a few extra commands to install the tools we recommend but it's worth it to make sure your final app is super optimised.\n\n:warning: **Important**: Polymer Starter Kit, and Polymer Starter Kit Light, both contain dotfiles (files starting with a `.`). If you're copying the contents of the Starter Kit to a new location make sure you bring along these dotfiles as well! On Mac, [enable showing hidden files](http://ianlunn.co.uk/articles/quickly-showhide-hidden-files-mac-os-x-mavericks/), then try extracting/copying Polymer Starter Kit again. This time the dotfiles needed should be visible so you can copy them over without issues.\n\nRob Dodson has a fantastic [PolyCast video](https://www.youtube.com/watch?v=xz-yixRxZN8) available that walks through using Polymer Starter Kit. An [end-to-end with Polymer](https://www.youtube.com/watch?v=1f_Tj_JnStA) and Polymer Starter Kit talk is also available.\n\n### Install dependencies\n\n#### Quick-start (for experienced users)\n\nWith Node.js installed, run the following one liner from the root of your Polymer Starter Kit download:\n\n```sh\nnpm install -g gulp bower && npm install && bower install\n```\n\n#### Prerequisites (for everyone)\n\nThe full starter kit requires the following major dependencies:\n\n- Node.js, used to run JavaScript tools from the command line.\n- npm, the node package manager, installed with Node.js and used to install Node.js packages.\n- gulp, a Node.js-based build tool.\n- bower, a Node.js-based package manager used to install front-end packages (like Polymer).\n- The starter kit gulp build process uses platform specific tools which is handled by node-gyp which is included in node.js. See https://github.com/nodejs/node-gyp/blob/master/README.md for additional platform specific dependencies.\n\n**To install dependencies:**\n\n1) Check your Node.js version.\n\n```sh\nnode --version\n```\n\nThe version should be at or above 0.12.x.\n\n2) If you don't have Node.js installed, or you have a lower version, go to [nodejs.org](https://nodejs.org) and click on the big green Install button.\n\n3) Install `gulp` and `bower` globally.\n\n```sh\nnpm install -g gulp bower\n```\n\nThis lets you run `gulp` and `bower` from the command line.\n\n4) Install the starter kit's local `npm` and `bower` dependencies.\n\n```sh\ncd polymer-starter-kit && npm install && bower install\n```\n\nThis installs the element sets (Paper, Iron, Platinum) and tools the starter kit requires to build and serve apps.\n\n### Development workflow\n\n#### Serve / watch\n\n```sh\ngulp serve\n```\n\nThis outputs an IP address you can use to locally test and another that can be used on devices connected to your network.\n\n#### Run tests\n\n```sh\ngulp test:local\n```\n\nThis runs the unit tests defined in the `app/test` directory through [web-component-tester](https://github.com/Polymer/web-component-tester).\n\nTo run tests Java 7 or higher is required. To update Java go to http://www.oracle.com/technetwork/java/javase/downloads/index.html and download ***JDK*** and install it.\n\n#### Build & Vulcanize\n\n```sh\ngulp\n```\n\nBuild and optimize the current project, ready for deployment. This includes vulcanization, image, script, stylesheet and HTML optimization and minification.\n\n## Application Theming & Styling\n\nPolymer 1.0 introduces a shim for CSS custom properties. We take advantage of this in `app/styles/app-theme.html` to provide theming for your application. You can also find our presets for Material Design breakpoints in this file.\n\n[Read more](https://www.polymer-project.org/1.0/docs/devguide/styling.html) about CSS custom properties.\n\n### Styling\n1. ***main.css*** - to define styles that can be applied outside of Polymer's custom CSS properties implementation. Some of the use-cases include defining styles that you want to be applied for a splash screen, styles for your application 'shell' before it gets upgraded using Polymer or critical style blocks that you want parsed before your elements are.\n2. ***app-theme.html*** - to provide theming for your application. You can also find our presets for Material Design breakpoints in this file.\n3. ***shared-styles.html*** - to share styles between elements and index.html.\n4. ***element styles only*** - styles specific to element. These styles should be inside the `` inside `template`.\n\n ```HTML\n \n \n \n ```\n\nThese style files are located in the [styles folder](app/styles/).\n\n## Unit Testing\n\nWeb apps built with Polymer Starter Kit come configured with support for [Web Component Tester](https://github.com/Polymer/web-component-tester) - Polymer's preferred tool for authoring and running unit tests. This makes testing your element based applications a pleasant experience.\n\n[Read more](https://github.com/Polymer/web-component-tester#html-suites) about using Web Component tester.\n\n## Dependency Management\n\nPolymer uses [Bower](http://bower.io) for package management. This makes it easy to keep your elements up to date and versioned. For tooling, we use npm to manage Node.js-based dependencies.\n\nComponents installed by Bower live in the `app/bower_components` directory. This location is specified by the `.bowerrc` file. Many projects which follow Yeoman conventions place the `bower_components` directory outside of the `app` directory and then mount it using a server. This causes problems for tools like [Vulcanize](https://github.com/polymer/vulcanize) and [web-component-shards](https://github.com/PolymerLabs/web-component-shards) which rely on relative paths. We've chosen to simplify things and have `bower_components` live inside of `app` to resolve these issues.\n\n## Deploy\n\n### Github Pages\n\n1. Uncomment this line `// app.baseUrl = '/polymer-starter-kit/';` in app.js near the top\n2. Change `app.baseUrl = '/polymer-starter-kit/';` to `app.baseUrl = '/your-pathname/';` (ex: if you repo is `github.com/username/bobs-awesome-site` you would change this to `app.baseUrl = '/bobs-awesome-site/';`)\n3. Run `gulp build-deploy-gh-pages` from command line\n4. To see changes wait 1-2 minutes then load Github pages for your app (ex: https://polymerelements.github.io/polymer-starter-kit/)\n\n[See more details](/docs/deploy-to-github-pages.md/)\n\n### Firebase\n\n[See detail recipe](/docs/deploy-to-firebase-pretty-urls.md/)\n\n## Service Worker\n\nPolymer Starter Kit offers an optional offline experience thanks to Service Worker and the [Platinum Service Worker elements](https://github.com/PolymerElements/platinum-sw). New to Service Worker? Read the following [introduction](http://www.html5rocks.com/en/tutorials/service-worker/introduction/) to understand how it works.\n\nOur optional offline setup should work well for relatively simple applications. For more complex apps, we recommend learning how Service Worker works so that you can make the most of the Platinum Service Worker element abstractions.\n\n### Enable Service Worker support?\n\nTo enable Service Worker support for Polymer Starter Kit project use these 3 steps:\n\n1. Uncomment Service Worker code in index.html\n ```HTML\n \n \n ```\n2. Uncomment Service Worker code in elements.html\n\n ```HTML\n \n \n ```\n3. Uncomment 'cache-config' in the `runSequence()` section of the 'default' gulp task, like below:\n[(gulpfile.js)](https://github.com/PolymerElements/polymer-starter-kit/blob/master/gulpfile.js)\n\n ```JavaScript\n // Build Production Files, the Default Task\n gulp.task('default', ['clean'], function (cb) {\n runSequence(\n ['copy', 'styles'],\n 'elements',\n ['images', 'fonts', 'html'],\n 'vulcanize', 'cache-config',\n cb);\n });\n ```\n\n#### Filing bugs in the right place\n\nIf you experience an issue with Service Worker support in your application, check the origin of the issue and use the appropriate issue tracker:\n\n* [sw-toolbox](https://github.com/GoogleChrome/sw-toolbox/issues)\n* [platinum-sw](https://github.com/PolymerElements/platinum-sw/issues)\n* [platinum-push-notifications-manager](https://github.com/PolymerElements/platinum-push-messaging)\n* For all other issues, feel free to file them [here](https://github.com/polymerelements/polymer-starter-kit/issues).\n\n#### I get an error message about \"Only secure origins are allowed\"\n\nService Workers are only available to \"secure origins\" (HTTPS sites, basically) in line with a policy to prefer secure origins for powerful new features. However http://localhost is also considered a secure origin, so if you can, developing on localhost is an easy way to avoid this error. For production, your site will need to support HTTPS.\n\n#### How do I debug Service Worker?\n\nIf you need to debug the event listener wire-up use `chrome://serviceworker-internals`.\n\n#### What are those buttons on chrome://serviceworker-internals?\n\nThis page shows your registered workers and provides some basic operations.\n\n* Unregister: Unregisters the worker.\n* Start: Starts the worker. This would happen automatically when you navigate to a page in the worker's scope.\n* Stop: Stops the worker.\n* Sync: Dispatches a 'sync' event to the worker. If you don't handle this event, nothing will happen.\n* Push: Dispatches a 'push' event to the worker. If you don't handle this event, nothing will happen.\n* Inspect: Opens the worker in the Inspector.\n\n#### Development flow\n\nIn order to guarantee that the latest version of your Service Worker script is being used, follow these instructions:\n\n* After you made changes to your service worker script, close all but one of the tabs pointing to your web application\n* Hit shift-reload to bypass the service worker as to ensure that the remaining tab isn't under the control of a service worker\n* Hit reload to let the newer version of the Service Worker control the page.\n\nIf you find anything to still be stale, you can also try navigating to `chrome:serviceworker-internals` (in Chrome), finding the relevant Service Worker entry for your application and clicking 'Unregister' before refreshing your app. This will (of course) only clear it from the local development machine. If you have already deployed to production then further work will be necessary to remove it from your users' machines.\n\n#### Disable Service Worker support after you enabled it\n\nIf for any reason you need to disable Service Worker support after previously enabling it, you can remove it from your Polymer Starter Kit project using these 4 steps:\n\n1. Remove references to the platinum-sw elements from your application [index](https://github.com/PolymerElements/polymer-starter-kit/blob/master/app/index.html).\n2. Remove the two Platinum Service Worker elements (platinum-sw/..) in [app/elements/elements.html](https://github.com/PolymerElements/polymer-starter-kit/blob/master/app/elements/elements.html)\n3. Remove 'precache' from the list in the 'default' gulp task ([gulpfile.js](https://github.com/PolymerElements/polymer-starter-kit/blob/master/gulpfile.js))\n4. Navigate to `chrome://serviceworker-internals` and unregister any Service Workers registered by Polymer Starter Kit for your app just in case there's a copy of it cached.\n\n## Add to home screen banner\n\nIf you've enabled Service Worker support, your app becomes eligible to trigger a Chrome [web app install banner](https://developers.google.com/web/fundamentals/engage-and-retain/app-install-banners/) if you add a `start_url` property to `manifest.json`, and point it to a valid URL. The best practice here is to add a query parameter to that URL, in order to distinguish between the app being launched from the web vs. the homescreen. Simply add this to `manifest.json` and you'll be all set:\n\n \"start_url\": \"/?homescreen=1\"\n\nIf you are implementing an offline experince using Service Worker, make sure to cache `/?homescreen=1`. For a short explanation, you can refer to [this segment](https://youtu.be/g7f1Az5fxgU?t=1435) from Rob Dodson's talk Building Progressive Web Apps with Polymer. A more in-depth exploration can be found at [Service Workers in Production](https://developers.google.com/web/showcase/case-study/service-workers-iowa#watch-out-for-extra-query-parameters).\n\n## Yeoman support\n\n[generator-polymer](https://github.com/yeoman/generator-polymer/releases) now includes support for Polymer Starter Kit out of the box.\n\n## Frequently Asked Questions\n\n### Where do I customise my application theme?\n\nTheming can be achieved using [CSS Custom properties](https://www.polymer-project.org/1.0/docs/devguide/styling.html#xscope-styling-details) via [app/styles/app-theme.html](https://github.com/PolymerElements/polymer-starter-kit/blob/master/app/styles/app-theme.html).\nYou can also use `app/styles/main.css` for pure CSS stylesheets (e.g for global styles), however note that Custom properties will not work there under the shim.\n\nA [Polycast](https://www.youtube.com/watch?v=omASiF85JzI) is also available that walks through theming using Polymer 1.0.\n\n### Where do I configure routes in my application?\n\nThis can be done via [`app/elements/routing.html`](https://github.com/PolymerElements/polymer-starter-kit/blob/master/app/elements/routing.html). We use Page.js for routing and new routes\ncan be defined in this import. We then toggle which `` page to display based on the [selected](https://github.com/PolymerElements/polymer-starter-kit/blob/master/app/index.html#L105) route.\n\n### Why are we using Page.js rather than a declarative router like ``?\n\n`` (in our opinion) is good, but lacks imperative hooks for getting full control\nover the routing in your application. This is one place where a pure JS router shines. We may\nat some point switch back to a declarative router when our hook requirements are tackled. That\nsaid, it should be trivial to switch to `` or another declarative router in your\nown local setup.\n\n### Where can I find the application layouts from your Google I/O 2015 talk?\n\nApp layouts live in a separate repository called [app-layout-templates](https://github.com/PolymerElements/app-layout-templates).\nYou can select a template and copy over the relevant parts you would like to reuse to Polymer Starter Kit.\n\nYou will probably need to change paths to where your Iron and Paper dependencies can be found to get everything working.\nThis can be done by adding them to the [`elements.html`](https://github.com/PolymerElements/polymer-starter-kit/blob/master/app/elements/elements.html) import.\n\n### Something has failed during installation. How do I fix this?\n\nOur most commonly reported issue is around system permissions for installing Node.js dependencies.\nWe recommend following the [fixing npm permissions](https://github.com/sindresorhus/guides/blob/master/npm-global-without-sudo.md)\nguide to address any messages around administrator permissions being required. If you use `sudo`\nto work around these issues, this guide may also be useful for avoiding that.\n\nIf you run into an exception that mentions five optional dependencies failing (or an `EEXIST` error), you\nmay have run into an npm [bug](https://github.com/npm/npm/issues/6309). We recommend updating to npm 2.11.0+\nto work around this. You can do this by opening a Command Prompt/terminal and running `npm install npm@2.11.0 -g`. If you are on Windows,\nNode.js (and npm) may have been installed into `C:\\Program Files\\`. Updating npm by running `npm install npm@2.11.0 -g` will install npm\ninto `%AppData%\\npm`, but your system will still use the npm version. You can avoid this by deleting your older npm from `C:\\Program Files\\nodejs`\nas described [here](https://github.com/npm/npm/issues/6309#issuecomment-67549380).\n\nIf you get a browser console error indicating that an element you know you have installed is missing, try deleting the bower_components folder, then run `bower cache clean` followed by `bower install` to reinstall. This can be especially helpful when upgrading from a prior version of the Polymer Starter Kit.\n\nIf the issue is to do with a failure somewhere else, you might find that due to a network issue\na dependency failed to correctly install. We recommend running `npm cache clean` and deleting the `node_modules` directory followed by\n`npm install` to see if this corrects the problem. If not, please check the [issue tracker](https://github.com/PolymerElements/polymer-starter-kit/issues) in case\nthere is a workaround or fix already posted.\n\n### I'm having trouble getting Vulcanize to fully build my project on Windows. Help?\n\nSome Windows users have run into trouble with the `elements.html` file in their `dist` folder\nnot being correctly vulcanized. This can happen if your project is in a folder with a name containing a\nspace. You can work around this issue by ensuring your path doesn't contain one.\n\nThere is also an [in-flight](https://github.com/PolymerElements/polymer-starter-kit/issues/62#issuecomment-108974016) issue\nwhere some are finding they need to disable the `inlineCss` option in our configuration for Vulcanize\nto correctly build. We are still investigating this, however for the time-being use the workaround if\nyou find your builds getting stuck here.\n\n\n### How do I add new JavaScript files to Starter Kit so they're picked up by the build process?\n\nAt the bottom of `app/index.html`, you will find a build block that can be used to include additional\nscripts for your app. Build blocks are just normal script tags that are wrapped in a HTML\ncomment that indicates where to concatenate and minify their final contents to.\n\nBelow, we've added in `script2.js` and `script3.js` to this block. The line\n`` specifies that these scripts will be squashed into `scripts/app.js`\nduring a build.\n\n```html\n\n\n\n\n\n```\n\nIf you are not using the build-blocks, but still wish for additional files (e.g scripts or stylesheets) to be included in the final `dist` directory, you will need to either copy these files as part of the gulpfile.js build process (see the `copy` task for how to automate this) or manually copy the files.\n\n### I'm finding the installation/tooling here overwhelming. What should I do?\n\nDon't worry! We've got you covered. Polymer Starter Kit tries to offer everything you need to build and optimize your apps for production, which is why we include the tooling we do. We realise however that our tooling setup may not be for everyone.\n\nIf you find that you just want the simplest setup possible, we recommend using Polymer Starter Kit light, which is available from the [Releases](https://github.com/PolymerElements/polymer-starter-kit/releases) page. This takes next to no time to setup.\n\n## Licensing\n\nLike other Google projects, Polymer Starter Kit includes Google license headers at the top of several of our source files. Google's open-source licensing requires that this header be kept in place (sorry!), however we acknowledge that you may need to add your own licensing to files you modify. This can be done by appending your own extensions to these headers.\n\n## Contributing\n\nPolymer Starter Kit is a new project and is an ongoing effort by the Web Component community. We welcome your bug reports, PRs for improvements, docs and anything you think would improve the experience for other Polymer developers.\n","has_starred","hub_user","immutable_tags_settings",{"_72":11,"_73":74},"enabled","rules",[75],".*","is_automated","permissions",{"_79":17,"_80":11,"_81":11},"read","write","admin","user","storage_size",6098584084,"orgData","recentTags",[88],{"_89":40,"_90":91,"_92":93,"_94":95,"_96":97,"_46":115,"_116":91,"_117":29,"_118":52,"_53":119,"_120":121,"_122":106,"_123":115,"_124":62,"_125":17},"content_type","creator",572142,"full_size",274986946,"id",2398348,"images",[98],{"_99":100,"_101":102,"_103":104,"_105":106,"_107":108,"_109":104,"_110":104,"_111":-5,"_112":113,"_59":62,"_114":-5},"architecture","amd64","digest","sha256:0528cfc5cf16a4704d38a2451a6d2c426cfa484d83612bc45583db63c91bc2be","features","","last_pulled","2026-09-23T18:00:47.737712043Z","last_pushed","2016-04-10T21:39:53Z","os","os_features","os_version","size",274987074,"variant","2016-04-10T21:39:52.251552Z","last_updater","last_updater_username","media_type","latest","repository",594805,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":137,"_144":145,"_133":154,"_155":11},{"_36":138,"_38":139,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":140,"_53":31,"_28":29,"_54":55,"_56":-5,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":65,"_66":67,"_68":11,"_69":29,"_70":141,"_76":17,"_77":143,"_82":29,"_83":84},[],[40],[52],{"_72":11,"_73":142},[75],{"_79":17,"_80":11,"_81":11},"tags",{"_146":60,"_147":-5,"_148":-5,"_149":150},"count","next","previous","results",[151],{"_89":40,"_90":91,"_92":93,"_94":95,"_96":152,"_46":115,"_116":91,"_117":29,"_118":52,"_53":119,"_120":121,"_122":106,"_123":115,"_124":62,"_125":17},[153],{"_99":100,"_101":102,"_103":104,"_105":106,"_107":108,"_109":104,"_110":104,"_111":-5,"_112":113,"_59":62,"_114":-5},[],"canDeleteTags","actionData","errors"]

hankhendrix/meme-generator

Tags for hankhendrix/meme-generator