Home首頁  /  Lessons課程  /  Lesson 3第三課

Why I Don't Use Google Sites為什麼我不選用 Google Sites?

Google Sites is genuinely easy — it hosts a page for you, and you just paste in an embed. If you only ever need one simple page, it's a fair choice. So why do I still teach GitHub? Because the moment you want a real, growing website that looks the way you imagine, Google Sites quietly boxes you in. Here's the honest picture — the good and the limits.

Google Sites 真的很容易——它幫你 host 一頁,你只要貼上 embed 就好。如果你永遠只需要一頁,它是個合理的選擇。那我為什麼還是教 GitHub?因為當你想要一個會成長、又能照你想法呈現的真正網站時,Google Sites 會悄悄把你框住。這一課我老實攤開講——好處和侷限都說。

What you'll understand你會明白

  • a What Google Sites is genuinely good ata Google Sites 真正的強項
  • b Where it quietly limits youb 它在哪裡悄悄限制了你
  • c Google Sites vs GitHub Pages, side by sidec Google Sites 與 GitHub Pages 並排比較
  • d When each one is actually the right choiced 兩者各自什麼時候才是對的選擇
Fair is fair先說公道話

Google Sites really is easyGoogle Sites 確實很簡單

Let's give it full credit. For the simplest needs, it's hard to beat:先給它應得的肯定。在最單純的需求上,它很難被打敗:

For a single notice, a quick sign-up, or one simple page — honestly, that's fine. If hosting 20 separate pages sounds like too much, making one Google Sites page at a time is a perfectly reasonable way to work.對於一則公告、一個快速報名、或一頁簡單的頁面——老實說,這樣就夠了。如果要 host 20 個頁面聽起來太麻煩,每次只用 Google Sites 做一頁,其實是完全合理的做法。

The catch但問題在這

Where it quietly limits you它在哪裡悄悄限制了你

The trouble starts the moment you want more than one simple page — or you want it to look truly yours.麻煩會在你想要「不只一頁」、或想要「真正屬於自己的樣子」時開始出現。

The deepest limit:最根本的侷限: on Google Sites your beautiful AI-made page is a guest in a box. On GitHub, it is the page. 在 Google Sites 上,你那漂亮的 AI 頁面只是「框裡的客人」。在 GitHub 上,它本身就是那一頁。
Side by side一張表看懂

Google Sites vs GitHub PagesGoogle Sites vs GitHub Pages

Google SitesGoogle Sites GitHub PagesGitHub Pages
How you build怎麼做 Drag-and-drop + embeds拖拉 + 嵌入框 Real HTML files (AI makes them)真正的 HTML 檔(AI 做的)
Your AI-made page你的 AI 頁面 Sits in a box (iframe)塞在框裡(iframe) IS the actual page本身就是那一頁
Control over design設計掌控 Limited to templates受限於模板 Full control完全掌控
A 20-page site20 頁的網站 Google's menu, hard to keep custom用 Google 的選單,難客製一致 One folder, shared menu & style一個資料夾,共用選單與樣式
The web address網址 Long, Google-controlled又長、由 Google 掌控 username.github.io (or your own domain)username.github.io(或你自己的網域)
Who owns the files檔案誰擁有 Inside Google's system關在 Google 系統裡 You — download & move anytime你——隨時下載、搬走
Cost費用 Free免費 Free免費
Best for最適合 One quick page, no fuss單一頁面、求快不求多 A real, growing, custom site會成長、能客製的真正網站
Be fair那什麼時候用它

When Google Sites is the right call什麼時候 Google Sites 才是對的

If you need exactly one simple page today, never want to touch a file, and just want something live fast — Google Sites is a perfectly good choice. No shame in it. But if you want a website that grows, looks the way you imagine, and genuinely belongs to you — that's why, in this course, I teach GitHub.如果你今天就只需要一頁簡單的頁面、完全不想碰檔案、只想快點上線——Google Sites 是個很好的選擇,一點都不丟臉。但如果你想要一個會成長、能照你想像呈現、又真正屬於你的網站——這就是為什麼這門課我教 GitHub。

Quick recap快速回顧

  • Google Sites is genuinely easy for one simple pageGoogle Sites 做單一簡單頁面確實很容易
  • But your AI page only goes in as an embedded box, not the real page但你的 AI 頁面只能以嵌入框放入,不是真正的頁面
  • Design, URL, and your files all stay under Google's control設計、網址、你的檔案,全都留在 Google 的掌控裡
  • A custom 20-page site is hard to keep consistent there在那裡,客製的 20 頁網站很難維持一致
  • GitHub keeps the HTML truly yours — portable and fully yoursGitHub 讓 HTML 真正屬於你——可攜帶、完全是你的
  • Use Google Sites for quick one-pagers; use GitHub for a real site快速單頁用 Google Sites;真正的網站用 GitHub