
First Steps into Web Development at Full Sail University
This post outlines my experience with Introduction to Web Architecture at Full Sail University. This was the first development themed course in the program and served as my introduction to writing code, understanding web structure, and getting comfortable with the tools that developers use daily. The goal of this retrospective is not to expose internal assignments or curriculum details, but to describe the general themes and how the course helped establish a foundation for later work.
Week 1: Orientation and Web Foundations
My thoughts at the time
During the first week, my main focus was understanding how the web functions at a broad level. I remember feeling both curious and slightly overwhelmed by the number of moving parts involved in a single website, even one that appears simple to a user. The course introduced the basic terminology that I would encounter throughout the program, and I recall spending time connecting these concepts to things I had already experienced online. It felt like the curtain was being lifted on how the technology I rely on every day actually works.
I also remember this week being important for getting comfortable with the program structure at Full Sail. It helped me orient myself to the pace, expectations, and workflows that the degree would follow. That early clarity made the transition smoother as I prepared for hands on work in later weeks.
Retrospective insight
Looking back, this introduction played a major role in giving me a foundation for understanding later technical concepts. Even though the material was rudimentary, it helped me recognize patterns and workflows that appear repeatedly in web development. Learning about the roles in a typical web project also helped me understand how each part connects, and I would later draw on this understanding when collaborating with other students or interpreting documentation.
This week was not about mastering skills but about building context. That context made later challenges feel more approachable and gave me the mental framework to understand how each new skill fits into the larger ecosystem of modern development.
Week 2: HTML Structure and First Lines of Code
My thoughts at the time
This week was my first real step into writing code in a structured environment. Working with HTML was a new experience, but the immediate visual feedback from the browser made it feel accessible. I remember testing small changes and watching how the page responded, which helped cement the idea that front end development is a combination of structure, clarity, and predictable rules. I enjoyed how hands on the week was, and it boosted my confidence early in the program.
I also recall noticing how important it was to maintain clean and readable markup. Even though the examples were simple, it became clear that consistency in structure and naming would matter much more as projects grew larger.
Retrospective insight
In hindsight, learning HTML early and thoroughly was critical. Almost every project I have worked on since then has relied on a strong understanding of page structure and semantics. Even in more advanced courses involving JavaScript frameworks, component based systems, or server rendered content, the foundational HTML knowledge from this week continued to be relevant.
This section of the course helped me develop good habits, especially regarding organization and readability. The early exposure to browser tools and debugging also prepared me for future problem solving when dealing with more complex layouts or unexpected behaviors.
Week 3: CSS and Visual Presentation
My thoughts at the time
Week 3 shifted my focus toward visual design and the mechanics behind styling. CSS felt both creative and technical, which made it an interesting challenge. I found myself experimenting with different colors, layout options, and spacing techniques to see what was possible. I remember being surprised by how powerful CSS was, even at a basic level, and how small adjustments could completely change the appearance of a page.
At the time, I also started to understand how design choices affect the user experience. Having the opportunity to explore and test styles in a live environment made it easy to iterate quickly and learn from trial and error. Layouts, specifically flex boxes, were the bane of my existance this week.
Retrospective insight
Looking back, the introduction to CSS was one of the most valuable parts of the course. The concepts introduced here continued to show up throughout the program, especially in responsive design, component styling, and more advanced layout techniques. Understanding the cascade, specificity, and selectors early on made later lessons significantly easier. I would have appriciated being introduced to the concept of utility classes at this stage since it would have made building sites with HTML significantly easier.
This week also taught me the importance of experimenting and being patient when refining visual styles. Much of front end development involves adjustment and iteration, and this was my first exposure to that workflow. It prepared me for more complex styling tasks, including modular CSS, design systems, and framework specific styling patterns.
Week 4: Synthesis and Creating a One Page Website
My thoughts at the time
The final week brought everything together. Building a simple one page site felt like a meaningful milestone because it was the first time I assembled structure and design into a cohesive outcome. I enjoyed the ability to apply personal branding elements, even in small ways, because it made the project feel like something I owned rather than a generic learning exercise. It was the first time that a project looked and felt like something I had created intentionally.
I also remember becoming more aware of how much planning goes into even a small website. Making choices about layout, content, and structure gave me a better appreciation for the early steps involved in any development workflow.
Retrospective insight
From a long term perspective, this synthesis week helped establish a sense of confidence. It showed me that I could start with foundational concepts and produce something functional and presentable. That is a pattern that repeated throughout the program and in my own projects: learn a concept, combine it with others, and create something small but complete.
This early project also prepared me for later portfolio based work, where the ability to build a branded page with clear content became increasingly important. Even though the result was simple, the process taught me to think through structure, styling, and presentation as a unified workflow, which has continued to benefit me as my skill set has grown.
Closing Thoughts
This course served as an important starting point in my development journey. It introduced the foundational concepts needed to understand web architecture and prepared me for more advanced topics. Although the material was introductory, it provided valuable structure and momentum that helped shape how I approached later challenges.
Credits and Collaboration
A huge thank you to Esther Allin for designing the blog banner art! If you're looking for a professional digital media specialist, Connect with her on LinkedIn!
Share this article
Recommended Reading

Introduction to Development at Full Sail University
A personal retrospective on DEV1001 Introduction to Development 1, the course where I first explored JavaScript, logic structures, and interactive programming. This post walks through each week and reflects on how the material influenced my growth as a developer.

Building Better User Experiences at Full Sail University
A retrospective look at DEV2319 Interfaces and Usability, the second course in my Full Sail learning journey. This post outlines the weekly themes, what I learned, and how the course shaped my understanding of effective user interface design.

First Time Bringing It All Together at Full Sail University
A retrospective look at Project and Portfolio 1: Web Development, the course where earlier skills came together through milestones, iteration, and a working portfolio project.