-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Put technical notes on the website. (#177)
Publish technical notes on the website.
- Loading branch information
Showing
15 changed files
with
113 additions
and
58 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,7 @@ | ||
--- | ||
title: Blog | ||
menu: {main: {weight: 30}} | ||
weight: 30 | ||
--- | ||
|
||
Blogs related to Foyle. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
--- | ||
description: Technical Notes About Foyle | ||
title: Tech Notes | ||
weight: 40 | ||
--- | ||
|
||
# Objective: | ||
**Describe** how we want to use technical notes and establish guidelines on authoring technical notes (TNs) for consistency. | ||
|
||
# Why TechNotes? | ||
We use TNs communicate key ideas, topics, practices, and decisions for the project. TNs provide a historical record with minimal burden on the authors or readers. We will use TNs in Foyle to document our team engineering practices and technical “stakes-in-the-ground” in a “bite-sized” manner. Use a TN instead of email to communicate important/durable decisions or practices. Follow this up with an email notification to the team when the document is published. | ||
|
||
TNs are not meant to replace documents such as User Guides or Detailed Design documents. However, many aspects of such larger docs can be discussed and formalized using a TN to feed into the authoring of these larger docs. | ||
|
||
## Guidelines | ||
|
||
1. All TNs have a unique ID that TNxxx where xxx is a sequential number | ||
1. Keep TNs brief, clear and to the point. | ||
1. Primary author is listed as owner. Secondary authors are recognized as co-creators. | ||
1. Allow contributors to add themselves in the contributors section. | ||
1. TNs are considered immutable once they are published. They should be deprecated or superceded by new TNs. This provides a historical timeline and prevents guesswork on whether a TN is still relevant. | ||
1. Only mark a TN published when ready (and approved, if there is an approver). | ||
1. If a TN is deprecated mark it so. If there is a newer version that supersedes it, put the new doc in the front matter. | ||
|
||
Happy Tech-Noting |
File renamed without changes
File renamed without changes
File renamed without changes
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
13 changes: 8 additions & 5 deletions
13
tech_notes/tn002_learning.md → ...tent/en/docs/tech-notes/tn002_learning.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
17 changes: 7 additions & 10 deletions
17
tech_notes/tn003_learning_eval.md → ...en/docs/tech-notes/tn003_learning_eval.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
13 changes: 8 additions & 5 deletions
13
tech_notes/tn004_runme.md → ...content/en/docs/tech-notes/tn004_runme.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
15 changes: 9 additions & 6 deletions
15
..._notes/tn005_continuous_log_processing.md → ...-notes/tn005_continuous_log_processing.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
13 changes: 8 additions & 5 deletions
13
tech_notes/tn006_continuous_learning.md → ...s/tech-notes/tn006_continuous_learning.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
13 changes: 8 additions & 5 deletions
13
tech_notes/tn007_shared_learning.md → .../docs/tech-notes/tn007_shared_learning.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
13 changes: 8 additions & 5 deletions
13
tech_notes/tn008_auto_insert_cells.md → ...ocs/tech-notes/tn008_auto_insert_cells.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters