kciter / awesome-style-guide

A list of awesome style guide.

💼 Currently working on

Cobalt. Inc.

CTO, 2018. 07 ~

📘 Writing / Translation

• 리액트 훅을 활용한 마이크로 상태 관리
• Vue.js 이 정도는 알아야지

📺 Presentation

• My presentations

❤️ Open Source

Look below!

awesome-style-guide's Issues

Validate Links

Hi @kciter, I wrote a tool that can validate README links (valid URLs, not duplicate). It can be run when someone submits a pull request or a commit is pushed.

It is currently being used by

• https://github.com/vsouza/awesome-ios
• https://github.com/matteocrippa/awesome-swift
• https://github.com/dkhamsing/open-source-ios-apps
• and many more

Examples

• https://travis-ci.org/matteocrippa/awesome-swift/builds/96526196 ok ✅
• https://travis-ci.org/matteocrippa/awesome-swift/builds/96722421 link redirected / rename 🔴
• https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/96763135 bad link / project deleted 🔴
• https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/95754715 dupe 🔴

You would have found these changes if you used it:

3 redirects

https://make.wordpress.org/core/handbook/coding-standards/javascript/ redirects to
https://make.wordpress.org/core/handbook/best-practices/coding-standards/javascript/

http://framework.zend.com/manual/1.12/en/coding-standard.coding-style.html redirects to
https://framework.zend.com/manual/1.12/en/coding-standard.coding-style.html

http://creativecommons.org/publicdomain/mark/1.0/ redirects to
https://creativecommons.org/publicdomain/mark/1.0/

If you are interested, connect awesome-style-guide to https://travis-ci.org/ and add a .travis.yml file to the project. You can also use https://circleci.com/ which does not not require a config file in your repo.

See https://github.com/dkhamsing/awesome_bot for options, more information
Let me know if you have any questions 😄

Is AWS Cloud Design Pattern suitable for 'style guide'?

I read that CDP(Cloud Design Pattern) and thought 'is it really suitable to say 'style-guide''?.

The style guide is one of the rule to coding, to make better productivity, I think.
But the 'Design Pattern' is a kind of reusable solutions which commonly occur.

So why don't we remove AWS Cloud Design Pattern and other Design Pattern things in this repository?

Maybe something from this list?

I'm the author of this one.. https://github.com/lipis/awesome-style-guides maybe you can scrap things from this list and I can delete mine..