Remove Pattern Type, Subtype, and Pattern Order mechanic using ##- in the filename

[bmuenzenmeyer]

As documented in our feature review I am planning to remove the 00-atoms/ means of ordering in favor of markdown.

• Metadata should not be baked into file names - it mucks with git history
• It complicates the code immensely, leading to issues like [uikit-workshop] View All for sub types is broken #890

When this issue is finished, specify order within the optional markdown frontmatter to specify the order in which PL generates the UI.

source/_patterns/atoms.md

order: 1
---
# Atoms are small

_patterns/atoms/buttons.md

order: 1
---
# Buttons are the next big thing.

_patterns/atoms/buttons/calltoaction.md

order: 3
---
# Try a click today

Related: #415

[bradfrost]

Yep, this is a good move!

[sghoweri]

@bmuenzenmeyer is markdown going to be the only way this Pattern-specific data gets lifted or would other data formats we parse like JSON or Yaml (... or even Javascript) also going to be supported?

[bmuenzenmeyer]

pattern-specific data works with JSON as always. I feel as if someone had tried or did succeed in also supporting Yaml. We have code in core that can load both but I'd have to check.

the order metadata is pattern documentation: https://patternlab.io/docs/documenting-patterns/

[sghoweri]

@bmuenzenmeyer another quick question or two relating to this one:

1. Is the plan to temporarily disable this feature (to get things in a more stable / predictable spot) but potentially bringing things back in the future (perhaps with Blueprint for Pattern Lab’s Internal Plumbing? #1031?) or is the idea to retire this particular feature indefinitely?

2. Isn't this a major breaking change...? If so, is this a major breaking change for "v3.0" or do we need to bump our semver across the board to v4.x to play it safe?

CC @lwpinion

[sghoweri]

@bmuenzenmeyer just read the feature roadmap and yup, file system hacks do suck. 👍

[stale]

It's hard to keep track of everything. This issue has been automatically marked as stale because it has not had recent activity, neither from the team nor the community. It will be closed if no further activity occurs. Please consider adding additional info, volunteering to contribute a fix for this issue, or making a further case that this is important to you, the team, and the project as a whole. Thanks!