Terminology: Lowercase "architecture as code" used in prose (Appendix D, Ch 13, Ch 16)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- python
- Domain
- documentation
Research direction
Start by searching the listed occurrences in docs/appendix_templates_and_tools.md, docs/16_migration.md, docs/13_testing_strategies.md, 06_structurizr.md, 31_appendix_b_technical_architecture.md, and 19_management_as_code.md. Update the specified prose, docstrings, checklist items, alt text, and non-project-name hyphenated references while preserving URL slugs, file names, and branch names; verify no unintended lowercase or hyphenated references remain.
Written by the indexing model from the issue text.
Description
Category: terminology
Severity: high
Problem
The Style Guide mandates always writing Architecture as Code with capital A/C. Docstrings, comments, checklist items, and image alt text repeatedly use lowercase "architecture as code". Examples:
"""Automated assessment of existing infrastructure for architecture as code migration"""(appendix_templates_and_tools.md:35)# architecture as code Migration Playbook for {assessment_results.get('organization_name', 'Organization')}(line 219)- [ ] architecture as code foundation training for all team members(line 230)- [ ] Continuous improvement architecture as code implementation(line 281)
Affected files
docs/appendix_templates_and_tools.mdlines 35, 45, 76, 95, 196, 219, 230, 251, 281, 284docs/16_migration.mdlines 207, 215docs/13_testing_strategies.mdline 3 (image alt text)
Suggested fix
Replace all lowercase prose/docstring occurrences of "architecture as code" with Architecture as Code. Leave URL slugs, file names, and branch names (#architecture-as-code-general, 0002-use-terraform-for-architecture-as-code.md, workflows/architecture-as-code-pipeline.yml) unchanged. Also normalise "Architecture-as-Code" (hyphenated) in 06_structurizr.md:1278, 31_appendix_b_technical_architecture.md:67, 323, 19_management_as_code.md:59 where the reference is not to the FINOS project name.
Auto-generated by editorial review agent.
- Dominant language
- Python
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Geonitab/architecture_as_code
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Geonitab/architecture_as_code#1930 ·
-
design documentation
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Geonitab/architecture_as_code#1885 ·
-
design documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Geonitab/architecture_as_code#1874 ·
-
design documentation
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Geonitab/architecture_as_code#1869 ·
-
documentation language
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Geonitab/architecture_as_code#1867 ·
All issues in Geonitab/architecture_as_code
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100