Build your academic website.
Choose a design you love. Make it yours with AI. Publish it with GitHub Pages.
Pick a design you love. Make it yours with AI. Publish it free.
In this workshop, you will choose a website template, use a chatbot as your personal web-design tutor, and publish a professional website with GitHub Pages. No prior coding experience or paid hosting required. Bring a laptop and internet access.
Your roadmap | approximately 90 minutes
0–10: Decide what your website should communicate. 10–25: Browse and choose a template. 25–50: Customize it with a chatbot. 50–70: Publish to GitHub Pages. 70–90: Test, improve, and share.
1. Plan your story
Who is your audience: prospective research mentors, graduate programs, employers, collaborators, or the public? What should they remember? List your interests, two or three examples of work, and how you want to be contacted. A project, course, poster, internship, volunteer experience, or research question all count. You do not need publications.
Ask a chatbot: “Help me plan my first professional website for [audience]. My interests and experience are [facts]. Suggest a short headline, bio, and three appropriate sections. Ask me questions if details are missing; do not invent results, credentials, publications, or affiliations.”
2. Choose a template
Browse the BootstrapMade resume and CV collection or personal website collection. Open a few Live Demo previews. Pick a layout you like on both a phone and computer, not one whose example content resembles your career. A simple one-page layout is usually easiest. For example, compare Personal and Laura.
On your chosen template page, select Download and choose the free download if offered. You do not need to purchase a Pro plan for this exercise. Follow that page’s current prompts. Save the ZIP, then extract/unzip it. Open the extracted folder and find index.html, often alongside an assets folder. Open index.html in a browser to see the design.
Free-template license: BootstrapMade requires keeping its “Designed by BootstrapMade” footer credit intact. Review the current license yourself. Do not redistribute the template as your own product. Preserve the license and copyright files.
3. Understand the template folder
Think of index.html as the homepage, CSS as appearance, JavaScript as optional interactivity, and assets as the accompanying styles, images, fonts, and scripts. Your exact folder structure may differ. Preserve the template’s existing CSS, JavaScript, Bootstrap version, and asset paths; do not ask a chatbot to convert it into a single file or remove its dependencies. Keep the extracted folder together; uploading only index.html often produces an unstyled or broken site.
Make a backup copy before editing. Use a code or plain-text editor such as VS Code, not a word processor. Some template features may rely on a server: GitHub Pages hosts static files, so PHP forms will not work there. Replace the contact form with a professional email link or remove it unless you arrange a compatible form service separately.
4. Let a chatbot be your tutor and collaborator
If your chatbot accepts files, upload the template ZIP or relevant files, subject to its file limits and the template license. Otherwise paste index.html in manageable parts, and share the folder structure and relevant CSS when needed. Never share passwords, tokens, private data, or unpublished confidential work.
Start here: “I am a beginner making an academic website using this Bootstrap template. First inspect the files and explain the folder structure and how to preview the site. Then ask me what I want changed. Preserve the existing design, responsive behavior, working relative asset paths, and required BootstrapMade footer credit. Do not invent accomplishments or add a framework. Give me complete replacement files, exact filenames, and step-by-step instructions. My accurate information is: [facts].”
Customize: “Replace the example content with my information below. Remove sections I do not need, including fake testimonials, skill percentages, counters, and claims. Keep the credit footer. Tell me what files to replace and which images I need to supply. Do not change facts or create nonexistent links. [facts]”
Polish: “Make the site feel [three adjectives], with readable mobile typography and accessible contrast. Preserve the template structure and attribution. Explain each change and give complete files rather than snippets.”
Save the returned code in the matching file. If the chatbot returns only index.html, do not delete the other template folders. Refresh your local browser. Verify the chatbot’s facts and claims, and inspect your changes before publishing.
Images and contact
Use your own images or properly licensed ones. Put them in the appropriate assets folder; match filenames and capitalization exactly, and add useful alternative text. A professional email link can look like mailto:you@example.edu. Photo, CV, and contact details are optional.
5. Create your GitHub repository
Sign in at github.com or create an account and verify your email. Select + → New repository. For a personal homepage, use exactly YOUR-USERNAME.github.io, substituting your actual GitHub username. Choose Public and create the repository. GitHub Free supports Pages in public repositories.
If you already have that repository, do not overwrite it. Instead make a new repository named, for example, portfolio. The site address will be https://YOUR-USERNAME.github.io/portfolio/. Use relative asset paths such as assets/img/photo.jpg, not a path starting with /, for portability.
6. Upload the whole site and publish
1. In the repository choose Add file → Upload files, or the upload link in an empty repository. Open your extracted template folder and select the contents: index.html, assets, and any other files it needs. Do not upload the ZIP or an enclosing parent folder. Keep folder structure intact.
2. Confirm that index.html is at the top level of the repository and assets appear beside it. Write a commit message such as “Add my site” and select Commit changes. A commit is a saved version. If the browser will not preserve folders or the upload is too large, upload smaller batches into the correct folders, or use GitHub Desktop to add the complete site folder and publish it to the repository. GitHub browser uploads allow up to 100 files per batch, with a 25 MiB limit per file.
3. In the repository go to Settings → Pages. Under Build and deployment choose Deploy from a branch; select main and /(root), then Save. If the branch is missing, first commit the files.
4. Wait for deployment, then open the address shown in Settings → Pages. GitHub says publishing can take up to 10 minutes. Check the live site rather than assuming that uploading files published it.
Public means public
Your site and repository files are visible to anyone. Do not post a home address, student ID, personal phone, passwords, tokens, unpublished sensitive research, private information about others, or a CV with details you do not want public. Git history can preserve deleted content. Review every file before uploading.
7. Test, improve, and share
Open the live site on a phone and laptop. Check the menu, project links, images, spelling, real contact details, and the template attribution. Remove placeholder content and unearned credentials. Navigate with the Tab key. Ask a partner: “Can you tell who I am and what I am interested in within ten seconds?”
To update later, open a file in the repository and click the pencil, or upload revised files to the same locations. Commit changes and wait for redeployment. Share the live website URL, not merely the repository URL.
Troubleshooting
404: Check the exact URL; include /portfolio/ for a project site. Verify Pages is configured for main and /(root), index.html is at the root, and deployment has completed.
Plain page or missing images: Upload the assets folder too. Match capitalization and check relative paths. A project site should usually use assets/... rather than /assets/....
Changes not visible: Confirm you committed to the publishing branch, wait for the deployment, check Actions for errors, and refresh.
Contact form does nothing: GitHub Pages does not execute PHP. Replace the form with an email link or explicitly set up a compatible external service.
Ask AI for help: “My GitHub Pages site should show [expected], but shows [actual]. It is a BootstrapMade template. Here is the site URL, folder structure, exact error, and relevant code: [details]. Explain the simplest fix in beginner-friendly steps. Preserve my existing files and attribution. Never request credentials.”
Instructor close
Have students exchange their live URLs and offer one concrete improvement. Finish with a functioning site or locally previewed draft, one accurate sentence about their interests, and a next step. Students who finish early can improve accessibility, projects, and mobile layout.
Official references
GitHub Pages quickstart | Create a Pages site | Configure publishing source
BootstrapMade license | Browse templates
Updated November 17, 2026. Interface labels and service terms may change; use the linked official documentation for current details.