WK58: CST462S -  Race Gender & Class in Digital World

Service Learning Final Reflection

My service learning project was a meaningful experience because it gave me a chance to work on a real website for a real organization. During this project, I worked on improving the site layout, navigation menu, mobile and tablet views, footer, page sections, colors, spacing, and general visual style. I also communicated with the site supervisor to understand what changes were needed and to make sure the website matched the organization's goals.

One thing that went well was that I learned how to solve real design problems. Some parts looked simple at first, but they became more complicated when I tested them on different screen sizes. For example, the navigation menu needed a lot of CSS work to look good on desktop, tablet, and mobile. I also learned that small changes, like padding, colors, and alignment, can make a big difference in how professional a website feels.

If I could improve something, I would plan the style guide earlier. It would have helped to have clear settings for sections, rows, fonts, buttons, and spacing before making changes. This would make the design more consistent and save time.

The most impactful part was seeing the website slowly improve through my work. It felt good to know that my service could help the organization present its information more clearly to visitors. The biggest challenge was working with Divi settings and custom CSS because some changes did not work the way I expected. However, this also helped me become more patient and better at troubleshooting.

My advice for future Service Learning students is to communicate often, take notes during meetings, and test everything on different screen sizes. Do not wait until the end to ask questions. Also, keep a record of your work because it helps when writing logs and reflections. Overall, this project helped me build technical skills, communication skills, and more confidence.

Comments

Post a Comment

Popular posts from this blog

Week 20: CST 363 - Introduction to Database Systems

   WK04:  Midpoint Reflections I'm not new to databases and have some practical experience with SQL, but this course gave me the theoretical backbone for concepts I've used pragmatically. I connected everyday tasks - designing tables, choosing keys, writing joins, and skimming plans - to the relational model and formal normalization. Seeing why clustered vs. heap layouts affect access, how B-tree indexes support equality/range predicates, and where optimizers derive their strategies clarified earlier "rules of thumb." Overall, I gained vocabulary and structure to justify design choices. Brief Summary of 5 Things Learned I strengthened the relational model: entities/attributes, candidate vs. primary keys, and why foreign keys enforce meaning across tables. I practiced expressive SQL beyond basics - joins, subqueries, and aggregates - while reading execution plans to understand scans, seeks, and join algorithms. I deepened constraints and referential integrity to preven...
Read more

Week 11: CST 338 - Software Design

  Week 3 Learning Journal – HW 1 Code Review This week was extremely busy. Between multiple programming assignments, studying for quizzes, and finishing up other coursework, I didn't get a single day off - not even Sunday. I worked through the entire weekend just to keep up. One of the last things I tackled was the code review assignment, not because it was difficult, but because it was worth fewer points compared to other assignments. Ironically, despite being worth less than half of another assignment, it took nearly the same amount of time. Reading, testing, and analyzing other students' code takes real focus - especially when you're trying to give meaningful feedback and not just check a box. But I'll be honest: even though it felt like extra work at first, the peer code review assignment turned out to be one of the most helpful parts of the week. Looking through other people's code - seeing what they did right, where they made mistakes, or how they handled logi...
Read more

Week 17: CST 363 - Introduction to Database Systems

 WK01: Starting CST363 – Introduction to Databases This week I officially started a new course: CST363 – Introduction to Database Systems . The class looks like a solid mix of theory and practice. We'll design relational schemas, practice SQL queries, connect to databases programmatically, and even touch on NoSQL concepts like MongoDB. The syllabus makes it clear that this isn't just about running commands - it's about understanding the underlying algorithms, data structures, and principles that power modern database systems. That excites me, since databases are everywhere, from apps to analytics pipelines. Relational Databases vs. Spreadsheets At first glance, relational database tables and spreadsheets look the same - rows and columns full of data. But digging deeper, the differences are critical. Spreadsheets are flexible but mostly unstructured; you can mix data types freely, create ad hoc formulas, and manually tweak things. Databases, on the other hand, enforce stric...
Read more