Add 2025 Curtin Capstone End of Semester Blog Post

[kavi2du]

Adds the end-of-semester blog post for Semester 1 of the 2025 Curtin Capstone collaboration with BeeWare. The post reflects on the team's progress, learnings, and contributions during the first half of this year-long internship.

It provides an overview of the project’s current status and sets the stage for continued work in Semester 2.

PR Checklist:

• [ x ] All new features have been tested
• [ x ] All new features have been documented
• [ x ] I have read the CONTRIBUTING.md file
• [ x ] I will abide by the code of conduct

[freakboy3742]

A couple of initial high level comments inline; but this is headed in the right direction. It's about the right length, and covers the required content in the right level of detail (with references to deeper sources). I'll wait until all the TBDs and other bits are fleshed out before I give a deep review of those parts.

Two

1. We've now landed a big refactor of translations - that won't impact on this PR, but it would be worth merging the lektor branch (not main or master) into this branch so that you're getting the current rendering behavior
2. A lot of the problems with this PR would be picked up if you ran lektor serve - the basic Markdown problems (like indentation issues) stand out when you do.

[johnzhou721]

Sorry for finding a few trivial things.

[freakboy3742]

Team: Let me know when this PR is ready for review.

[mEp3ii2]

I think it's ready for a review now, I've updated me and @JMah007 sections since we have got our issue up now

[github-actions]

Visit the preview URL for this PR (updated for commit fdc851a):

https://beeware-org--pr639-curtin-capstone-blog-cf0rz75u.web.app

_{(expires Fri, 20 Jun 2025 01:28:43 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: b0da44bc067e7d9a4255c77cb2c5fce572218cec}

[freakboy3742]

Looks good; a couple of minor edits and suggestions inline, but otherwise, this looks good.

One thing to check in the next review pass is brand identity. It's "BeeWare" and "PyScript", not "Beeware" and "Pyscript"; we need to make sure these are used correctly and consistently.

[freakboy3742]

I've picked up one really minor markup improvement; but other than that, this all looks great.

@kavi2du @Stringer90 @caydnn @JMah007 @mEp3ii2 @vt37: Can I get a formal signoff from all team members that you're happy to put your name to this? A 👍 on this post is sufficient. Once I've got those sign-offs, I'll put the post live.