Note: As of the end of December 2018, our site has changed hosts and some architecture. As a result, all tutorials are now have a /tutorials in their paths. You will need to update bookmarks.
Our Future . . .
When I initially created this site in 2014, it was to serve two primary purposes.
To document the tips, tricks, and other higher level development practices that make programming for FRC in LabVIEW easier.
Provide a common place for LabVIEW teams to find resources.
At first, this meant documenting the architectural and similar tools that I had learned on my way to becoming a Certified LabVIEW Developer, that had been put to use by the team I was currently mentoring (#3937, Breakaway). (This had the added bonus of helping the senior programmer that had been soaking all this up document it for his successor.)
Since then, this site has had a few additions and updates (mostly by me).
While I have often invited other teams (I am no longer in the AR area and have pretty much lost contact with Breakaway) on CD and at the regionals I've been at to write tutorials for specific topics that they had solved, I was rarely met with a response (specifically once - shout out to the Huskie Robotics 3061 for actually following through, but they were the only ones).
In recent years, I have found myself going through some family changes and needing to dial back my commitment to other activities.
This leaves this site both:
Looking for a new champion/curator, that is willing to:
maintain the back end,
make sure material that becomes obsolete is either updated, or moved to the archives section of the menu,
and either write content or get other teams to write content to help this site remain relevant.
Looking for a new source of funding/hosting. (I have been personall providing the $36/yr that it costs to maintain it using Google Domains for the domain name - and email - and Hosting24 for the hosting; I have thought about using some sort of a Donate button, but have not been able to find a platform that allows for *only* raising the target amount). (With moving to Github's gh-pages for hosting, the cost has been reduced to $12/yr, mitigating this need).
If you have any interest in seeing the continuation of this site, please let me know.
FRC LabVIEW Tutorials - Writing/Contributing
First, let me (mshafer1 - site Curator) say “Thank you.” for being willing to share your knowledge with the rest of the FRC community.
I am posting this article for new writers to have an easy reference on how to format their pages and submit them.
Visual Studio Code to create a basic markdown file (Visual Studio Code even has a preview option) or
Another option is to use an online markdown editor like this free one and download the resulting source (If using this method, please adjust the image and file links before submitting - see section below.)
Please put a written by [Team Number] with a logo or something on the bottom.
Header 1 and 2 are used in the setup for the page, so use Header 3 and smaller for section labels within the document.
Don’t worry about the exact path to the css file or the menu or other header items - when I move build it with jekyll, the template will take care of those things.
To keep architecture consistent, please put any and all images in a folder named images next to your markdown file (i.e. paths should look like src=”images/example.jpeg”), and downloadable files should be linked with href=”files/example.vi” (which means that any attached vi’s and the like should be put in a folder named files next to the markdown file). You will need to make sure to include these files when submitting.
Submitting for Review,
Option1 - email
You can email me your draft at firstname.lastname@example.org. Once I have what I need to format your page, I will post it for peer review to the admin group.
Option2 - Github Pull request
Now that the site is hosted on Github, you can fork the repo (Github Repo link), make your changes, and post a pull request to have your changes merged into the master branch (this will start the peer-review process).
May we use Google Analytics to collect anonymized data on your use of the site?May we use Google Analytics to collect anonymized data on your use of this site such as browser type and size, what site referred you, and country of use?
We use this to help us understand how we are doing on getting the word out, and what browsers we should be testing against to make sure the site works for all our readers.