Add 2025 Curtin Capstone End of Year Blog Post

[caydnn]

Adds the end of semester blog post for semester 2 of the 2025 Curtin Capstone collaboration with BeeWare.
The post will highlight the teams contributions from the second half of the year-long internship.

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

[caydnn]

Hi @freakboy3742, we've added all our parts to the blog post. Feel free to check it out when you get a chance 😄

[freakboy3742]

Looks good team! I've lefts some review notes inline. Most of them relate to either rendering issues, or the sort of "narrative voice" we use in blog posts. If you need any clarification on any of these points, just ask.

If I've made a point in one section (e.g., about spaces between paragraphs), that note will generally apply to every other section as well (where appropriate), so just because I didn't specifically comment on your section of the document, doesn't mean you're in the clear :-)

[freakboy3742]

You could add a link to the first semester blog post here.

[freakboy3742]

Great content; but could be broken into a couple of paragraphs (as with Kavi - make sure there's a blank line between paragraphs)

[mEp3ii2]

Updated

[freakboy3742]

As with Jaeden - this should be paragraphs not bullet points.

[freakboy3742]

There's two options here:

1. An introductory paragraph with a tight list of bullet points; or
2. A couple of paragraphs describing in high level terms with links to relevant outstanding PRs/designs.

[caydnn]

I've added an opening paragraph at line 98. Did you need me to expand on it? :)

[freakboy3742]

So - that introductory paragraph is kind of half way to what I intended.

My main issue is that the bullet point list is inconsistent with the rest of the text. After a lot of narrative descriptions, we've got a set of bullet points reads a bit like a first draft for the paragraphs that should be here. If the future work was as simple as "here are the four issues that need to be resolved" or "here are the 3 PRs that need to be completed", then a bullet list might be appropriate. Here we have a combination of short descriptions and links; some of which is duplicating content that are covered in more detail in the handover reports.

Rather than duplicate the handover reports, this further work section should be giving a really high level summary of the work to be done, and then referring to those handover reports for more details.

(Also some of the todo items have already been done :-) )

[caydnn]

Alrighty that makes sense, I'll see if I can get the team to update their sections for this. A few of us have exams tomorrow but we should be able to change this soon.

For the Insertion system changes, would you like a similar approach but with a link to the remaining issue ticket instead of a handover report?

[freakboy3742]

Alrighty that makes sense, I'll see if I can get the team to update their sections for this. A few of us have exams tomorrow but we should be able to change this soon.

No problems - your exams should absolutely take priority. If we can get this wrapped up by the end of the week, that would be ideal.

For the Insertion system changes, would you like a similar approach but with a link to the remaining issue ticket instead of a handover report?

I'm not sure I follow you're referring to here. My original comment was intended as highlighting an issue with the entire "future work" section, not a flag on this specific bullet point. If there's a handover report, link to it, with maybe a very brief summary of the nature of the outstanding work; if the future work is just a ticket or two, link to those.

To avoid content duplication, it might also be appropriate to remove references to the handover reports in the sections above, and consolidate them down in this future work section.

[caydnn]

Hi @freakboy3742, we have addressed your comments and believe this is ready to go.
Feel free to check it out again :)

[freakboy3742]

Body content all looks good (with a couple of minor suggestions inline).

The only thing outstanding is the outstanding note on the last section.

[caydnn]

Hi @freakboy3742
Apologies for the delay, the future work section has been updated now :)

[github-actions]

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

https://beeware-org--pr705-lektor-lgzwbvz0.web.app

_{(expires Tue, 11 Nov 2025 00:12:25 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: b0da44bc067e7d9a4255c77cb2c5fce572218cec}