some content
\")\n utils.addPortlet(context, 'plone.leftcolumn', portlet)\n\n utils.createImage(context, 'random-nature.jpg',\n file = utils.getRandomImage(category='nature', gray=False),\n title=u\"Random Image\",\n description=u\"Downloaded from lorempixel.com\")\n\n utils.createImage(context, 'random-sportscar.jpg',\n file = utils.getRandomFlickrImage(keywords=['car','sport'],\n match_all_keywords=True,\n gray=False),\n title=u\"Random Flickr Image\",\n description=u\"Downloaded from loremflickr.com\")\n\n myPlugin = MyPlugin()\n component.provideUtility(myPlugin,\n ISampleDataPlugin\n 'my.plugin')\n\nSee `wm.sampledata.example`__\nfor a complete example of a custom plugin.\n\n.. __: http://dev.plone.org/collective/browser/wm.sampledata/trunk/wm/sampledata/example\n\n\n\nYou can also group plugins (and even other plugin-gropus) so users need to run only one plugin to setup their sampledata correctly.\n\n.. code-block:: python\n\n from wm.sampledata import PluginGroup\n\n class TestPortal(PluginGroup):\n\n PLUGINS = [\n MyPlugin, # also 'my.plugin' could be used\n MainMenu,\n AnotherPluginGroup,\n ]\n\n title = u\"Complete Test Portal\"\n description = u\"Creates Main Menu items, Sampledata Folder and Portlets\"\n\nNote that you can use the utility names as well in `PLUGINS` but using classes directly is more straight forward in most cases.\n\n\nThere is a growing set of utility methods in ``wm.sampledata.utils`` (eg for\nhandling portlets and files, or download images from http://lorempixel.com)\nwhich you can use in your plugins.\n\n\nInstallation\n============\n\n\nSimply add ``wm.sampledata`` to your buildout's instance eggs - a zcml slug is not needed\nin plone versions that ship with z3c.autoinclude (Plone>=3.3)::\n\n [buildout]\n ...\n eggs =\n ...\n wm.sampledata\n\n\n\nWhy yet another package?\n========================\n\nThere are several other packages for generating test/sampledata but none of them\nfitted my usecase. (Which is providing a user interface for pluggable sampledata generators\nso developers/skinners can use standardized data when developing on a project)\n\nA while ago i `asked what other people do on plone.users`__\n\n.. __: http://plone.293351.n2.nabble.com/Best-way-to-create-sampledata-for-tests-and-development-tp338487p338487.html\n\n\nz3c.sampledata\n Would do the same and much more (dependencies, groups, configuration ui for each plugin)\n\n for me it was too complex to get it running on my zope2 instance and it\n seems to be tailored for zope3 anyway.\n\n Basically it would be great to make wm.sampledata use z3c.sampledata\n and provide plone specific plugins for it.\n\n .. http://comments.gmane.org/gmane.comp.web.zope.plone.devel/17379\n\n\n`zopyx.ipsumplone`_\n Seems to provide very similar utility methods.\n No pluggable Generators, No User-Interface\n\n .. _`zopyx.ipsumplone`: https://pypi.python.org/pypi/zopyx.ipsumplone/\n\n\n`ely.contentgenerator`_\n provides a xml syntax to create samplecontent,\n might be useful to use in custom plugins\n\n .. _`ely.contentgenerator`: http://ely.googlecode.com/svn/ely.contentgenerator\n\n\ncollective.contentgenerator\n looks like this is meant for creating (random) sampledata for stresstests\n\n\n`collective.lorem`_\n content action to fill content with lorem-ipsum text and provides `utility methods\n