{
    "info": {
        "author": "Musharraf Omer",
        "author_email": "ibnomer2011@hotmail.com",
        "bugtrack_url": null,
        "classifiers": [
            "Development Status :: 5 - Production/Stable",
            "Environment :: Web Environment",
            "Framework :: Django",
            "Intended Audience :: Developers",
            "License :: OSI Approved :: MIT License",
            "Operating System :: OS Independent",
            "Programming Language :: Python"
        ],
        "description": "Mezzanine Live Tile\n================\n\nA Plug and play app for mezzanine CMS to provide live tile and notifications for new website content for your Windows 8,Windows 8.1, Windows 10, or Windows Phone visitors.\n\n\nIntroduction\n-----\n\n\nIn Windows 8 and above Microsoft introduced the start screen with Metro UI. Every app is represented by a static tile, and the app can make that tile live by providing notifications which Windows will cycle between them instead of displaying a static tile.    \n\n\nInternet Explorer and Microsoft Edge took this further by enabling websites owners to insert a special meta  tags in the head of their pages in order to provide live tile functionality to their visitors.\n\n\nVisitors can click on ``Favorites`` and then ``Pinn To Start`` and a new tile will be added to their start screen.\n\n\nThis app makes it easier for sites built on top of mezzanine CMS to provide this functionality without any hassle, just plug the app, configure settings as descried billow, and you are ready to engage your visitors and push updated content to them right to their start screen.\n\n\nSetup\n-----\n\n\n1. Run ``$ pip install mezzanine-live-tile``\n2. In ``settings.py`` add ``mezzanine_live_tile`` to your ``INSTALLED_APPS`` above\n   mezzanine apps.\n3. Include ``mezzanine_live_tile`` urls in your projects ``urls.py`` as follows::\n    from mezzanine_live_tile import urls as tile_urls\n\t...\n    url(r\"^tile/\", include(tile_urls, namespace=\"tile\")),\n4. Run migrate::\n    $ python manage.py migrate mezzanine_live_tile\n5. Tweak settings as described below\n\n\nSettings\n---------\n\n\nTemplate\n===============\n\n\nIn your ``base.html`` insert the meta tags required to pin your site by loading ``tile_tags`` and inserting the following template tag in the ``head``:\n    {% tile_meta %}\n\n\nBy default the app uses ``settings.SITE_TITLE`` to get the name that Windows will display for the tile in the start screen (analogous to app name). Alternatively you can pass a name to the ``tile_meta`` template tag to be used instead:\n    {% tile_meta \"My Awesome Site\" %}\n\n\nTile Images:\n===============\n\n\nYou must provide 4 different size images to be used as tile images for different tile sizes. For your convenience here are the recommended sizes taken from `this MSDN page`_::\n- small (128x128) \n- medium (270x270)\n- wide (558x270)\n- large (558x558)\n\n\nTo override the provided ``food truck`` place-holder images, you should upload your own images to ``<static_dir>/tile/images/``.\n\n\nFor each image the name is the same as image size (\"small\" for small, \"medium\" for medium..etc.), we expect a \".png\" image format in our template.\n\n\nNotifications\n==================\n\n\nThe app provide live tile notifications for new contents and updates, when a visitor pin your site windows notification system will pull updates from your server regularly and cycle between them in his start screen.\n\n\nIn order to support live tile notifications, you need to configure a class from which the app pulls new notifications which windows will cycle between in the live tile. \n\n\nBy default, If ``mezzanine.blog`` is installed, then the app will use ``BlogPost`` model as the notification class, this simply means that the live tile will cycle between the recent five blog posts, this is fine for most situations.\n\n\nIf ``mezzanine.blog`` is not installed then the app has its own fallback ``Notification`` class which will be listed in the admin, and in this case you must edit the notifications manually to ensure that your users get updated content.\n\n\nAlso you can configure your own  class to be used as a notification class by configuring ``WINDOWS_TILE_MODEL`` setting in your ``settings.py``. It is a tuple of two items, the first item is the dotted path to the model class and the second one is a dictionary mapping notifications field names to your class field names::\n\n    WINDOWS_TILE_MODEL = (\"my_app.models.MyCustomNotificationClass\",\n     {\n      \"headline\": \"title\",\n      \"body_text\": \"description\",\n      \"image\": \"featured_image\",\n      \"pub_date\":\"publish_date\"\n     }\n    )\n\n\nEditable Settings\n==================\n\n\nA handful of options are provided to customize the look and behavior of your tile, you can edit those options in the ``admin > settings``. here is a quick run through::\n- ``TILE_COLOR``\n    A background/accent color to use in the tile, this must be in the format (009900)\n- ``LIVE_TILE_UPDATES_COUNT``\n    How many notification windows will cycle between in the live tile.\n- ``UPDATE_FREQUENCY``\n    How often windows will pull updates from your website (default to one hour).\n- ``TILE_BRANDING``\n    What will windows display in the corner of the live tile (default to web site's favicon)\n- ``CYCLE_OPTION``\n    Restrict cycling in certain tile sizes.\n\n\nOverriding Notification Templates\n==================\n\n\nBy default the app uses a (header - body) text-only template for all tile sizes, but  you can override the default template to use your own notification template instead.\n\n\nFirst read this `MSDN article about template catalog`_.\n\n\nAfter you are comfortable  with the template design, copy the template from \"<mezzanine_live_tile>/templates/tile/tileconf/notification.xml\" to your project's ``templates`` path or your own app templates path, in the latter case your app must appear in the `INSTALLED_APPS` list before `mezzanine_live_tile`.\n\n\nThen you can edit your newly copied template. To make your life easier you may make use of ``wrap_text`` and ``text_node_for`` template tags, see the original template for sample usage.\n\n\nNote also that you must test your templates before shipping them to your visitors, because you do not have any way to debug those templates it can be a little tricky to design custom templates, so make sure they are working for all tile sizes before shipping them.\n\nLicense\n-------\n\nCopyright (c) 2015 `Musharraf Omer`_\n\n\nMezzanine Live Tile  is licensed under the MIT license (See ``LICENSE`` for more details).\n\n\n\n\n.. Links\n\n.. _this MSDN page: https://msdn.microsoft.com/library/dn455106.aspx#CreatingLiveTiles\n.. _MSDN article about template catalog: https://msdn.microsoft.com/en-us/library/hh761491.aspx\n.. _Musharraf Omer: https://www.twitter.com/mush42",
        "description_content_type": null,
        "docs_url": null,
        "download_url": "https://github.com/mush42/mezzanine-live-tile/downloads/",
        "downloads": {
            "last_day": -1,
            "last_month": -1,
            "last_week": -1
        },
        "home_page": "https://github.com/mush42/mezzanine-live-tile",
        "keywords": null,
        "license": "MIT License",
        "maintainer": null,
        "maintainer_email": null,
        "name": "mezzanine-live-tile",
        "package_url": "https://pypi.org/project/mezzanine-live-tile/",
        "platform": "UNKNOWN",
        "project_url": "https://pypi.org/project/mezzanine-live-tile/",
        "project_urls": {
            "Download": "https://github.com/mush42/mezzanine-live-tile/downloads/",
            "Homepage": "https://github.com/mush42/mezzanine-live-tile"
        },
        "release_url": "https://pypi.org/project/mezzanine-live-tile/1.1/",
        "requires_dist": null,
        "requires_python": null,
        "summary": "A Plug and play app for mezzanine CMS to provide live tile and notifications for new website content for your Windows 8,Windows 8.1, Windows 10, or Windows Phone visitors.",
        "version": "1.1"
    },
    "last_serial": 1711517,
    "releases": {
        "1.0.1": [],
        "1.1": []
    },
    "urls": []
}