Skip to content

Make coding and documentation guides.  #36

@williamVbrines

Description

@williamVbrines

There have been issues that have popped up in the past like naming conventions, code portability, archiving, file management, and some documentation problems that need to be addressed, then changed. The files for these guidelines should be in the main directory of the repo as a text file.

These guidelines should include examples, does and don'ts of what to do.

  • Guidelines for Git.
  • Guidelines for the code.

Metadata

Metadata

Labels

enhancementNew feature or request

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions