-
-
Notifications
You must be signed in to change notification settings - Fork 26.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Categorize and Tag all patterns #213
Comments
Is there some limitation why we need to use snake casing e.g. |
What would be good tags to use? I'm thinking of implementation technologies e.g. |
Hmmm, to be honest im not too sure about beeing able to use proper casing with spaces. I'd say try it out and if it works then it definitly looks better than camel casing, right ? And Tags, yeah. Maybe some things that differences this pattern from other ones. Like if its an EJB only pattern, JEE or JSE, ... The technologies used or similar to the pattern also sounds quite good. But i agree, this needs more clarification... |
👍 Technologies can be tags for sure. Some other tags that I thought of are |
We need to tag based on difficulty as well. |
I did the categorization and tagging of the patterns today. The used categories and tags can be seen here. |
Due to splitting the issues up some information like the category got lost. And we have those cool new Tags.
All the index.md files of the patterns should get relevant categories and tags in the yaml frontmatter. The 'pattern_cat' and 'pattern_tag' stuff can be removed as it is only a placeholder...
The 'How to Contribute' Section of the README in master should explain everything that is needed for this issue.
EDIT:
After this point is done we should remove the pattern list from the master README file.
TODO:
ClarifyTest if we can use proper casing instead of camel case as shown in adbb4ac. EDIT: I looked it up, it should work without "", e.g. just -> Creational Patterns(done with 5ce932c)
(partially done the with usage of tag "Java" instead of placeholder :P 5ce932c)
(done with 5ce932c)
The text was updated successfully, but these errors were encountered: