You do not need to read everything. Start with the topic that fits your question. The examples, free sheets and detailed sources are all still here.
The basics
What is hosting?
Your website needs a place to keep and share its files. That is called hosting. GitHub Pages is one kind of hosting. It shares ready-to-use website files. [1]
What can a simple site do?
It can show words, pictures and links. It can also have tools that run on the visitor’s own device. For example, a simple calculator can work this way. A site like this is called a static site. “Static” does not mean nothing can move or change. [1]
Some jobs need a host to run code while a visitor uses the site. This is called server-side code. GitHub Pages does not run this app code. Those jobs need another service. The extra details below explain this. [2]
Can two websites link to each other?
Yes. A normal link can take a visitor from one site to another. Your main website and a separate example page can each link back to the other. The main site can stay where it is.
Using your own domain name for the example is another option. That needs extra setup. Buying a domain name and choosing where the website runs are separate steps. [6]
Costs, rules & privacy
What can I use for free?
Is a .io domain the same thing?
What might cost more?
You can use a web address you own, called a domain name. For example: example.com. GitHub Pages supports this. [6]
Our advice: check what it costs to buy and renew that name. Also check any extra tools you need. Forms, email and saved customer records may use other services. Some have free plans. Others charge fees. Check before you sign up.
Can I use it for an online shop?
GitHub says Pages must not be used as free hosting to run an online business or shop. The rule also covers sites mainly used for sales or paid online software. GitHub warns against using Pages to handle passwords or card details. [3]
Our advice: check the rules for what you want to do. Ask GitHub Support if you are unsure. Adding a payment tool does not mean you can skip this check.
Will my website be private?
A private file repository does not, by itself, make the published site private. People may still be able to see the website. Do not put customer records or secret keys in files you publish. [2]
GitHub has a separate private-site option for some business plans. It has specific rules. It is not the normal setup. See the extra details below. [4]
GitHub Pages also supports HTTPS. This helps protect data as it travels between the site and a visitor. It does not make a public page private. [5]
Examples & free downloads
Where can I see a real GitHub Pages website?
The Cayman theme sample is a real website on GitHub Pages. It belongs to the pages-themes project. Tammy Builds did not build it. It shows text, links and file-download buttons. [7]
Look at its web address: pages-themes.github.io/cayman/. The github.io part shows the address supplied by GitHub. You do not need to download the theme’s code to look at the page.
Can I try a free website planning download?
Choose the button below to get a small text file with six questions about your website. No signup or payment is needed. You can save the file and fill it in later.
Download my website planning sheet (.txt) ↓
This file comes from the Tammy Builds website you are reading now. It is a download example, not a claim that this website runs on GitHub Pages. Files offered this way are public. They are not suitable for private customer documents.
How Tammy can help
What should I ask before choosing hosting?
Our planning tips:
- What do I want people to read or do?
- Do I need to take payments?
- Do I need to save anyone’s private information?
- Who will update the site or fix a problem?
- What might I need to pay for later?
A paid host is not always the best choice. A free host is not always the best choice either. Pick the setup that fits the job and allows your planned use.
Need help choosing a paid host?
I can help you compare paid hosting plans and choose one that fits what your website needs to do and what you can spend.
We can look at the starting price, the price when you renew, help when something goes wrong, backups and any tools you need. We can also check how easy it is to move your website later. You do not need to understand all the technical words. I can explain the choices in plain language before you buy.
Need programming or database help?
Some websites need more than pages to read. They need code that makes things work and a database that keeps information organized.
I can help build or improve those parts. For example, your website may need to save form answers, let customers sign in, search a list of items or connect to another business tool. I can help with website programming and database design, queries and fixes. We can work out what you need before choosing where to host it.
Why hire Tammy if hosting is free?
Free hosting gives your website a place to live. You may still need help making it do the right job.
What do you need your website to do?
You can hire me to help choose, build, connect, fix or care for your website. Tell me the result you want. You do not need to know the technical words.
I need a place for my website.
Compare free and paid hosts. Check prices, support and room to grow.
I need a new site or better pages.
Plan and build clear pages that work on phones and larger screens.
I need something made just for my work.
Write new code or fix code so your site does the job you need.
I need to save and find information.
Build or improve a database: a place to keep records in order.
I need people to sign in.
Set up accounts, sign-in, account recovery and an extra sign-in check when needed.
I want sign-in with Google or Microsoft.
Set up sign-in through a trusted account provider.
I need to choose who can see or change things.
Set rules for customers, staff and site owners. Test those rules.
My customers need their own space.
Build a private area for files, requests and work updates.
I want my tools to work together.
Connect your site to email, calendars or other business tools, with the access you approve.
I keep typing the same things.
Make forms save answers and start the next task for you.
People need to find the right item.
Add search, lists and filters to help them find what they need.
I need business reports.
Turn your records into clear reports and charts. Help you track what matters.
I want bookings, sales or paid access.
Connect booking and payment tools. Set up access after payment where needed.
People need to send me files.
Add uploads and checks for file type, size and who can open them.
People ask the same questions.
Add a help page, chatbot or AI helper, with clear limits and a way to reach you.
My site is hard to read or use.
Improve text, forms, phone layouts and use without a mouse.
My site is slow or broken.
Find the cause and fix slow pages, broken forms or failed tool connections.
I want to move my site.
Plan the move, set up the web address and help old links lead to the right place.
I need to keep my site working.
Plan updates, backups, restore checks and alerts when things go wrong.
I want help checking my site’s safety.
Review sign-in, access rules and how private information is handled. Agree on the checks first.
An AI or another builder made my site.
Review the code, test key tasks and fix problems before you rely on it.
I want to learn how to run my site.
Give you clear steps for the parts you will manage yourself.
See something you need?
Open a question above, then choose its link to tell me about that need. Your selected need and its explanation will come with your request. Or tell me about something else below.
Talk to Tammy about my website →Prefer email? Email support@tammybuilds.com ↗
You choose when to send. Asking a question does not book work or commit you to a payment.
A website is more than its look. I bring experience in software, databases and business needs, as well as current work with AI and automation. I can help with the parts behind the page, too.
Some sites need only a few of these things. We choose the parts that fit your goal and budget. Tool fees and any ongoing care are discussed before you agree to the work. Security checks reduce risk; no one can promise that a site will never have a problem.
How would we work together, step by step?
This is one way we can work together. An existing site may only need a fix or a review.
- Tell me the goal. What should people be able to do? Tell me in your own words.
- Pick the parts you need. Use the questions above to choose what matters. You may only need help with one part.
- Choose a plan and price. We agree on the work, the cost, any tool fees and who will keep it up to date.
- Build or fix it. I work on the agreed parts and show you how they work.
- Try it and check access. We test key tasks, phone use and who can see private areas. We fix issues we find.
- Put it live and plan its care. You approve the launch. We agree on backups, updates and who to contact for help.
The sheet opens in a new tab. You can print it or save it as a PDF from your browser’s print menu. No signup is needed.
An AI tool can help write code. I can help choose what is needed, review the work, test it and fix problems. You can ask for help with one part or a larger project.
Any paid work needs a clear plan and a price you agree to first. Free resources do not commit you to hiring anyone.
Tell Tammy what you need →Details & sources
What are the technical plans, privacy and size limits?
You can skip this section if you only need the main points.
GitHub Pages serves HTML, CSS and JavaScript files. It does not run server-side languages such as PHP, Ruby or Python. A feature that needs server-side code must run that part elsewhere. [1][2]
Eligible paid plans can publish from private repositories. The separate private-publishing feature requires GitHub Enterprise Cloud. It applies to eligible organization-owned project sites, not organization sites. Visitors need read access to the source repository. [1][4]
| What is measured? | GitHub’s limit |
|---|---|
| Published website size | Maximum 1 GB |
| Data sent to visitors | Soft limit of 100 GB per month |
| Builds: making the site ready to publish | Soft limit of 10 per hour. This does not apply when a custom GitHub Actions workflow builds and publishes the site. |
| Publishing time | A deployment times out after 10 minutes. |
A soft limit is a usage threshold, not a promised allowance or an automatic cutoff. GitHub may slow or limit requests, or ask owners to reduce usage or move hosting. [3]
Where do these facts come from?
We checked GitHub’s help pages and the linked live example on October 24, 2026. The numbered links above let you check the facts. Plans and rules can change. Our planning tips and advice are Tammy Builds’ views. This page does not replace a review of your own site.
- Source 1: What is GitHub Pages? ↗
- Source 2: Creating a GitHub Pages site ↗
- Source 3: GitHub Pages limits and permitted use ↗
- Source 4: Private publishing and access control ↗
- Source 5: HTTPS for GitHub Pages ↗
- Source 6: Custom domains and GitHub Pages ↗
- Source 7: Cayman: a live GitHub Pages theme example ↗