96boards
diff --git a/‎README.md
+9-18 b/‎README.md
+9-18
diff --git a/‎TODO.md
+2-1 b/‎TODO.md
+2-1
diff --git a/‎changelog.md
+4 b/‎changelog.md
+4
diff --git a/‎common/.DS_Store
6 KB b/‎common/.DS_Store
6 KB
diff --git a/‎common/layout.html
+1-1 b/‎common/layout.html
+1-1
diff --git a/‎convert.py
+1-1 b/‎convert.py
+1-1
diff --git a/‎data.json
+1-1 b/‎data.json
+1-1
diff --git a/‎draft/.DS_Store
6 KB b/‎draft/.DS_Store
6 KB
diff --git a/‎draft/README.md
+1-1 b/‎draft/README.md
+1-1
diff --git a/‎draft/boards/.DS_Store
6 KB b/‎draft/boards/.DS_Store
6 KB
diff --git a/‎draft/overlay/.DS_Store
6 KB b/‎draft/overlay/.DS_Store
6 KB
diff --git a/‎draft/overlay/template.md
+7-25 b/‎draft/overlay/template.md
+7-25
@@ -29,16 +29,15 @@ Note that as part of the submission, a top-down view of the board in the form of
 Once your draft has been made, before filing a pull request, you should try to render the page and make sure it build and appears as intended. To do so:
 
 ```bash
-./draft/publish myboard
-make serve LANG=en
+draft/publish.sh myboard
+make LANG=en serve
 ```
-
 And then open: http://127.0.0.1:5000 in your browser.
 
 Once you are happy with the result, 
 
 ```bash
-./draft/unpublish myboard
+/draft/unpublish myboard
 ```
 (this will file the overlay back into the draft folder, ready for review)
 
@@ -47,7 +46,7 @@ Once you are happy with the result,
 
 *note 2: if you are facing issues with your preview (board not showing, text update not appearing, etc.), you can fix it by erasing your browser's cache (image and cache file only).*
 
-If you feel that the requirements for submissions is beyond your current possibilities, you may raise an [issue]() requesting the addition of a specific board instead and we'll consider it!
+If you feel that the requirements for submissions is beyond your current possibilities, you may raise an issue requesting the addition of a specific board instead and we'll consider it!
 
 # Translating
 
@@ -67,28 +66,20 @@ make serve LANG=de
 
 And then open: http://127.0.0.1:5000 in your browser.
 
-The last step will be to submit your finished translation as a [pull request]() (this can include any number of boards, it does not have to be the entire line-up) and we'll get it live on its own *&lt;languagecode&gt;*.pinout.xyz subdomain.
+The last step will be to submit your finished translation as a pull request (this can include any number of boards, it does not have to be the entire line-up) and we'll get it live on its own *&lt;languagecode&gt;*.pinout.xyz subdomain.
 
 If you wish to provide a translation for an existing subdomain, or correct a typo in an existing markdown file, just edit the file in place (leaving the files in the `translate` folder for review, if you are pushing a translation).
 
-If you have a question about translations, raise an [issue]() and we'll be happy to help you get past whatever hurdle you may face!
+If you have a question about translations, raise an issue and we'll be happy to help you get past whatever hurdle you may face!
 
 
 # Roadmap &amp; wishlist
 
-* Add as many [boards]() as possible!
+* Add as many boards as possible!
 
 # Acknowledgement
 
