All documentation for Navio project is at the moment stored as blog posts and this is clearly not the way to go. As our community grows a need in a convenient way to store and edit documentation arrises.
Our main criterias for picking a platform were:
- Easy to create and edit
- Anyone can contribute
- Version control
- Clear structure
- Great looks
We have chosen to write docs in markdown, store them in git and serve as a static web page. This way anyone can contribute by making a pull request on github and at the same time we have total control over the content.
Within next few days we will be transferring documentation from blog to http://docs.emlid.com.
We are looking for your feedback on this matter and welcome contributions.
Please visit docs.emlid.com
Great job guys.
This will definitely be more user-friendly.
I received my navio+ today, so please hurry and publish RTK for Odroid. Im itching to get this going.
If you looking for beta tester`s, mail me.
There have been many new releases including Odroid and Pi2. Both platforms require a large amount of work to be completed before they are usable. We are working on it as fast as we can.
I like this documentation, It’s even for people without a emlid product interesting, especially the rtklib sections.
We have made a switch to docs.emlid.com! All tutorials have been transferred there
Looks good I like it I was having trouble finding some things in the blogs.
Oh could you add something to say if the spi/i2c/uart headers are 5v or 3.3v?
I found here http://gpspp.sakura.ne.jp/paper2005/gpssymp_2014_ttaka.pdf on page 13 the settings for the Ublox M8N RAW data output, maybe you could add them also to the Documentation. At the point #set-up-rtk-mode I think you should also select Glonass and maybe SBAS for the Ublox M8N.
We have made some fine adjustments to the docs that should improve usability further:
- Added search
- Docs are now mobile friendly!
- Fixed image links handling and images now show up on GitHub correctly.
Welcome to the upgraded docs!
We were also really glad to see pull-request to the docs repository on GitHub. Contributions and improvements are always welcome.