I love PL and the work that Dave and Brad have been doing. This is just random bullshit I've been thinking after a week of Pattern Lab use. Just
I've found that working on my current Pattern Lab, the only directory I really need is the source
directory. That makes me think that all the config|core|extras|etc
folders could not exist or be hidden from the user. That way a generic Node process that could be used by grunt, gulp, broccoli, etc might be beneficial. The "engine" is hidden from the user. Then updates could be seamlessly injected where now it'd be a bit of a manual process.
I think the simplicity of just having the files you're working on decoupled from the technology would be great for onboarding new users. Edit your source
files (now at the project root) and point a nodeapp/grunt/gulp task at it.
It feels like a question of do you want it to be WordPress for patterns (engine coupled) or a Jekyll for patterns (engine decoupled/hidden).
Relevant links:
I've wondered if it's easier to just update some JSON instead of keeping folder and file names numerically prefixed. If you delete a pattern, it's a bit of work to re-ordinate all the other files (lots of git changes, etc).
This would maybe help in up-cycling patterns into a larger system (which is a lot of people's dream). I can then tell a backend developer to include()
the molecules/global/pagination.mustache
instead of molecules/02-global/03-pagination.mustache/
, where the numbers seem subject to change. PL could then start existing within a directory of a larger system.
I talked with Brad about this, I know it's on the roadmap. I wonder if Jekyll's _plugins
structure might be good here, and those are little web components (HTML/CSS/JS ... Polymer?) that inject features in to the style guide header. Extensions could be included/excluded using YAML/JSON as well.
Hi all. I super-duper appreciate the thoughts above. I myself have struggled with how best to use PL - and have found success with a number of the use-cases Brad mentioned, as well as showcasing it as a more modern workflow over static PSD throw-over-the-wall-syndrome.
PL-node has always been feature-poor compared to the PHP version. I contemplated naming it patternlab-grunt, as some have indicated it could be considered an unnecessary dependency. Some decisions need to be made, however, while finding balance between approachability (see here) and cutting with the grain of current front end dev practices. The same thought was given to shipped preprocessor support if I recall.
That said, I really welcome the larger conversation, am excited to see what @dmolsen and @bradfrost consider the PL Spec, and really do welcome PRs! There is certainly a lot of ground to make up, and some basic maturity issues that need sorting out :)
Short term PL-node roadmap:
Thanks!