6 pages
How to build your first personal website
Turn supplied sample content into a small personal website with a coding assistant, then test it like a visitor.
- Estimated time
- 27–45 min
Practical lessons for anyone building something online, and a learning path for software developers.
Save your progress and continue where you left off.
Learn by building with supplied examples and an AI assistant. You do not need to know how to code; each lesson explains the tools and accounts you need.
Estimates for the supplied starter files with prerequisite accounts and tools ready. Setup, deployment queues and delivery/DNS waits take additional time.
6 pages
Turn supplied sample content into a small personal website with a coding assistant, then test it like a visitor.
5 pages
Publish the supplied page from a GitHub practice repository and verify that a later edit reaches the public site.
5 pages
Connect a domain you control to a supplied or existing practice site, preserving unrelated settings and checking HTTPS.
5 pages
Set up a domain mailbox through your provider and verify receiving, sending and replying with inboxes you control.
5 pages
Use a ready broken page, ask a coding assistant for a focused phone-layout repair and check the same visitor tasks afterward.
5 pages
Resize the supplied image with the ready tool, have an assistant connect the smaller files and verify clarity and real downloads.
8 pages
Publish a ready contact form, connect your notification inbox and trace one message all the way through.
8 pages
Connect a provider-hosted subscription form and test joining, email confirmation and leaving with your own address.
5 pages
Run a supplied email project with an assistant, send a controlled confirmation and verify its arrival in your inbox.
5 pages
Save a website form in a supplied practice database project, then verify the record survives reopening the page.
5 pages
Connect the ready sign-in page to a managed account service and test email codes, sign-out and failed attempts.
5 pages
Use a ready sign-in project to keep a practice note private and test both allowed and denied access.
5 pages
Save and reload an account’s display name, then use a second test account to check that another person cannot change it.
5 pages
Upload, reopen and delete supplied test images while checking size limits and account ownership.
4 pages
Use a supplied server-backed example to keep a provider key out of the visitor’s browser and verify allowed and rejected requests.
4 pages
Use a ready repository lookup page, add one useful result with an assistant and check normal, missing and unavailable responses.
4 pages
Run a ready private chatbot with a coding assistant and test whether a follow-up uses the conversation and survives a failed request.
4 pages
Use a ready café project to connect a chatbot to supplied facts, show its sources and test a new rule with a coding assistant.
4 pages
Give an assistant your article text, add it to the ready blog and verify that readers can open, read and return from it.
4 pages
Add a new supplied article with an assistant and verify that visitors can find and open it through the ready search page.
4 pages
Give an assistant equivalent text for a second language and check that switching preserves the full page meaning and useful links.
8 pages
Inspect a public page you control, have an assistant fix accidental search blocks and record what Google actually reports.
4 pages
Give an assistant a title, description and supplied image, then check the card a real public link produces.
4 pages
Measure one useful visitor action in the supplied page, then compare consent-off, consent-on and repeat-click results with an assistant.
4 pages
Create a clear test appointment, connect its public booking link and verify booking, time zones and cancellation.
5 pages
Create a test Payment Link, connect it to the supplied page and verify the payment in your provider account without building a payment backend.
4 pages
Prepare a small website change with an assistant, review its separate preview address and keep production untouched until approval.
4 pages
Rehearse restoring a known working release on a disposable site, then verify the visitor action actually works again.
4 pages
Download a real backup of supplied practice records, restore it into a separate empty practice target and check the recovered values.
4 pages
Reproduce a supplied broken visitor action, ask an assistant for a focused repair and verify the same action after the change.
These lessons serve different audiences. Preparing for an interview, improving code, building an idea with AI, and making product decisions are different needs. Start with the lesson that fits yours.
Each course card states its own prerequisites. The first two use Python examples; you do not have to complete them before studying GenAI Development or Product Eye.
Read the explanation and worked example, then try the exercise yourself. Discuss your answer with the lesson tutor or compare it with the worked solution. Copy the code and run it in your own environment.
Suggested learning path
A suggested route for software engineering students and early-career developers: solve the problem, write readable code, develop with AI, then evaluate the product from the user’s perspective. Experienced engineers can start where they need practice.
Work through all four in order, or take a single lesson; there is no completion gate. Each card lists its own audience and prerequisites. Founders and designers can also take GenAI and Product Eye without being software engineers.
Solve the problem
A coding-interview playbook: understand the question, solve small examples manually, plan the algorithm, challenge your idea, implement, test, and simplify. Follow the seven steps through worked examples.
Who is it for?Software students and candidates preparing for algorithm problems and coding interviews. For people learning how to approach a question and explain their solution during an interview.
Before you startBasic programming: functions, conditionals, loops, lists, and dictionaries. Basic Python is enough to follow the examples.
During the lessonPlan a solution before jumping into implementation; explain why it works and which tests will check it.
Improve the code
Turn a solution idea into code another person can understand. Compare before-and-after examples of naming, functions, layout, and comments, then apply the habits through testing, Git, and code-review exercises.
Who is it for?Students and developers who can already write code and want better readability, testing, and team code-review habits. The focus is making a working solution understandable and changeable by someone else.
Before you startBasic Python. Advanced algorithms and previous code-review experience are not required; the Git exercise explains its setup separately.
During the lessonInspect palindrome, bracket, and grid examples, then try the separate Git exercise and cart-code review in your own environment.
Build with AI
Start with your own introduction and project page. Add a feature, inspect it in the browser, direct a broken-link correction and build a working filter. Use Emre’s real project cases to transfer the method.
Who is it for?Students, founders and developers who want to build and improve their own website with a coding assistant.
Before you startBasic comfort with folders and a browser. One available assistant is enough for hands-on AI work; the supplied files also support an account-free read-through.
During the lessonA personal website you can open and explain, with a clear request-to-correction development process.
See the product through its users’ eyes
Can a visitor find what they need in your portfolio? Does an application actually make their task easier? Study portfolios and familiar products to examine explanations, flows, feedback, and improvement decisions.
Who is it for?Founders, product managers, designers, and developers deciding what to build or improve. Students preparing a portfolio or project can use the same examples to practise evaluating products.
Before you startYou do not need to write code or own a product. Work with the lesson’s portfolio and product examples, then optionally apply the reasoning to your own project.
During the lessonObserve what someone is trying to do, find where they struggle, then repeat the same task to check whether your change helped.
More lectures coming soon...
Get email updates about new blog articles and lessons.