Closed (fixed)
Project:
Patterns
Version:
6.x-1.x-dev
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
23 Sep 2009 at 00:58 UTC
Updated:
12 Mar 2010 at 10:25 UTC
I haven't yet seen an actual example of a patterns server in action, so I'm not sure if the feature works, or how it should work.
Is this stable but undocumented, unfinished, or something else?
Where would I look if I wanted to try getting this working myself?
Comments
Comment #1
ChrisBryant commentedAt this moment it is a very basic, SUPER simple implementation. It currently just allows any Drupal site with the Patterns module enabled (and "Share your patterns" setting checked) to publish patterns. Once that setting is enabled there is a "Publish" link next to each pattern on the listing page. When that is clicked/enabled those patterns will show up in an XML file at the root of the domain. It is very simlar to RSS feeds:
http://example.com/patterns.xml
Here is a demo site with some sample public patterns:
http://patterns.graviteklabs.com/patterns.xml
Then on any client site you can go to admin/build/patterns/server and enter the URL of the server and it will show you the available patterns and let you download and run them on your site.
Again, this is an extremely basic implementation and not a full fledged or proper server/client system with tracking, versions, updates, etc. Nor is there currently any site that is setup to be a master patterns server keeping track of all the sites that have public patterns.
We'd love to expand it to be a full featured system as time permits. What are your thoughts and needs? Ideas? Etc.. :-)
Comment #2
dman commentedCool. I'm just trying to find a way to share my common settings among dev sites at the moment, but I can probably push up a demo server to a central spot sometime also ... if it's that easy.
However, I'm using php-based patterns (just to be awkward) so not sure that they will translate well just yet :-)
Mainly because the things I find awkward enough to automate (like today, fckeditor profile setups) require reading existing configs before modifying them.
I'll see what happens.
Good to know there is still hope.
Comment #3
vaish commented