[skip changelog] Migrate relevant documentation pages from arduino/Arduino wiki

[per1234]

These are all the pages from the arduino/Arduino wiki that are relevant to arduino-cli:

• https://github.com/arduino/Arduino/wiki/Build-Process
• https://github.com/arduino/Arduino/wiki/Arduino-IDE-1.5:-Library-specification
• https://github.com/arduino/Arduino/wiki/Arduino-IDE-1.5-3rd-party-Hardware-specification
• https://github.com/arduino/Arduino/wiki/Arduino-IDE-1.6.x-package_index.json-format-specification

The changes I made to that content during the migration:

• Make markup compatible with the documentation build system
• Update links to reflect the new locations of the pages
• Change page titles:
  • "Build Process" -> "Sketch build process"
    • "Build process" is ambiguous, since it could be interpreted as being about building arduino-cli.
  • "Arduino IDE 1.5: Library specification" -> "Library specification" (referred to in the text as "Arduino library specification")
    • Don't specify Arduino IDE, since this documentation is not specific to the IDE.
    • I think it's a bad idea to pin the page title to a specific version. This page should be the Arduino library specification, no matter which version of the specification we happen to be at.
  • "Arduino IDE 1.5 3rd party Hardware specification" -> "Platform specification" (referred to in the text as "Arduino platform specification")
    • Same reasoning about the IDE and version number as above.
    • There is nothing specific to 3rd party platforms about this documentation. It applies to all platforms.
    • Use the recommended term "platform".
  • "Arduino IDE 1.6.x package_index.json format specification" -> "package_index.json specification"
    • Same reasoning about the IDE and version number as above.

---

After some deliberation, I put the pages at the top level of the documentation structure:

---

---

I'm open to putting them in a subcategory ("More"?) if you prefer.

Built docs: https://per1234.github.io/arduino-cli/

[rsora]

Suggested change

	This new library format is intended to be used in tandem with the Arduino IDE"s **Library Manager**, available since version 1.6.2. The Library Manager allows users to automatically download and install libraries needed in their projects, with an easy to use graphic interface. It doesn't yet take care of dependencies between libraries.
	This new library format is intended to be used in tandem with the Arduino IDE's **Library Manager**, available since version 1.6.2. The Library Manager allows users to automatically download and install libraries needed in their projects, with an easy to use graphic interface. It doesn't yet take care of dependencies between libraries.

[per1234]

I also noticed this, as well as some other issues, but I thought it would be best for this PR to be as much a straight across migration of the content as possible, since I know all the commits will be squashed. This typo exists in the original content, it's not something I introduced during the migration.

I had planned to submit a follow up PR to fix the issues I noticed while I was doing the migration.

That said, if you want me to fix this in this PR, I'm happy to do so. I'm glad I'm not the only one who notices and cares about these sorts of details.

[rsora]

We can merge and fix it right after, I have no objections, so let's wait for @cmaglie review on the topic level then.

[rsora]

Suggested change

	In order to support old libraries (from Arduino 1.0.x), Arduino 1.5.x+ will also compile libraries missing a library.properties metadata file. As a result, these libraries should behave as they did in Arduino 1.0.x, although they will be available for all boards, including non-AVR ones (which wouldn’t have been present in 1.0.x).
	In order to support old libraries (from Arduino IDE 1.0.x), Arduino IDE 1.5.x+ will also compile libraries missing a library.properties metadata file. As a result, these libraries should behave as they did in Arduino IDE 1.0.x, although they will be available for all boards, including non-AVR ones (which wouldn’t have been present in 1.0.x).

[matthijskooijman]

Maybe it would be good to put up a notice on these wikipages that they are being migrated, to prevent people from editing them on the wiki and getting divergent versions?

[rsora]

Maybe it would be good to put up a notice on these wikipages that they are being migrated, to prevent people from editing them on the wiki and getting divergent versions?

@matthijskooijman yes, our plan is to update also the wiki referencing this new docs pages, once we merge the PR 👍

[matthijskooijman]

yes, our plan is to update also the wiki referencing this new docs pages, once we merge the PR +1

My suggestion was to update it now, to prevent people from editing the page from now until the PR is merged.

[rsora]

@per1234 can you help with this? @matthijskooijman is right, we should avoid wiki unattended updates

[per1234]

I have done as requested.

[cmaglie]

After rereading all the docs, I think we should refine some pieces that are a bit ambiguous (in particular the when we try to describe in detail the internals of the builder, that part requires some love :-) ).
But overall I like it.