FTP-Deploy-Action VS Skeleton

As GitHub Actions is a community-driven platform, we can utilize various open-source workflows available. In this case, we will use the popular "FTP-Deploy" Actions workflow developed by Sam Kirkland. In the main.yml file, include the following code:

This is where the files are now transferred to the shared hosting server. Get your FTP details from your shared hosting. Then go to your repo>settings>secrets then add the three secrets namely: server, username and then password. This action is courtesy of SamKirkland.

SamKirkland/FTP-Deploy-Action

It uses Skeleton https://github.com/dhg/Skeleton which is a billion years old.

To get styling out of the way, let's download Skeleton CSS, unzip all the CSS files into the src directory, and import all the .css files in the App.css main stylesheet in the project:

Skeleton - 18K⭐ - Last update: December 2014 (Wow! Since 2014!)

Latest stable version: 2.0.4 Github stars: 18.3K Development: without activity for 7 years Long of active development: 1 years Active maintainers: 0 Contributors: 25 Number of commits: 167 License: MIT Used by: 0 Github projects Git repository: https://github.com/dhg/Skeleton

dhg/Skeleton - Skeleton: A Dead Simple, Responsive Boilerplate for Mobile-Friendly Development

So I decided to start with Skeleton. The downside with Skeleton is that the GitHub project is not active anymore. The last release was in December 2014 and there are open PR’s and issues. But besides that it was quiet easy to integrate and customize. Skeleton worked quite well, but the point that the project is not active anymore made me switch to Milligram. Milligram also provides a minimal setup of styles for a fast and clean starting point. So it was easy to adapt my design and switch to Milligram.