Here a To-Do list & suggestions for the h-node project development and alike:

• RSS feeds of the modifications (done!)
• Mobile version of the website (partially done)

Only for some pages, for example the home page, the hardware pages, the search page. This should be done by adding a parameter in the URL (perhaps at the end) and decide the CSS file that should be loaded (if no parameter is present than the website will be optimized for monitors)

• Continue internationalization

(There are a lot of areas still in English)

• Build a form to help the user to choose a device

Something better than the current cataloging, perhaps inside the home page. The form should also consider those devices that can be easily mixed up, for example the ones ith the same model name but different chipset, and alerting the user or not suggesting that hardware at all (for each device it should be possible to add such an alert by the users or by the administrators)

• Add the possibility to download a pdf file

Built on the fly for example with fpdf) of each device page and in case of the whole database (Luis Alberto is working on this :)

• Add new categories of hardware

What should be the next category?

• Repair the translation management : currently (2017-11) translating https://h-node.org/wiki/page/fr/Main-Page does also replace the english page https://h-node.org/wiki/page/Main-Page)
• Add the toc option to the wiki (done: see the source of this page)
The table of contents ( TOC) is a great option to preview the documentation structure and keep organized the documentation structure. Like the one on mediawiki :)
• Improve wiki formatting
• Nested listing (done!)
On some cases we need to list inside a list, currently this is not possible.
• No formating text (partially done: use double { in place of [ and double } in place of ]. Example: [b]hello[/b])
Currently the code tag can't disable some functions as URL Links, headers, listing, and other tags. So while trying to explain the usage of the tags it is not possible to show the "How should it writes" and "How will it look".
• Tables
Adding tables to the wiki would be great to organize information.
• Quoting
Good option for the Issues page than the wiki.
• Comments?
Comments inside the wiki plain text for editors that are not displayed.
• Basic Font Color
Implementing some basic font colors would be a good idea, like blue, green, yellow, red on some topics.

• Add the possibility to export the hardware configuration

Hardware working or not working to an xml file

• Add the possibility to load the hardware configuration from an xml file
• Add the possibility to submit a whole xml file created by the client
• Add a preview hardware tab/window on the client

Right now when the client is launched it gets you to the main page where it modifies the devices by just typing on the fields. Not pretty sure it's the best way of opening the client, since a bad move on the keyboard could imply unwanted changes to the database.

The lspci -vmmnn search first sends a page where you can see if the hardware is already on the database and also tells you if it works or doesn't. If not present it will show an invitation to insert it.

So maybe the first tab?/window? at the client should show a "preview" of the hardware status, then invite to add/update the hardware found.

• Client l10n

Starting the localization of the client to the current supported by the project.

• English (complete text, needs proofreading and editing)
• Español
• Italiano
• Français
• Deutsch (mostly complete)

Mtjm's list:

• make communication with the server asynchronous (would solve the performance problem)
• laptop support (needs big design changes on both sides)
• redesign the database format to be more useful for the client
• improve test coverage (needs API changes)
• find which distros are supported
• write documentation for users, packagers and developers
• fix crashes caused by incorrect data sent by the server
• improve error reporting (so the user gets all data that is needed to test the issue elsewhere)
• check if dmidecode or another tool will get other useful data
• test some devices if they are supported

Please write on the list if you want to solve one of these issues.

• write an application for the Replicant operating system

It would be nice to have the h-node application or something similar

• ?