Skip to main content

Netlify Drop Is Easy. GitHub First Is Still Worth It.

· 4 min read

Netlify Drop is one of the lowest-friction ways to put a static project online. Drop a folder, zip file, or single HTML file into the browser, and Netlify gives you a shareable URL.

That is useful, especially for prototypes and projects exported from AI coding tools.

The problem shows up on the second deploy.

Drag and drop is great for "look at this." GitHub first is better for "this is the project."

Putting the project into GitHub before deploying to W7S adds one step, but that step buys history, repeatability, collaboration, and a deploy workflow that can grow with the app.

What Netlify Drop Optimizes For​

Netlify documents Drop as a way to publish a project when the code is on your computer and is not connected to a Git repository. You drag the folder to the Drop zone, then use the generated netlify.app URL.

That is an excellent first-publish experience.

It is also intentionally manual. To update a Drop project without Git, you rebuild or edit the local folder and drag the updated output folder into Netlify again.

For a tiny static page, that may be enough. For a project that someone will keep changing, the manual step becomes the weak point.

The Extra GitHub Step Changes the Project​

When the project goes into GitHub first, the folder becomes a repository:

  • every change has history;
  • the current production source is visible;
  • old versions can be recovered;
  • another person can suggest changes;
  • deploy rules live beside the code;
  • the same workflow can run again after every push.

That is why the extra step is worth it. It does not just make W7S possible. It makes the project easier to trust.

W7S Starts From the Repository​

W7S deploys from GitHub Actions. The minimum workflow is small:

.github/workflows/deploy.yml
name: Deploy

on:
  push:
    branches:
      - main
  workflow_dispatch:

permissions:
  contents: read

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - uses: w7s-io/w7s-cloud@v1
        with:
          token: ${{ github.token }}

For a plain HTML, CSS, and JavaScript site, that can be enough. For a project that needs a build, add install and build steps before the W7S action.

The important part is that deploy is now a file. You can read it, copy it, improve it, and review changes to it.

Why Beginners Should Learn This Path​

Drag and drop hides the release process. That feels friendly until something breaks and the beginner has no record of what changed.

GitHub first teaches a small number of durable ideas:

  • a repository is the project home;
  • a commit is a saved checkpoint;
  • a push sends changes to GitHub;
  • an Action can deploy the latest commit;
  • the app URL is tied to the repository.

Those ideas transfer to almost every serious software workflow.

When Drop Still Makes Sense​

Use Netlify Drop when the goal is:

  • a quick public preview;
  • a disposable demo;
  • a single static file;
  • a class exercise or one-off handoff;
  • a project that is not worth maintaining.

Use GitHub plus W7S when the project should keep living.

A Beginner-Friendly Recommendation​

If you have a folder on your computer, do this:

  1. Create a GitHub repository.
  2. Upload or commit the project files.
  3. Add .github/workflows/deploy.yml.
  4. Push to main.
  5. Open the W7S URL for the repository.

That is a little more work than dropping a folder into a browser, but it creates a project that has memory.

Sources​