Skip to content
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

Docs Standards and Procedures (Page) #90

Open
smolinari opened this issue Dec 10, 2015 · 2 comments
Open

Docs Standards and Procedures (Page) #90

smolinari opened this issue Dec 10, 2015 · 2 comments
Assignees
Milestone

Comments

@smolinari
Copy link
Contributor

Hi,

This should be a draft (and seen as a suggestion) and discussion for doc standards and contribution procedures.

Standards


1. ALL SQL statements must be in capitalized letters.**

For instance....

insert into TestLineSTring set name = 'Test1' , location = St_GeomFromText("LINESTRING(0 0, 3 3)")

should be

INSERT INTO TestLineSTring SET name = 'Test1' , location = St_GeomFromText("LINESTRING(0 0, 3 3)")

2. ALL "For more information see:" sections must be in a quote block.

Use ">" to add the quote block. Multiple links should be in an unordered list.

Example:

For more information see:

  • Item 1
  • Item 2

2.1 Links to commands should be placed in "code" blocks with back ticks "`".

Example:

For more information, see

Notice the BEGIN and ROLLBACK commands.

Procedures


Authoring and Editing

In order to become an author or editor of the documentation, you'll need a Github account.

To make additions or changes do the following:

  • Yadda, yadda, yadda

Proofreading

If you proofread either for technical purposes or for grammatical reasons, you MUST add an html comment at the top of the file like so.

`'

Where, "XXX" is the initials to your name. This will indicate the file was corrected and when and should avoid double work. It can also help with general changes to doc standards, should there be any.


Please add any additional information in posts below. I'll add them and then make the document and add them to the docs.

Scott

@smolinari
Copy link
Contributor Author

Made some updates.

Scott

@smolinari
Copy link
Contributor Author

Another update.

Added a formatting rule of "For more information" section.

Scott

@santo-it santo-it added this to the 3.0 milestone Dec 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants