mirror/sqlstyle.guide
1
0
Fork 0
mirror of https://github.com/treffynnon/sqlstyle.guide.git synced 2025-03-09 12:49:51 -05:00
Code Activity
A consistent code style guide for SQL to ensure legible and maintainable projects
60 commits 9 branches 0 tags 646 KiB
HTML 70.5%
CSS 23%
JavaScript 6.1%
Ruby 0.4%
Find a file
Simon Holywell ba9b116865 Merge pull request #7 from jroitgrund/patch-1 
Correct spelling of SQL commenting section
2016-10-11 12:29:16 +10:00
_includes Spelling 2016-10-10 10:28:04 +01:00
_layouts Correct HTML etc 2015-07-13 11:29:31 +01:00
.gitignore gitignore the gemfile lock 2015-07-03 14:23:37 +01:00
_config.yml Change to use the rouge syntax highlighter 2016-09-01 13:06:15 +10:00
CNAME Correct HTML etc 2015-07-13 11:29:31 +01:00
Gemfile Add dependency management 2015-07-03 14:22:17 +01:00
index.md Add in a TOC 2015-07-07 09:45:27 +01:00
LICENCE Add in some licence information 2015-07-11 23:36:58 +01:00
README.md Add notable forks to readme 2016-09-01 13:23:36 +10:00
scripts.js Add some more ancillilary info 2015-07-13 11:48:15 +01:00
style.css Eradicate mobile bug 2015-07-13 12:14:17 +01:00

README.md

SQL style guide

Read the guide

General

The guide is written in Markdown and uses Jekyll via GitHub's Pages facility to render itself upon pushing to the gh-pages branch.

Sources

The markdown source for the guide can be found in _includes/sqlstyle.guide.md

Installing for local development

There is a Gemfile supplied so you just need to follow the GitHub Pages documentation to install the dependencies.

To then run it locally bundle exec jekyll serve

Projects known to be implementing the guide

If your project uses this styleguide and you'd like to be mentioned in this readme then please open a pull request adding it below in alphabetical order with a URL and short description.

  • Stock Talk - a realtime dashboard that displays the stock data of the most Tweeted Nasdaq companies.

Notable forks of the guide

These are based on, but deviate in some way from sqlstyle.guide.

If you have forked this styleguide and you'd like to be mentioned in this readme then please open a pull request adding it below in alphabetical order with a URL and short description of your deviance.