Restructure filesystem to better align concerns and support upgrades

[bmuenzenmeyer]

Basically https://github.com/pattern-lab/patternlab-php/releases/tag/v0.7.0

• Move _patternlab-files out of source to make upgrading easier for users
• Restructure filesystem to allow for metapatterns
• Make a clearer distinction between source and pl code.
• 
  Edit New issue
  meta patterns missing?

UPDATE
I've mapped this work on the wiki

[Xiphe]

Do you have any plans on how you want to do this?

I've lately put some time into isolating grunt tooling from our projects.
We achieve that by having all tools in one single npm package that is then loaded and configured in a projects gruntfile.
I feel that this would be a great way, for this project to maintain upgradability and prevent monkey-patching.

Let me know how you think about this :)

[e2tha-e]

Excited for this to happen!

[bmuenzenmeyer]

Hi all

My current scope for this is to clarify the source code which I'd expect a user to alter from the code necessary to make the pattern-lab style guide frontend run. PL-PHP has restructured source/_patternlab-files/* out of source for a long time now - and this would be step one.

I do want to look at the link you provided more and generally create a more future-friendly file structure that is approachable to newcomers.

Stay tuned

[Xiphe]

Nice, feel free to contact me if you want to chat :)

Just as a feedback on this topic:
We already have a working design system with our own structure and a bunch of grunt tooling. We would have loved to use pattern-lab as a frontend and follow the suggested structures - Sadly the merge of this project into ours would have been very complicated and we would have lost/rebuild lots of our own tooling.
It would have been easier if this where a plain npm tool or grunt/gulp task that one can just use in any project. Not saying that it needs to be like this, i can totally see the benefits of having a project scaffold that just works, this is just the story of my team :)

[Xiphe]

While re-reading i just figured, that the moving of _patternlab-files would totally enable this. These files can then live in their own project that has build tools and everything one can imagine while the pattern-lab project is just the frontend.

[e2tha-e]

@bmuenzenmeyer @Xiphe Has there been any development on this? My current work requires this separation of concerns so I'll start on this myself if there's nothing already in development.