-Maintainers: [@Gadgetoid](https://github.com/Gadgetoid) and [@RogueM](https://github.com/RogueM)
-
-GPIO Zero code examples by: [@bennuttall](https://github.com/bennuttall)
+96Boards pinout: [radhikap18](https://github.com/radhikap18)
+Pinout.xyz Maintainers: [@Gadgetoid](https://github.com/Gadgetoid) and [@RogueM](https://github.com/RogueM)
 
-Notable contributions:
 
-* [en](http://pinout.xyz/) - [@lurch](https://github.com/lurch), [@abelectronicsuk](https://github.com/abelectronicsuk) and [@francesco-vannini](https://github.com/francesco-vannini)
-* [de](http://de.pinout.xyz/) - [@rdmueller](https://github.com/rdmueller) and [@KojoePi](https://github.com/KojoePi)
-* [es](http://es.pinout.xyz/) - [@ResonantWave](https://github.com/ResonantWave) and [@IkerGarcia](https://github.com/IkerGarcia)
-* [fr](http://fr.pinout.xyz/) - [@RogueM](https://github.com/RogueM) and [@smileyn64](https://github.com/smileyn64)
-* [it](http://it.pinout.xyz/) - [@LizardM4](https://github.com/LizardM4)
-* [tr](http://tr.pinout.xyz/) - [@Ardakilic](https://github.com/Ardakilic)
@@ -1,2 +1,3 @@
-# TODO
+#TODO
+
 
@@ -0,0 +1,4 @@
+#Overlays History
+
+This document only logs the changes to the overlay files that are relevant for purposes of translations. See files history for further details!
+
@@ -21,7 +21,7 @@
 	</head>
 	<body class="{{body_class}}">
 		<div id="container">
-			<h1 class="logo"><a title="96Boards GPIO Pinout home" href="/"><img src="{{resource_url}}pinout-logo.png" />Raspberry Pi Pinout</a></h1>
+			<h1 class="logo"><a title="96Boards GPIO Pinout home" href="/"><img src="{{resource_url}}pinout-logo.png" />96Boards Pinout</a></h1>
 
 			{{main_content}}
 
 
@@ -2,7 +2,7 @@
 import sys
 
 
-db = json.load(open('pi-pinout.db'))
+db = json.load(open('96-pinout.db'))
 
 
 def from_phys(phys, mode="bcm"):
 
@@ -15,4 +15,4 @@ I2C and SPI pins should be included if your board uses them, however they will g
 
 Power pins and EEPROM should specifically be excluded, but specifying the power and eeprom fields are highly recommended if that info is known.
 
-All of the above is further expended in the overlay template.md. We recommend you use this template as a starting point for any new add-on board submission and add or remove fields as required.
+All of the above is further expended in the overlay template.md. We recommend you use this template as a starting point for any new add-on board submission and add or remove fields as required.
@@ -5,39 +5,23 @@ class: board
 type: other
 formfactor: Custom
 manufacturer: Company
-description: An add-on board for the Raspberry Pi
+description: An add-on board for 96Boards
 url: https://my-addon-board.com
 github: https://github.com/my-addon-board-repo.com
 schematic: https://my-addon-board-schematic.com
 buy: http://buy-my-addon-board.com
 image: 'image.png'
 pincount: 40
-eeprom: no
 power:
+  '':
+  '':
+ground:
   '1':
   '2':
-ground:
-  '6':
-  '9':
-  '14':
-  '20':
-  '25':
-  '30':
-  '34':
   '39':
+  '40':
 pin:
-  '3':
-    mode: i2c
-  '5':
-    mode: i2c
-  '7':
-    name: Enable
-    mode: output
-    active: high
-i2c:
-  '0x00':
-    name: device display name
-    device: chip name
+
 -->
 #my add-on board
 
@@ -46,10 +30,8 @@ Use this section to provide additional information such as features, technical p
 The overlay itself uses the following fields, some of which are mandatory, as noted below:
 
 MANDATORY
-* name: the board name as it will appear at pinout.xyz
+* name: the board name as it will appear at 96boards/pinout
 * class: the class the overlay falls in, 'board' is the most common (use that if in doubt).
-* type: the typical applications of the board, i.e 'lcd' (use 'other' if in doubt). If multiple types apply, use a comma separated list (for example, 'adc,motor'). The keywords submitted will be used to filter boards on the site so don't include anything but tags that are relevant to the key functionality of the board.
-* formfactor: the board's form factor. Valid values are Custom, HAT and pHAT. Note that an EEPROM is required for HAT specs, use Custom if that is not the case.
 * manufacturer: the manufacturer's name.
 * description: a description of what the add-on board provides.
 * url: the main URL for the product providing detailed technical information about the board.
Original file line number	Diff line number	Diff line change
`@@ -15,4 +15,4 @@ I2C and SPI pins should be included if your board uses them, however they will g`
`15`	`15`
`16`	`16`	`Power pins and EEPROM should specifically be excluded, but specifying the power and eeprom fields are highly recommended if that info is known.`
`17`	`17`
`18`		`-All of the above is further expended in the overlay template.md. We recommend you use this template as a starting point for any new add-on board submission and add or remove fields as required.`
	`18`	`+All of the above is further expended in the overlay template.md. We recommend you use this template as a starting point for any new add-on board submission and add or remove fields as required.`