02 — Methods / Blog
Building a Research Portfolio
Website with No Coding
Free and fully no-code, with Claude Code, GitHub, and Cloudflare Pages
This website (yamarice.pages.dev) was built without writing a single line of HTML by hand. Claude Code, an AI coding assistant available through Claude Desktop, handles everything from initial creation to ongoing updates. You simply describe what you want in plain language. Files are managed on GitHub and hosted automatically via Cloudflare Pages, with no frameworks or monthly fees required. This guide walks you through the entire process from scratch.
What you need (all free)
- Claude Desktop Install it from claude.ai/download. Launch Claude Code inside it to create and edit files with plain-language instructions. No coding is required.
- GitHub account A cloud service for managing your files. Sign up at github.com.
- GitHub Desktop An app for sending your changes to GitHub by clicking buttons. Install it from desktop.github.com.
- Cloudflare account A service that publishes and hosts your site automatically. Sign up at cloudflare.com.
Create a local folder and connect Claude Code
What is Claude Code?
Claude Code is an AI assistant from Anthropic. Open a folder on your computer, describe what you want in plain language, and it creates and edits the files for you. Unlike a chatbot that only answers questions, it can do the editing itself.
First, create a folder on your computer for the website (e.g., a folder called website on your Desktop). Then open Claude Desktop and click the "Code" tab at the top to start using Claude Code.
- Create a new folder anywhere on your computer (e.g.,
Desktop/website) - Open Claude Desktop and click the "Code" tab at the top
- Click "Add folder" or the folder icon, then select the folder you just created
Once connected, just describe what you want in plain English. You don't need to know HTML or how to code.
"Please build a researcher portfolio website using HTML, CSS, and JavaScript. My name is Jane Smith, and I am an Assistant Professor at Example University. Include sections for About, Publications, and Links, with a clean, mobile-friendly design. Save the files as index.html, style.css, and script.js in this folder."
Claude Code will generate all the files directly inside the connected folder. To make changes, just describe what you want, such as "Change the header color to dark green" or "Add a new publication." Claude Code handles the rest.
Claude Code reads and writes files directly, so you never need to open a text editor. You can also ask it to "review the current site" at any time, and it will read all the files and give you a full overview.
Create a GitHub account and repository
What is GitHub?
GitHub is a cloud service for storing and managing files. Think of it as "Google Drive for code." It keeps a full history of every change you make. Once you connect it to Cloudflare Pages, your site updates automatically whenever you send new files.
Creating an account (first time only)
- Go to github.com and click "Sign up"
- Enter your email address, set a password and username, then complete email verification
Creating a repository
A repository is your project folder on GitHub. It is the online counterpart of the local folder you created in Step 1.
- Log in to github.com and click the "+" icon in the top right → "New repository"
- Enter a repository name (e.g.,
my-website, using only letters, numbers, and hyphens) - Select "Public" (required for Cloudflare Pages to access it)
- Click "Create repository"
The repository name does not affect your site's URL. Cloudflare Pages will generate a separate URL for you.
Connect your folder with GitHub Desktop and push
What is GitHub Desktop?
GitHub Desktop is an app that lets you send files to GitHub by clicking buttons, so you don't need any command-line knowledge. Download and install it from desktop.github.com.
Commit means recording your changes as a snapshot, like creating a save point in a game.
Push means sending those recorded changes up to GitHub, much like syncing a folder to the cloud.
First-time setup
- Open GitHub Desktop and click "Sign in to GitHub.com," then sign in with the account you created in Step 2
- Go to "File" → "Add Local Repository" and select the folder from Step 1
- If prompted with "This folder does not appear to be a Git repository," click "Create Repository"
- Type a short description in the "Summary" field at the bottom left (e.g.,
Initial commit) - Click "Commit to main" to record your changes locally
- Click "Publish repository" in the top bar to send your files to GitHub
- Uncheck "Keep this code private" and click "Publish Repository"
Open github.com in your browser and you should see your files uploaded to your repository. Your local folder and GitHub are now in sync.
Deploy with Cloudflare Pages and get your URL
Connect your GitHub repository to Cloudflare Pages to publish the site automatically.
What is Cloudflare Pages?
Cloudflare is a company that runs a global network for delivering websites quickly and securely. One of its services, Cloudflare Pages, publishes the files in your GitHub repository as a website, free of charge.
- Log in to dash.cloudflare.com (create a free account at cloudflare.com if needed)
- In the left menu, go to "Workers & Pages" → "Create" → "Pages" tab
- Click "Connect to Git" and authorize your GitHub account
- Select the repository from Step 2 and click "Begin setup"
- Leave "Framework preset" as "None," leave "Build command" and "Build output directory" blank, then click "Save and Deploy"
Deployment completes in about 30 seconds. You will receive a URL like your-project.pages.dev. That is your live website.
From this point on, every push to GitHub automatically triggers a new deployment. No manual action needed.
How to update your site
Once your site is live, all future updates follow the same no-code workflow. Just describe the change to Claude Code, then push.
to make the change
in GitHub Desktop
automatically in 1 to 2 min
"Add a new publication to the Publications section. Title: [title], Journal: [journal], DOI: [DOI]."
"Update the About section to say the following: …"
"Apply the same changes to the English version of the page."
After Claude Code edits the files, commit and push with GitHub Desktop.
- Confirm your changed files appear in the left panel of GitHub Desktop
- Type a short commit message in the "Summary" field (e.g.,
Add new publication) - Click "Commit to main," then "Push origin"
You can monitor deployment progress in the Cloudflare Pages dashboard (dash.cloudflare.com). A "Success" status means your changes are live.
Things to watch for when updating
Check what changed. Claude Code sometimes edits more than you asked for, or changes something in a way you did not expect. Before you commit, look at GitHub Desktop to see which lines changed in which files. Red lines were removed and green lines were added. It also helps to open the page in a browser and check how it looks.
Explain your workflow to Claude in advance. Tell it the ground rules at the start, for example that this folder is published and that every push goes live right away. If you write these rules in a file called CLAUDE.md in the folder, Claude Code reads it at the start of every session and follows it without being reminded. You can simply ask Claude Code to write the file for you.
"This folder is connected to GitHub and Cloudflare Pages. Anything I push goes live immediately."
"Only commit or push when I ask you to."
"After editing, tell me briefly which files you changed and what you changed."
"When you change the English page, make the same change to the Japanese page."
CLAUDE.md sits in the same folder, so by default it is pushed to GitHub and can be viewed on your site. If you want to keep it private, add it to the .gitignore file described below.
File management and repository visibility
Because every file in your folder ends up on GitHub, it's worth guarding against accidental leaks from the start. This section covers two ways to do that. One is listing the files to exclude from uploads, and the other is switching your repository to Private.
Using .gitignore to exclude files
A .gitignore is a plain text file placed at the top level of your repository. Anything listed in it is excluded from uploads. It is commonly used to keep OS-generated files, editor settings, and other local-only items out of the repository.
Never commit confidential information. API keys, passwords, unpublished research data, and personal information about research participants must never be committed, whether the repository is Public or Private. Once committed, the data stays in the history forever, and switching to Private afterward does not remove the risk of a leak.
Create a file named .gitignore at the top level of your folder. The example below is a safe starting point. You can also simply ask Claude Code to "create a .gitignore," and it will generate one for you.
# OS files .DS_Store Thumbs.db # IDE / editor .vscode/ .idea/ # Logs and caches *.log .cache/ node_modules/ # Secrets (as needed) .env secrets.txt
Switching the repository to Private
If you do not need your source code to be publicly visible, you can switch the repository to Private. Only you and the collaborators you invite will see the contents. Your published site (the pages.dev URL) remains accessible to everyone, because hosting is unaffected.
Cloudflare Pages connects through an OAuth-based GitHub App. This means that once you have completed the initial connection while the repository is Public, you can switch to Private afterward, and automatic deployments will keep working. To stay safe, confirm that the first Cloudflare deployment has succeeded before switching to Private.
- Open the repository page on GitHub (e.g.,
github.com/your-username/your-repo) - Click the "Settings" tab
- Scroll to the bottom, and under "Danger Zone," click "Change repository visibility" → "Change visibility"
- Choose "Make private" and type the repository name to confirm
Right after the switch, check the Cloudflare Pages dashboard to confirm the next build runs successfully. If you see a "cannot access repository" error, go to GitHub Settings → Applications → "Cloudflare Workers and Pages" and add the repository to its allowed list.
If you want the repository to be Private from the start, simply choose "Private" in Step 2. You will then need to explicitly grant the Cloudflare GitHub App access to that specific repository when you connect Cloudflare Pages.
Getting your site to appear on Google and Microsoft Edge
A newly published site is unknown to search engines, so it will not show up in search results yet. Let both Google and Bing know about it. Bing is the default search engine in Microsoft Edge. It can take a few days to a few weeks for your pages to appear.
First, make a sitemap
A sitemap (sitemap.xml) is a file that lists every page on your site. Ask Claude Code to create a sitemap.xml for all your pages. After you commit and push, check that https://your-project.pages.dev/sitemap.xml opens in your browser.
Google Search
- Open Google Search Console and sign in with your Google account
- Click "Add property," choose "URL prefix," and enter your site's URL (e.g.,
https://your-project.pages.dev/) - To verify ownership, choose "HTML tag." Give the
<meta>tag it shows you to Claude Code and ask it to add the tag to the head of your home page. Once the change is live, click "Verify" - Open "Sitemaps" in the left menu, enter
sitemap.xml, and submit it - For pages you want listed soon, paste the URL into the search bar at the top and click "Request indexing"
The "Domain" option does not work with a pages.dev address, because you cannot change its DNS settings yourself. Choose "URL prefix" instead.
Microsoft Edge (Bing)
When you search from the address bar in Microsoft Edge, the results come from Bing by default. To appear there, register your site with Bing Webmaster Tools.
- Open Bing Webmaster Tools and sign in with a Microsoft or Google account
- Choose the option to import from Google Search Console. Your site and sitemap carry over as they are
- If you skip the import, add your site's URL by hand, verify ownership with an HTML tag as you did for Google, and submit your sitemap
Bing also supports IndexNow, a way to notify search engines right after you add or change a page. Ask Claude Code to set up IndexNow, and it will help you prepare it.
Helping people find you
- Write accurate
<title>and<meta name="description">tags in the<head>of each page - Add your site URL to external researcher profiles (researchmap, ORCID, institutional pages) so more sites link to yours
Once your site is indexed, a search for your name on Google should bring it near the top of the results.