---
# System prepended metadata

title: Untitled

---

#### New section: Docs.ubports.com > Platforms > Devices (can also be published as blog posts)

#### On Devices.ubports.com (after: "find your device")
**Note**: The more challenging devices may not be supported by the [installer](https://devices.ubuntu-touch.io/installer/) and you may find very little information out there to help you get started with it. You might do better to go straight to another device which has a good level of support built around it. Otherwise, consider reaching out to the porter for detailed and up-to-date information.
- A: For porters, making sure that the relevant information can all be found in one place will help us, will onboard newcomers more quickly and will make the device's site much more useful over time.
- A: Developers are good at creating software, but explaining their work in terms that others can understand may not be their strong point.
- Q: "Isn't that the porter's job?" 
- Q: Why does content obtained from Ubform or Git need to be rewritten for ordinary readers?

1. The device name is simply what the smartphone is called in retail sale 
1. Look for a device page which seems to you to be weak on content, and where you're background knowledge gives you a good shot at filling in the gaps
12. External links 
14. Team 
16. Notes [...]
17. SEO & Meta description [...] 
2. Create a draft with the above structure
2. The device codename, means the project name the manufacturer uses before launch [e.g. jasmine_sprout]
3. The device's kernel, is the executive program at the core of any computer operating system
3. Read the [instructions](https://gitlab.com/ubports/infrastructure/devices.ubuntu-touch.io) for how to update devices' markdowns
4. The so-called 'maturity score' is what we use to give a fair impression of the overall functionality and performance of a device.
4. Just start writing and when you need to ask questions, there will always be someone ready to help
5. Finalize your review and commit 
5. Porting status indicates the general state of the porting effort, and especially whether progress has ground to a halt or is continuing. If we say the port is 'making progress' that suggests that the port will get better over time. 'Currently stalled' is a bad sign and indicates either a dead-end or a hope that it will eventually be picked up by a new porter. If it is an actual dead-end it probably means porting failed for a reason, such as lack of manufacturer documentation, or some technical brick wall.
6. Describe the usability of the device based on your own personal experience. Share what you like about it and the things which don't work as well. Highlight any particular features, such as a great looking screen or a pretty bad camera. Concentrate on the specifically UT things. There are a ton of reviews out there with it running Android. Be straightforward, and share what has really made your experience memorable.
7. Listen to 'Never gonna give you up' by Rick Astley and celebrate.
7. Specifications table
8. Repeat.
9. Installation steps Add the manufacturer's specification table, so visitors can compare devices
10. As an experienced UT user, your task is to explain installation and the functionality of the device, so that visitors can properly understand how to flash their phone with the installer or where that is not possible, without.
11. Due to the natural characteristics of open source, information tends to be spread across and wide range of resources and it can be a challenge to hunt everything down. We encourage porters to bring everything together in one place and to keep the most relevent links for their device up-to-date
12. Entry Level
13. Familiarity with one or more devices, and just very basic testing skills are enough. It would be even better if you have several devices running UT.
14. Finding all the necessary information might require some digging. We are
15. counting on you to deliver the best you can.
16. From top to bottom:
17. At present some devices still lack basic features or in some cases it is even a struggle to get them to boot! The more detailed the information you give about them, the easier it will be for someone to follow so that they can test or contribute and speed things up 
18. If you can, point to the ways in which would-be users of a device can give feedback porter, to help them see beyond blocks 
19. Help close the gap between newcomers’ expectations of a device and the actual experince of using it by writing honest and detailed reviews 
20. The journey from the initial idea to the point where a new device will boot up a fully working Ubuntu Touch can be long and discouraging. That is where you can help.
21. Improve the site for the device by giving newcomers everything they need to make the best choice between devices. Your job is to transform the available resources into easy to read device guidelines. Remember, most of our visitors have very little idea what it takes to get Ubuntu Touch up and running on a phone.
22. Join the [writers' group ](https://t.me/joinchat/RJqvps-k-pDu3y4f)
23. On Docs.ubports.com > Contribute > Alternative ways
24. Every month the Devices site attracts hundreds of people who are exploring how to put a new operating system such as Ubuntu Touch on their smartphone.

The devices which are not included in the installer require elaborate and probably unfamiliar steps, even before building the system image. This is something which will put off all but the real enthusiast.

We are dealing with two quite different groups of people. The first is the most common here, the ordinary user, who wants to install UT for the first time. The second group consists of porters, developers,and enthusiasts
Two Telegram groups will come in handy: for the average user [Welcome & Install](https://t.me/WelcomePlus), and for the enthusiast [porting group](https://t.me/ubports_porting).
UBports forum, git repositories, YouTube and our Telegram groups will be your main sources for gathering information.
[Read more about this opportunity here](https://docs.ubports.com/en/latest/contribute/documentation.html) >