How to make a blog for a school project without losing marks to the setup

Turn the assignment into a build sheet

Read the brief once for the subject and a second time for the deliverable. Highlight every item the teacher can check: number of posts or pages, required sources, word range, images, reflection, bibliography, deadline, presentation and whether the result must be public. Do not assume that "blog" means weekly posts. Some teachers use the word for any small website.

Convert those requirements into a build sheet with five columns:

1. Requirement: the exact instruction from the brief.
2. Location: the page or post where the requirement will appear.
3. Evidence: the source, example, data or observation that supports it.
4. Status: not started, drafted, checked or complete.
5. Proof: the final URL, screenshot or file that shows the requirement is present.

This small table separates content work from website work. If the brief asks for three arguments and a reflection, you can see whether each has a home before you spend time on colours. It also gives a group project an ownership map: one person can research while another prepares images, but every requirement still has a named destination.

Ask the teacher about any ambiguity before building. The expensive questions are practical: May the site be public? Must classmates comment? Can you use a personal account? Is a free subdomain acceptable? Does the school require a particular citation style? What exactly must be submitted - a link, a PDF, screenshots or all three?

Decide who may see it before choosing the platform

Visibility is a design decision, not a switch to think about at the end. A public site can be opened without an account and is easy to share, but it can also appear in search results and be copied. A restricted site protects the work from general access, but every intended viewer needs permission and sometimes an account on the same service.

Google Sites lets a publisher choose whether a published site is restricted or public. A restricted site can be shared with named people or groups. Google also warns that its request to keep a public site out of search engines does not guarantee exclusion, so that option should not be treated as privacy. Google Sites: publish and share your site

WordPress.com provides a private mode in which only the owner and approved, logged-in users can view the site. That can work for a class, but it changes the handoff: the teacher needs a WordPress.com account and an invitation, and private mode disables some features. Test those conditions before committing to the platform. WordPress.com: make your website private

Use a school-managed account and an approved service when either is available. Do not publish student surnames, personal email addresses, timetables, home locations or identifiable photographs simply because the software allows it. If students under 13 are involved in the United States, platform and school responsibilities may fall under COPPA. The Federal Trade Commission says a school may consent on a parent's behalf only within the educational context and urges schools to assess an operator's collection, use, security, retention and deletion practices. That is a reason to follow the school's approved-tool process, not to improvise a legal decision as a student. FTC: COPPA questions for schools and service operators

Choose the simplest tool that satisfies the brief

A school blog rarely needs paid hosting, a custom domain or a self-hosted content system. Those choices add billing, updates, backups and account recovery without improving the argument. Start with the tool the school already supports. If there is no prescribed tool, compare only the functions the assignment needs.

Google Sites suits a small page-based project when the work uses Google documents, slides or videos and does not require a traditional stream of dated posts. Google's current workflow is direct: select a template, add content and publish. WordPress.com is closer to a conventional blog, with posts, categories and a public or private site, but it gives you more settings to manage. A learning platform or school content system may be better than either when the teacher already receives work there. Google Sites: create, add content and publish

Use a four-question selection rule: Can the teacher open it? Can every group member edit it? Can it show the required media and citations? Can you preserve a copy after grading? If one answer is no, solve that problem before you draft inside the platform. A familiar tool with fewer visual options is usually safer than an impressive tool that creates a new access problem.

Create a blank test site and share it with one classmate or another account. Open the published address in a private browser window. This ten-minute test reveals whether you shared the editor instead of the published site, whether the viewer needs a login and whether school account restrictions block people outside the organisation.

Build a site map that follows the argument

A blog is not automatically a pile of posts. Give readers a route through the assignment. For most projects, four page types are enough: a home page that states the question and conclusion, one or more evidence pages, a reflection or method page, and a sources page. If the brief requires dated posts, use the home page to explain the sequence and link to them in the intended order.

Name pages after the questions they answer. "Results" is clearer than "Part Three". "Why the river changed course" is clearer than "More information". Keep the navigation short enough to understand at a glance, and put supporting material below the main argument rather than giving every note its own menu item.

Draft a one-sentence job for each page. The home page or opening post should tell the reader what the project investigates, what you found and where the strongest evidence appears. Each evidence page should make one main claim. The reflection should explain choices, limitations and what changed during the work rather than retelling the conclusion.

