-
-
Notifications
You must be signed in to change notification settings - Fork 860
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation Improvements #992
Conversation
Improve getting-started.md Fix incorrect GitHub links Fix incorrect copyright
Removed docusaurus.config.min.js (no need to minify)
Start of how-does-it-work.md
Added /miscellaneous placeholders for links
Added pub.dev links Added API Reference links Edited landing page to remove placeholder text and add custom text Edited go.md, how-does-it-work.md for general improvements Finished the-basics.md Started options.md
Finish options.md
Finished map-layers.md Finished tile-layer.md Added migration guides
…md & polygon-layer.md Renamed examples.md to master-example.md Started master-example.md Removed repetitive code line from examples throughout Added circle-layer.md
…up-to-date information Added to options.md Added information about performance to marker-layer.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like it overall. One thing I was wondering, is I guess as PR on flutter_map come in, options will be out of date on the docs here ? Could there be a link to either the flutter_dev api or the git code...
Eg if a doc is on tile_layer, is there any way to see this level of detail via a link...
https://pub.dev/documentation/flutter_map/latest/flutter_map.plugin_api/TileLayerOptions-class.html (which may be slightly out of date as well!), just trying to think of ease of access without needing to do too many updates when parameters change etc...
I can add links to each page, but not much more than that. In Contributing I have said that they should edit the documentation should they need to. |
* Fix example application (#1213) * Update versions in the example * Remove obsolete splash screen * Added location permission for a live location example * Fix for opacity widget causing hairlines and possible shimmering (#1169) * Fix EPSG4326 parameter difference with Leaflet.js (#1135) * EPSG4326 parameter modification * Add EPSG4326 example page Merge conflicts resolved by: Luka S <[email protected]> Co-authored-by: Ilya Zverev <[email protected]> Co-authored-by: Ian <[email protected]> Co-authored-by: yeleibo <[email protected]>
Remove duplicate imports in example app Fix missing menu item in drawer in example app
…s/flutter_map into fix-merge-conflicts
Add notices of unfinished documentation to appropriate pages Make writing more concise on many pages Improve landing page Add feedback link to PR Add some content to plugin creation guide
…s/flutter_map into fix-merge-conflicts
Added more prominent links to Discord server Added `tileBounds` Replace `bounds` with `maxBounds`
… fix-merge-conflicts
Update polyline documentation Change navbar external links to more modern icons
Added documentation for polyline calculations Improved documentation about polyline performance issues Improved documentation about polyline format conversion Improved plugins list page Improved consistency betwen \`flutter_map\` and 'flutter_map'
As discussed in thread #927 (comment), this PR will merge a whole new documentation for
flutter_map
, including: