wildernesslabs / documentation Goto Github PK

There is an @2x image here, but only the standard resolution image is showing up:

The header should squish up until it has no room, and then change to a menu on resize for responsiveness. Instead, right now it's flowing on to a new line:

Need to add the footer from the main site, to this site.:

You can find the footer in the WLabs_Web GitHub Repo.

Right now it does this:

On the developer site, code blocks with language tags should get syntax highlighting.

For example, consider this article. When viewed on the github site, the CSharp blocks are syntax highlighted. But they're just static content on the developer site.

developer.wildernesslabs.co/Hardware/Tutorials/Electronics/Part5/Kirchhoffs_Voltage_Law/

arrows are pointing in the opposite directions

Right now, they're winding up under the bottom of the content:

Basically where one would see N3 describing the features of the entire range of N3 models. And then below it we would also see the N2 description one sees the N3 entered there, and then the features for the N2.

Ideally this should be corrected before it confuses someone else successfully.

See here, http://developer.wildernesslabs.co/Netduino/About/ And it shows up below the N3 entry of course, which is correct in its description.

• http://downloads.wildernesslabs.co/LegacyFirmware/Netduino2_Firmware_4.2.2.2.zip
• http://downloads.wildernesslabs.co/LegacyFirmware/NetduinoPlus2_Firmware_4.2.2.2.zip
• etc.

when the site gets reduced in width; the wood margins should resize first, going down to 10px minimum width. Here; the content is reduced too much, and the wood margins are too wide:

Need to document that the way to unbrick a board is to use the non-mfdeploy tools that use DFU and therefore don't need tinybooter.

from the forums:

Bryan, if you ever do that troubleshooting page, please, explain the USBcable issue. I get that some cables can power, but not transfer data, either because the data lines are broken or the darn cable was built to only power or charge in the first place. But is there a possibility that a faulty cable appears to work? It can succeed in making the Netduino recognisable for the computer, it can transfer parts of the data and then refuses to send something else?

Need a document that describes the various expansion options for Netduino, such as shift registers, LED drivers, analog chips, etc.

See:

maybe make a new document.

Should be using a lighter version of the google font. note the web site (top) vs. the design (bottom):

Debug.Print is useful for debugging, but it's a different API than standard .net, so we should call it out. maybe make a page on debugging.

something akin to:

If you're using the Netduino 3 WiFi model, the authentication and encryption options can be a little confusing, however, if you're connecting to a modern WiFi network that requires a password, you'll likely need to set the Authentication setting to Shared, and the Encryption setting to WPA. Additionally, SSID refers to the name of the WiFi network. 

need some help here.

Create a udev rule at /etc/udev/rules.d/50-netduino.rules with the content SUBSYSTEMS=="usb", ATTR{idProduct}=="1000", ATTR{idVendor}=="22b1", MODE="0660", GROUP="users", TAG+="uaccess" (this makes the Netduino accessible to standard users).

the gray bar should extend at least until the bottom of the nav bar

See top and left side of the left nav:

wrong fonts, padding is too much.

Intro section needs some simplifying. Get to the point faster.

Resolve: unknown type: System.Diagnostics.DebuggerBrowsableState

Error: ff000000

I put in the new file for the workaround and it still doesn't work. when I run the application, the emulator opens and gets stuck there. VS 2015 community

Instead of Thread.Abort() use a bool _isRunning; member variable and check in the loop:

        public void Start()
        {
            this._running = true;

            // create a new thread that actually writes the pwm to the output port
            _th = new Thread(() => { 
                while (this._running)
                {
                    OutputPort.Write(true);
                    Thread.Sleep(_onTimeMilliseconds);
                    OutputPort.Write(false);
                    Thread.Sleep(_offTimeMilliseconds);
                }
            });
            _th.Start();
        }

        public void Stop()
        {
            // setting this will wrap up the thread
            this._running = false;

            // need to make sure the port is off, otherwise it can get
            // stuck in an ON state.
            OutputPort.Write(false);
        }

1. The title, "Downloads", in this case, is an H2 which is being drawn as the same size as H1.
2. The "Windows" subheading is an H2 but has the "#windows" class applied to it which sets it to a different font, Conv_Lato-Regular instead of Conv_Lato-Light, which is bolder than the other subheadings.
3. The "Development Environment (Windows Only)" subheading under "Discontinued Products (Netduino 1, Plus, & Mini)" is larger than it's parent header because of the above-mentioned issues with the H2 CSS.

if you resize the site so that it's small enough that the menu button shows on desktop and then click it, it won't work.

"Download the latest Netduino firmware files from the downloads page. You’ll need the Tinybooter, ER_CONFIG, ER_FLASH files for your specific Netduino model."

What package are these files inside? I see the Netduino3Wifi_4_3_2_2 dir, but the files are the wrong extension for MFDeploy

when you resize the browser window down, the header doesn't resize well:

note that the space between the items is collapsed even before it should:

Additionally, the space between the logo and the log in link should resize down, equally.

they should stack to make room for the logo on left. right now, they squish:

See below:

It should probably stack. right now, it just squishes:

Implementation on left, design on right:

implementation on left, design on right:

Installation is currently embedded in the Getting Started guide, but it should probably be split out into its own section with a page for each of the platforms.

Additionally the Linux install guide would be new. Content would be the same as Mac, with the addition of the following steps:

• Install libusb from the distro package manager
• Create a udev rule at /etc/udev/rules.d/50-netduino.rules with the content SUBSYSTEMS=="usb", ATTR{idProduct}=="1000", ATTR{idVendor}=="22b1", MODE="0660", GROUP="users", TAG+="uaccess" (this makes the Netduino accessible to standard users).

The end of the getting started should push people towards:

• Explore samples
• Learning more about netduino - we need a kind of "why/what" page
• Netduino.Foundation (already done).

Resistor networks are cool. Great for multi-segment LEDs. Add a photo and a bit of info on them to the Electronics Tutorial, Resistor Section.

Add a quick reference chart that shows the resistor needed for a given forward voltage at 3.3V.

Should probably do a range of voltages and note which colors they generally apply to.

we need to point to the hackster projects at the end of our getting started doc
so it goes: Netduino Getting Started > Netduino.Foundation Getting Started > Hackster Projects

first two are done:

• http://developer.wildernesslabs.co/Netduino/Getting_Started/
• http://netduino.foundation/Getting_Started/

but that then sends folks to the peripheral library; we should send to hackster

and on the netduino getting started docs, we should have a list at top that enumerates those steps

Add information about changing the MAC address and also the number of times this can be done.

see this:

Note, design is on right, implementation on left:

See the web site vs. the sketch design:

in landscape mode on a tablet the background image doesn't repeat:

Implementation on left, design on right. Ignore the code colors.

currently, it flows all the way to the edge:

lead-free solder can be hard to get flowing. Solder paste makes a huge difference.

Add that to the Analog Level Shifting Lab, soldering section.

looks weird:

Should include:

• Bad USB cable
• holding down reset button for DFU programming mode
• No EntryPoint issue (where VS unchecks "deploy" for some unknown reason)

when the network class is published in the Netduino.Foundation core