For group work, decide whether the voice is collective or attributed. A consistent collective voice usually reads better than switching between unnamed writers. If individual contributions must be assessed, identify responsibility in a contributor note or project log rather than inserting names into random paragraphs.

Write the evidence before decorating the page

The fastest drafting unit is claim, evidence and explanation. State the point in the first sentence. Add the source, observation, quotation, example or data that supports it. Then explain how that evidence answers the project question. A link by itself is not an explanation, and a long quotation does not show that you understood it.

Keep citations while you draft. Record the author or organisation, title, date, URL and the date you accessed a changeable web page. Follow the teacher's required citation style even when the blog also links directly to the source. Hyperlinks make checking easier, but they do not automatically satisfy an academic referencing requirement.

Separate your words from source material. Use quotation marks for exact language and cite it beside the quotation. Paraphrase by explaining the idea from your understanding, not by replacing a few words in the original sentence. If a chart, photograph or diagram came from elsewhere, the page needs a source and a rights basis as well as a factual citation.

Write page titles, summaries and introductions after the core evidence is stable. This prevents a clever headline from promising more than the project proves. It also reduces repetition: the title identifies the subject, the opening states the finding and the sections show the evidence.

Make the site readable and accessible

Use one clear page title and headings that describe the sections beneath them. The W3C Web Accessibility Initiative explains that logical headings help people with cognitive and learning disabilities, screen-reader users and keyboard users navigate more efficiently. Headings should describe structure, not serve as a shortcut for making text large. W3C WAI: page structure tutorial

Keep paragraphs focused, but do not force every sentence onto a new line. Use lists for genuine steps or comparisons. Write link text that names the destination, such as "Google Sites sharing instructions", instead of repeating "click here". Check colour contrast and avoid placing essential text inside an image.

Add alternative text that communicates the purpose of meaningful images. A chart needs the important conclusion in nearby text, not only a label such as "chart". A purely decorative divider can have empty alternative text so assistive technology can skip it. W3C's image guidance emphasises that the correct text depends on the image's function in context. W3C WAI: resources on alternative text

Preview the site at phone width even if the teacher will grade it on a laptop. Look for cropped tables, unreadable captions, horizontal scrolling and navigation that hides required pages. A responsive theme cannot fix an image containing tiny text or a table with too many columns.

Use images you are allowed to publish

The cleanest options are photographs and diagrams you created, school-provided media with clear permission, public-domain material and Creative Commons works whose terms you can follow. "Found on Google" is not a licence. The search result points to a page; it does not grant reuse rights.

For a Creative Commons image, record the title, creator, source URL, licence and any changes. Creative Commons recommends linking to the specific licence deed and making the licensing statement easy to find. Some licences require adaptations to use the same licence, and licences with a non-commercial restriction may not fit every use. Creative Commons: license your work and mark it clearly Creative Commons: considerations for licensors and licensees

A compact credit can sit in the caption: "Photo title, by Creator, source, CC BY 4.0, cropped." Keep a separate source log while building so you do not have to reconstruct credits the night before submission. If the image shows classmates, school work or a private location, permission and school policy still matter even when you took the photograph yourself.

Test the published version, not only the editor

Finish content at least one work session before the deadline. Publish, then run a viewer test in this order:

1. Open the exact submitted URL in a private browser window while logged out.
2. Follow every navigation item and every link required by the assignment.
3. Check that images load, captions and credits are visible, and videos have a usable fallback link.
4. Read the site on a phone-sized screen and at 200 percent browser zoom.
5. Ask another person to find the project question, strongest evidence, conclusion and sources without guidance.
6. Check spelling, citation completeness and the marking brief one final time.

Do not change sharing settings after this test without testing again. Copy the viewer URL from the published page, not the editing dashboard. If the site is restricted, share it with the teacher's exact account and ask the platform to send an invitation only if that matches the teacher's instructions.

Preserve a submission copy. Export or print the important pages to PDF, save the final text and source list, and take screenshots of the navigation and sharing setting. Dynamic websites can change, accounts can be disabled and embedded media can disappear. The saved copy shows what you submitted and makes later portfolio use possible.

The final package should contain the published URL, the project title, the student or group identifier permitted by the school, any password or access instruction the teacher requested, and the backup file. A blog succeeds as a school project when the argument is easy to follow, the evidence is easy to verify and the teacher can open the same version you tested.