First of all I have to say it is best practice to learn design patterns! But be sure you don't mix up the meaning of design patterns and architectural patterns.
In computer software a design pattern is a reuseable approach to solving a commonly-occurring software design problem. A design pattern is a template for solving a problem that can be used in many different situations.
Object-oriented design patterns illustrate relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved.
» Why I am explaining this to you?
What I am trying to explain is that it is possible and often the case that third generation programming languages have some of them already implemented and this isn't system or programming lanugage specific. And I am guaranteeing you that you already use some of them. The best example is the observer pattern, which you always use if use bind an event to an object or eventhandler.
An architectural pattern is a widely recognised and reused solution to a recurring design problem in the field of software architectures. The concept of an architectural pattern has a broader scope than the concept of design pattern.
The architectural patterns address various issues in software engineering, such as computer hardware performance limitations, high availability and minimization of a business risk. Some architectural patterns have been implemented within software frameworks like ASP.NET MVC.
» Back to topic
I was wondering what should be considered when applying them to web development rather than software development?
So let wikipedia answer this question for us, referring to arechitectural patterns rather than design patterns with the example of the Model View Controller pattern:
Although originally developed for personal computing, Model View Controller has been widely adopted as an architecture for World Wide Web applications in all major programming languages. Several commercial and noncommercial application frameworks have been created that enforce the pattern. These frameworks vary in their interpretations, mainly in the way that the MVC responsibilities are divided between the client and server.
Because I see you are interested in good practices, take a look on architecture patterns (MVC, MVP, MVVM). The only thing you have to keep in mind here, is that you have to adapt your architecture patterns to the HTTP-mechanics.