[EPIC] vNext

[bmuenzenmeyer]

This is the tracking issue for the vNext milestone, which serves as a living document for the 4..0 version of this repository.

All vNext Issues: https://github.com/pattern-lab/styleguidekit-assets-default/milestone/1

vNext is informed in part from the following locations:

• This repository backlog
  • review backlog for vNext enhancements
• Solve the problem of mapping Drupal fields to pattern Variables drupal-pattern-lab/roadmap#8
• The evolving Pattern Lab Spec Guidance - https://github.com/pattern-lab/the-spec

More to come...

[bmuenzenmeyer]

@sghoweri please feel free to add anything you like to this re: the front end architecture.

[sghoweri]

Lol impeccable timing.

I literally had just finished naming a new Evernote doc "Styleguidekit Assets Default Reimagined" to jot down my thoughts when I saw this first notification come through.

Sounds good @bmuenzenmeyer!

[sghoweri]

@bmuenzenmeyer Just a quick brain dump of a few things that come to mind:
https://www.evernote.com/shard/s13/sh/66ca246c-cd6f-4733-ae2a-2066641e97f0/14480f2181f847bdec4e5cdb8bdefbba

CC @jesconstantine

[bmuenzenmeyer]

@EvanLovely tagging you on this, though I wouldn't doubt if you already talked it over with Salem.

cc @geoffp

[sghoweri]

@bmuenzenmeyer ...you mean about how @EvanLovely's taking over as Pattern Lab's Lead PHP Developer and how we're all crazy excited to start planning out the next big step for all this?!! 😀

[bmuenzenmeyer]

that yes, which will be announced officially with other fanfare too 🎺

I tagged him mostly to ensure conversations happening inside #69 are part of the context of this issue and your evernote.

I understand we will need to make a stepwise approach to tackling all this collaboratively with minimal disruption to existing workflows - so overcommunicating seemed prudent

[bradfrost]

Just looked at your Evernote brain dump, @sghoweri. Awesome! I think we're on the same page, and I think I've addressed most HTML/CSS-related bullets in #72.

As for the others, it would be great to convert those into issues so we could further discuss.

Aside from that, @bmuenzenmeyer what's the status of this issue?

[bradfrost]

(I'm trying to organize and tag all the issues in this repo, so if it needs to stay open, what should its tag be?)

[bmuenzenmeyer]

@bradfrost the milestone here: https://github.com/pattern-lab/styleguidekit-assets-default/milestone/1 is intended to track all work towards our next level near-term vision, based off of conversations started in August. This issue was created because Github has 💩 support for markdown inside a milestone's description, so by convention I have gotten used to creating a summary issue within the milestone that can have longer-form documentation in it.

like I did for pattern-lab/patternlab-node#603

[bmuenzenmeyer]

labeling spec writeup needed as we need to get trailing docs on this once dust settles, most likely

[EvanLovely]

I'd really like to get support for links and tags as discussed here: pattern-lab/the-spec#34

I could see tags just being a list of <span>s right after state and having data-pl-tags="tag1 tag2" as an attribute on the wrapping pattern and menu item. This is mainly for future use or hooks on plugins.

links should be a list of <a href="{{ url }}" target="_blank">{{ text }}</a> in the Pattern Info.

Additionally, state should have data-pl-state="inprogress" as an attribute on the wrapping element as well... and it would be really cool if the PL menu had a dropdown listing each state, that when clicked would hide/show those Patterns with that state. This could get us a step closer on the Workshop / Storefront idea.

[bmuenzenmeyer]

I could see tags just being a list of s right after state and having data-pl-tags="tag1 tag2" as an attribute on the wrapping pattern and menu item. This is mainly for future use or hooks on plugins.

enhancing the current search to also bring back results by tag, or have dedicated tag pages would be an amazing addition to the navigation capabilities.

and it would be really cool if the PL menu had a dropdown listing each state, that when clicked would hide/show those Patterns with that state.

love it!

@bradfrost perhaps you can mock up what some of these ideas would look like?

[bradfrost]

@bradfrost perhaps you can mock up what some of these ideas would look like?

Can do! Going to make an issue that starts laying out my priorities, because as you all know there's a lot that can be done.