Fixes #11: Incorrect Create Date and Filename on each Code Block

Author: PrathameshDhande22

Diff for: content/Decorator Pattern.md

@@ -2,6 +2,7 @@
 title: Decorator Pattern
 tags:
   - structural
+created: 2025-02-22
 ---
 ## Definition
 
@@ -80,16 +81,14 @@ _Design of the Coffee Shop_
 ---
 ## Coding Decorator Pattern
 
-```java title:Coffee.java
-// Coffee.java
+```java title="Coffee.java"
 interface Coffee {
 	public String getDescription();
 	public int getCost();
 }
 ```
 The `Coffee` interface acts as an **abstraction layer** between the **variety of coffee types**. By implementing this interface, you can create **as many coffee varieties** as needed.
-```java title:PlainCoffee.java
-// PlainCoffee.java
+```java title="PlainCoffee.java"
 class PlainCoffee implements Coffee {
 
 	@Override
@@ -104,8 +103,7 @@ class PlainCoffee implements Coffee {
 }
 ```
 
-```java title:CappuccinoCoffee.java
-// CappuccinoCoffee
+```java title="CappuccinoCoffee.java"
 class CappuccinoCoffee implements Coffee {
 	@Override
 	public String getDescription() {
@@ -119,8 +117,7 @@ class CappuccinoCoffee implements Coffee {
 }
 ```
 In the code example above, the `Coffee` interface is implemented by both the **PlainCoffee** and **CappuccinoCoffee** concrete classes. For each coffee type, we override the methods and assign the **specific cost** for each coffee.
-```java title:CoffeeDecorator.java
-// CoffeeDecorator.java
+```java title="CoffeeDecorator.java"
 abstract class CoffeeDecorator implements Coffee {
 	protected Coffee _coffee;
 
@@ -140,8 +137,7 @@ abstract class CoffeeDecorator implements Coffee {
 }
 ```
 The `CoffeeDecorator` class is the **decorator class** that implements the `Coffee` interface to **decorate different varieties of coffee**. In our case, the **CoffeeDecorator** acts as an **add-on** (e.g., milk, sugar) that can be added to the customer's coffee if requested.
-```java title:MilkDecorator.java
-// MilkDecorator.java
+```java title="MilkDecorator.java"
 class MilkDecorator extends CoffeeDecorator {
 	public MilkDecorator(Coffee decoratedcoffee) {
 		super(decoratedcoffee);
@@ -159,8 +155,7 @@ class MilkDecorator extends CoffeeDecorator {
 }
 ```
 
-```java title:SugarDecorator.java
-// SugarDecorator.java
+```java title="SugarDecorator.java"
 class SugarDecorator extends CoffeeDecorator {
 	public SugarDecorator(Coffee decoratedCoffee) {
 		super(decoratedCoffee);
@@ -178,7 +173,7 @@ class SugarDecorator extends CoffeeDecorator {
 }
 ```
 When creating coffee objects, you can **layer decorators** as needed. For example, a **Cappuccino** with **milk and sugar** is created by **wrapping the decorators** around the base coffee object.
-```java title:DecoratorPattern.java
+```java title="DecoratorPattern.java"
 public class DecoratorPattern {
 	public static void main(String[] args) {
 		Coffee plaincoffee = new PlainCoffee();
@@ -199,7 +194,7 @@ Cappuccino + Milk + Sugar Cost=35
 ```
 ---
 ## Complete Code In Java
-```java title:Decorator.java
+```java title="Decorator.java"
 package decorator;
 
 // Coffee.java
@@ -307,7 +302,7 @@ public class DecoratorPattern {
 
 The Java I/O library is a textbook example of the Decorator Pattern. The base classes such as `InputStream` and `OutputStream` are extended by concrete classes (like `FileInputStream`) and then wrapped by decorator classes that add additional functionality at runtime.
 
-```java title:StreamInput.java
+```java title="StreamInput.java"
 // Base stream reading from a file
 InputStream fileStream = new FileInputStream("data.txt");
 

Diff for: content/Observer Pattern.md

@@ -2,6 +2,7 @@
 title: Observer Pattern
 tags:
   - behavioral
+created: 2025-02-18
 ---
 ## Definition
 
@@ -86,7 +87,7 @@ The Design will look like the Above.
 
 ---
 ### Code in Java
-```java title:Observerpattern.java
+```java title="Observerpattern.java"
 // These is the Subject
 interface Subject {
 	public void registerObserver(Observer o);
@@ -229,7 +230,7 @@ The **Observer Pattern** is commonly used in many libraries and frameworks. For
 This class allows you to **add or remove observers** easily. You can also create multiple listeners by implementing the `ActionListener` interface.
 
 Below is an example demonstrating this.
-```java title:SwingApp.java
+```java title="SwingApp.java"
 package observer;
 
 import java.awt.Rectangle;

Diff for: content/Strategy Pattern.md

@@ -2,8 +2,8 @@
 title: Strategy Pattern
 tags:
   - behavioral
+created: 2025-02-11
 ---
-
 ## Definition
 
 It defines a family of algorithms, encapsulates each one, and makes them interchangeable. The **Strategy Pattern** allows algorithms to vary independently from the clients that use them.
@@ -284,7 +284,7 @@ classDiagram
 
 The `Comparator` interface acts as the Strategy Pattern. By inheriting this interface, you can create your custom comparator, which allows you to sort collections.
 
-```java title:Person.java
+```java title="Person.java"
 class NameComparator implements Comparator<Person> {
     public int compare(Person p1, Person p2) {
         return p1.name.compareTo(p2.name);

Diff for: content/index.md

@@ -1,5 +1,6 @@
 ---
 title: Design Patterns
+created: 2025-02-07
 ---
 ### What is Design Pattern ?
 
@@ -30,7 +31,7 @@ In software design, **coupling** refers to the degree of dependency between tw
 
 **Example :** 
 Consider a `MessageService` class that sends messages via Email, SMS, or other techniques. The implementation might look like the following code:
-```java title:MessageService.java
+```java title="MessageService.java"
 class MessageService {
 
 	public static void sendMessage(string message){
@@ -48,7 +49,7 @@ These Approach Follows **Dependency Inversion Principle** which is again the par
 
 **Example:**
 In the earlier example, the `MessageService` class was heavily dependent on `EmailClient`. In such cases, if you need to create another service, it becomes inefficient. We can avoid this dependency by passing the `ProviderClient` interface as a parameter to the `sendMessage` method. Then, we implement the `ProviderClient` interface for various provider services.
-```java title:MessageService.java
+```java title="MessageService.java"
 
 // Interface to be implemented by various provider services
 interface ProviderClient {

Diff for: quartz.layout.ts

@@ -21,15 +21,17 @@ export const sharedPageComponents: SharedLayout = {
     })
   ],
   head: Component.Head(),
-  header: [Component.MobileOnly(
-    Component.Drawer({
-      links: {
-        Blogs: "./blogs",
-        Github: "https://github.com/PrathameshDhande22/Java-Tutorial",
-        "About Me": "https://github.com/PrathameshDhande22"
-      }
-    })
-  )],
+  header: [
+    Component.MobileOnly(
+      Component.Drawer({
+        links: {
+          Blogs: "./blogs",
+          Github: "https://github.com/PrathameshDhande22/Java-Tutorial",
+          "About Me": "https://github.com/PrathameshDhande22"
+        }
+      })
+    )
+  ],
   afterBody: [
     Component.RecentNotes({
       limit: 5,
@@ -66,7 +68,6 @@ export const defaultContentPageLayout: PageLayout = {
   right: [
     Component.TableOfContents(),
     Component.Backlinks(),
-
   ]
 }