Installing Sleeky Theme to Beautify YOURLS Short URL Program

Publish: 2021-01-04 | Modify: 2021-01-04

YOURLS is a well-established foreign short URL program that is free and open source. Because it is an old program, the YOURLS interface looks very outdated, with a style that is still stuck in the last century. A few days ago, I came across a YOURLS theme called Sleeky on Github, and this article shares the installation process for the Sleeky theme, hoping it will be helpful to you.

Link

Installing YOURLS

If you haven't used YOURLS before, you can refer to my article: YOURLS Installation, Configuration, and Settings for installation instructions. If you have already installed it, please continue reading.

Installing the Sleeky Theme

The latest version of the Sleeky theme can be downloaded from Github: https://github.com/Flynntes/Sleeky/releases

The Sleeky theme consists of two parts: the YOURLS front-end and the YOURLS backend. After downloading the Sleeky theme, you will see two folders:

  • sleeky-frontend: Front-end theme
  • sleeky-backend: Backend theme

Simply place the contents of the sleeky-frontend folder in the root directory of your YOURLS site. No additional configuration is needed, just access the YOURLS main interface to see the effects.

Frontend

Place the sleeky-backend folder in the /user/plugins directory of your YOURLS installation, and enable the Sleeky theme plugin in the YOURLS backend, as shown in the image below.

Backend

After activation, you will see that the appearance of the backend interface is much more aesthetically pleasing, as shown in the image below.

Backend Appearance

Conclusion

YOURLS does not come with a default frontend interface. You can install the Sleeky theme for the frontend as described above, or you can write your own frontend using the YOURLS API. For example, xiaoz provides a short URL service: https://xw.al/

In addition, the Sleeky frontend theme loads many resources from abroad, which may result in slower loading speeds in China. It is recommended to replace the static resource paths on your own.


Comments