Git Product home page Git Product logo

nfc-tools.github.io's People

Contributors

doegox avatar martinbeentjes avatar smortex avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

nfc-tools.github.io's Issues

Migrate content

The nfc-tools wiki has a number of informational pages that are not that easy to find with the current flat layout and would benefit from a move to Jekyll with a hierarchical organization.

  • Documentation
    • Chips
      • PN51x
      • PN53x
    • Initiators
      • ACR122
      • Arygon
      • OpenPCD 2
      • RC-S360
      • RDR608
      • SCL3711
      • StickID
    • Targets
      • FeliCa
      • Innovatron
      • Jewel/Topaz
      • MIFARE Classic
      • MIFARE DESFire
      • MIFARE DESFire EV1
      • MIFARE Plus
      • MIFARE Ultralight
      • MIFARE Ultralight C
    • Standards
      • ISO14443
      • ISO14443A
      • ISO14443B
      • ISO14443B'
      • ISO15693

Open questions:

  • Documentation (root element) is probably not the right name. Any better idea?
  • How to name / group initiators ?
  • Separating Targets / Standards is maybe not a good idea ?
  • Any point you would like to see discussed ?

Migrate project pages

Currently, the nfc-tools wiki has pages for each project, containing various information about obtaining, building, using and debugging the software. Some of these instructions are also present in the project repository (e.g. build instructions) and the duplicated information trend to be inaccurate (nfc-tools/libnfc#294).

Because GitHub's README.md is an ubiquitous primary source of information for most hackers (those I know at least), it makes sense to have the build instructions of each project in it's README.md file, and removed them from other places.

The nfc-tools website page for each project can become an "advertising" page highlighting key features of the project and linking to the GitHub repository.

Pages about "advanced" hacking (e.g. with patches, that is pages which contain code that can be broken in the future with the evolution of the tools) need to be timestamped and can therefore be moved in some kind of blog.

Finally, general information can be linked from each project's README.md regarding:

  • Debugging
  • Reporting bugs
  • Support

Any though are welcome !

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.