Skip to content

Commit 3e04324

Browse files
Initial commit
0 parents commit 3e04324

File tree

1 file changed

+79
-0
lines changed

1 file changed

+79
-0
lines changed

README.md

Lines changed: 79 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
_The example below is meant to be a reference more than a prescriptive template.
2+
The end goal is that README files always present the information here presented in some capacity._
3+
4+
---
5+
<a href="https://jenkins.albelli.com/view/{area}/job/{project-name}"><img src="https://img.shields.io/badge/-Jenkins-success?logo=jenkins&logoColor=D24939" />
6+
</a> <a href="https://octopus.deploy.photoconnector.net/app#/Spaces-1/projects/{project-name}"><img src="https://img.shields.io/badge/-Octopus-2F93E0?logo=octopus-deploy&logoColor=white" /></a>
7+
8+
# <Name of the system/component/application/API>
9+
10+
## Resources
11+
12+
Include references to all resources related to and relevant for this system.
13+
14+
* Endpoints/URLs of all environments where an instance of this system exists
15+
* Swagger URLs of all environments
16+
* Deployment control panel URLs
17+
* AWS accounts
18+
* Logs URLs
19+
20+
See for example:
21+
* https://github.com/albumprinter/ECOM-OrderCloudAPI
22+
23+
# Purpose and context
24+
25+
The information should summarise:
26+
* Why does this system exists
27+
* What is its domain
28+
* Links to systems, external and internal, this system is connected to or interacts with
29+
30+
## Architecture
31+
32+
Include here diagrams describing the system in its components and flows.
33+
34+
If relevant, a diagram describing how this system is connected to other systems should also be added here.
35+
36+
For example:
37+
38+
![Order Promise Flow](https://github.com/albumprinter/PL-Blobs/blob/master/OrderPromise/Order%20Promise%20Flow.png)
39+
40+
More examples in context:
41+
* https://github.com/albumprinter/OrderCutoff-Api
42+
* https://github.com/albumprinter/storefront-product-info-provider
43+
* https://github.com/albumprinter/storefront-feed-management-tool
44+
45+
## Functionality
46+
47+
High level description of what the system does and how it works.
48+
49+
### Schemas/Contracts/Business rules
50+
51+
Typical elements to include here:
52+
53+
* What are the existing contracts, what to they look like (include examples or references to examples)
54+
* With whom such contracts have been agreed upon
55+
* Why is the data structured in a certain way
56+
57+
## Development information
58+
59+
Here information on how to set up and run a development enviroment.
60+
61+
The information should include:
62+
* How to get and use keys necessary to configure and run locally
63+
* How to run unit/integration tests
64+
65+
### Commands and operations
66+
67+
Here the information on how to execute commands, trigger flows, make the system _work_ should also be included.
68+
69+
See for example:
70+
* https://github.com/albumprinter/storefront-platform
71+
72+
## User manual (when relevant)
73+
74+
Here information on how to use the system from a stakeholder point of view.
75+
76+
For example:
77+
* Jarvis commands
78+
* Etc.
79+

0 commit comments

Comments
 (0)