-
Notifications
You must be signed in to change notification settings - Fork 100
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
Update/Fix naming conventions #196
Comments
deadbytefpv
added a commit
to deadbytefpv/Docs
that referenced
this issue
Apr 18, 2022
#197 has been merged. |
yep, looks a lot better now, only things that still bother me:
|
Looks better now from #213 . I think we said Vantac b/c frsky doesn't have their name on it. Some still may be changed but generally formatting is better |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently naming conventions don't exist/are unintuitive/aren't followed/don't make sense.
One example to name directly:
https://expresslrs.org/2.0/quick-start/transmitters/tx-diy
vs
https://expresslrs.org/2.0/quick-start/receivers/rx-diyreceivers/
should be:
https://expresslrs.org/2.0/quick-start/transmitters/diy
and
https://expresslrs.org/2.0/quick-start/receivers/diy
Notice the differences:
diy
for the DIY receivers, as well as the DIY transmitters)tx-
andrx-
part got removed, as it doesn't make sense to have it, as it is redundant information (we already have thetransmitters/
andreceivers/
parts)I think the best option for naming would be to use the actual short namings (happymodel-ep1, happymodel-ep2, namimno-flash, happymodel-es900rx, etc etc).
A couple other things that bother me:
Flashing Receivers
andFlashing TX Modules
aren't coherent in their naming, should either beFlashing Receivers
andFlashing Transmitters
ORFlashing RX Modules
andFlashing TX modules
(I reckon the former one is easier to understand)Flashing <module>
before their name which makes it quite a bit harder to read, remove that as we know that we are flashing stuff and it's redundant informationSPI based AIO flight computers
section there too, and reference the /hardware/SPI-receivers section.The text was updated successfully, but these errors were encountered: