sergiocamachor

Building my personal WordPress site changed the project from a list of course tasks into a public, verifiable record of participation. I created the site as the central place for my WordPress Credits reflections, technical updates, contribution links, and evidence.

Purpose and structure

I decided that the site should be simple and evidence-oriented. The most important page is the WordPress Credits project page, which explains my Astra translation scope, quality controls, results, and community-review status. Separate posts document each required reflection and milestone so a mentor or evaluator can follow the work in chronological order.

What I learned

Working in the block editor helped me understand the difference between a page and a post. A page works well for a stable project overview, while posts are better for dated progress reports and reflections. I also learned that publishing is not the final quality check: I reviewed the public version, corrected formatting that did not render as intended, verified that each link opened the correct official WordPress resource, and kept screenshots of the finished result.

The process also showed why content design matters. Clear headings, short sections, descriptive links, and concrete measurements make technical work easier to evaluate. Instead of saying only that I “worked on translations,” the site records the locale, project, number of suggestions, review request, and the checks used to protect placeholders and HTML.

Reflection

The strongest part of the site is that it connects learning with contribution. It is not only a course requirement; it is a transparent portfolio of open-source work. My next priority is to keep it accurate as reviewers respond, document community participation honestly, and avoid claiming milestones before they actually happen.