atmoos / atmoos/GlassView

Create Coding and Design Guidelines

Open
#14 0 comments 0 reactions 0 assignees View on GitHub
documentation
Dominant language
C#
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Let's create a design guideline document.

High Level:
- [ ] Design principles
- [x] Testing strategy
- [ ] Benchmarking strategy
- [ ] PR strategy
- [ ] Squash or Merge commit

Lower Level
- [ ] Coding guidelines
- [ ] Concepts
- [ ] Style guide captured as `.editorconfig`
- [ ] Development environment

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are named in the issue. Review the unchecked design principles, benchmarking strategy, PR strategy, commit policy, coding concepts, .editorconfig style guide, and development environment topics. Done means the guideline document covers the requested high- and lower-level sections.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
developer-experience, documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.