Current Setup (Mine):

4 disks: In PowerShell run [to check the statuss of disks]

Get-PsDrive -PSProvider FileSystem

• C:\ consist of Home (Windows 11)

• W:\ consist of WSL (Ubuntu + Debian)

  • Confirmation:- [PowerShell]

Target Set Up:

C:\ remains untouched, for future experimental accidents, to avoid any root windows failures

And as there’s 266 GB of space available in W:\ (in my case), we will set up Kali Linux inside W:\ only, along with WSL running in parallel but inside a VM (VirtualBox) for distributed (limited) machine load, as it operates dynamically, doesn’t immediately occupy the complete 60-80 GB required space of Kali Linux on our local machine.

1. Why won't it interfere with WSL

WSL and VirtualBox are like two different apps running on the same computer.

• WSL (Ubuntu/Debian): Lives in a hidden utility VM managed by Windows.

• Kali VM: Lives in a standard folder you created on W:\VMs\.

They use the same "engine" (the Windows Hypervisor Platform), so they can run at the exact same time without fighting for control of your hardware.

2. "Will it stay in that folder?"

Yes. When you extract the Kali image and "Add" it to VirtualBox, everything Kali does - every tool you install, every file you save - stays inside a single large file (usually ending in .vdi) located in W:\VMs\Kali-Linux\.

• No Registry Bloat: It won't scatter files across your Windows C:\ drive.

• Portability: If you ever get a new laptop, you can literally copy that W:\VMs folder to an external drive, plug it into the new PC, and your Kali setup will be exactly where you left it.

3. Potential "Troubles" to Watch For (and how to fix them)

While they won't break each other, they do share your physical resources (RAM and CPU).

• RAM Usage: If you give Kali 8 GB of RAM and Ubuntu is already using 4 GB, and Windows needs 4 GB... your system might slow down.

  • Fix: Since you have a Home version of Windows 11, just make sure you don't run too many heavy apps (like Chrome with 50 tabs) while both Kali and WSL are active.

• Network Conflicts: Sometimes, if you try to run a "Web Server" on Kali and a "Web Server" on WSL using the same port (like port 80), they might clash.

  • Fix: In VirtualBox, use "NAT" mode for networking. This gives Kali its own private internal IP address separate from your Windows/WSL IP.

Conclusion Glimpse:

Set Up:

To ensure VirtualBox and WSL don't fight over your CPU, run this one command in your PowerShell (as Administrator) just to be 100% sure the required Windows feature is active:

dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

o/p:

So opening PowerShell and running as an administrator:

confirm again-

Now-

-> Click here for {Set-Up Steps}

Step-by-Step Execution:

1. Install VirtualBox: Download the .exe and install it. If it asks for a location, just hit "Next" and let it go to C:\ .

2. Redirect the Storage: * Open VirtualBox.

   • Go to File > Preferences > General.

   • Set Default Machine Folder to W:\VMs.

3. Setup Kali:

   • Manually create the folder W:\VMs\Kali-Linux.

   • Extract your downloaded Kali .7z file into that folder.

   • In the VirtualBox app, click Machine > Add and select the .vbox file from that folder on W:.

For File > Preferences > General, you should set it to:

W:\VMs

Why not W:\VMs\Kali-Linux?

The "Default Machine Folder" is the parent folder where VirtualBox will look for all your virtual machines.

When you set it to W:\VMs, VirtualBox will treat that as the main "garage."

If you decide to install another OS later (like a Windows Server or another Linux flavor), VirtualBox will automatically create a new sub-folder for it inside W:\VMs (e.g., W:\VMs\WindowsServer).

If you pointed it directly to W:\VMs\Kali-Linux, things would get messy because VirtualBox would try to put files for other machines inside your Kali folder.

The Final Folder Structure on W:\

Once you are done, your drive will look like this:

• W:\WSL\ (Your existing Ubuntu/Debian)

• W:\VMs\ (The "Global" VM folder)

  • Kali-Linux\ (The specific folder where your Kali .vbox and .vdi files live)

Quick Recap of the "Add" step:

1. Set the Preference to W:\VMs.

2. Click Machine > Add.

3. Open VirtualBox.

4. In the top menu, click Machine > Add (or press Ctrl + A).

5. A file explorer window will open. Navigate to: W:\VMs\Kali-Linux\kali-linux-2026.1-virtualbox-amd64\

6. Look for a file ending in .vbox (it usually has a blue cube icon and might be named kali-linux-2026.1-virtualbox-amd64.vbox).

7. Select that file and click Open.

Result: Kali Linux will now appear in the left-hand sidebar of VirtualBox.

2. Quick Hardware Check (For a CS Student's PC)

Before you hit Start, let's make sure it doesn't lag. Right-click the Kali entry in the list and select Settings:

• System > Processor: Give it 2 or 4 cores. (Since you handle competitive programming and open-source projects, you'll want the speed).

• System > Motherboard: Ensure it has at least 2048 MB (2 GB) of RAM.

• Display > Video Memory: Slide this to the max (128 MB). This makes the desktop environment much smoother.

• General > Advanced: Set Shared Clipboard to Bidirectional. This is a lifesaver for copy-pasting code/commands from Windows.

3. The "Ignition" (First Boot)

1. Click the green Start arrow at the top.

2. A new window will pop up. You’ll see some text scrolling - that’s the Linux kernel waking up.

3. When you reach the login screen, enter the default credentials:

   • Username: kali & Password: kali

Result:

Welcome to Dragon Mode {Kali-Linux}:

How to Access it in future:

1. The Standard Way (GUI)

Whenever you want to start hacking or practicing your CSE labs:

1. Open VirtualBox from your Start Menu.

2. Select Kali-Linux from the list on the left.

3. Click the green Start arrow.

4. To Close it: Don't just "X" out the window like a browser. Inside Kali, click the Power icon (top right) and select Shut Down. This ensures your virtual hard drive on W: doesn't get corrupted.

2. The "Pro" Way (Save State)

If you are in the middle of a project (like a ZenYukti task or a DSA problem) and don't want to close your terminals:

1. Click the "X" on the VirtualBox window i.e) close the VM window.

2. Select "Save the machine state".

3. Result: VirtualBox will freeze Kali exactly where it is and save it to your W: drive. Next time you click Start, it will "wake up" in 2 seconds exactly where you left off.

   

I wanted to make a commit on GitHub with a custom past date - specifically, July 1, 2025, at 12:00 PM - to reflect the actual date the work was completed on my GitHub profile.

Sounds easy, right? I thought so too.
But here's how it actually went 😅

📍Step 1: Creating the Commit Locally

I made a small change in my project and staged it with:

$ echo "Backdated test" >> backdated.txt
$ git add backdated.txt

To commit with a custom timestamp, I used:

$ GIT_AUTHOR_DATE="2025-07-01T12:00:00" GIT_COMMITTER_DATE="2025-07-01T12:00:00" git commit -m "Backdated commit to July 1, 2025"

✅ This created a commit with the exact timestamp I wanted.

❌ Problem 1: bash: commit: command not found

At first, Git Bash wouldn’t recognize the commit command because I broke it across lines incorrectly.

Fix: Run the full commit command on a single line, or use backslashes with proper spacing.

❌ Problem 2: Push Rejected

When I tried to push to GitHub, it said:

error: failed to push some refs to origin

Turns out, Git wouldn't let me push because my local branch and the remote had different histories.

Fix: I pulled the latest changes using this:

$ git pull origin main --allow-unrelated-histories

❌ Problem 3: Vim Nightmare

During that pull, Git launched Vim to ask for a merge message... and I got stuck inside it.

Fix: Exited Vim by pressing:

$ Esc
:wq
Enter

Classic Git developer moment.

[Screenshot- Vim Window in git Bash terminal]

✅ Final Steps

After escaping Vim, I added the file again just to be sure, then committed and pushed:

$ git add backdated.txt

GIT_AUTHOR_DATE="2025-07-01T12:00:00" GIT_COMMITTER_DATE="2025-07-01T12:00:00" git commit -m "Backdated push for July 1, 2025"

git push origin main

This time - everything worked.

🟩 The Green Square Appears

I went to my GitHub profile and hovered over July 1, 2025. Finally saw:

📸 [Screenshot: GitHub contribution graph showing green square on July 1, 2025]

💡 What I Learned (the hard way)

• Backdating commits is possible - but only if you set the environment variables correctly.

• GitHub counts a commit only if:

  • It’s pushed to the default branch (usually main)

  • It uses a verified email linked to your GitHub account

• Git can reject pushes if the histories don’t match - --allow-unrelated-histories is your friend

• Git Bash doesn’t support Ctrl + V (use right-click to paste) (funny…)

• Vim will trap you if you’re not prepared

🧘 Final Thoughts

All of this… just to get one green square on the contribution graph.
Was it a lot?
Yes.
Was it worth it?
Absolutely. 😄

If you’re ever trying to do the same and getting stuck, just remember - I did too.

~Ayush Hardeniya

🚩 Problem

I had just updated the OG image on my personal website. But when I tried sharing the link on LinkedIn, it still showed the previous version of the image.
At first, I thought maybe I made a mistake while uploading...

🖼️ [Screenshot: Old OG image being shown on LinkedIn]

🕵️‍♂️ Investigating via LinkedIn Post Inspector

I headed to LinkedIn Post Inspector to see what was being cached.

Surprisingly, it showed the correct updated OG image - which meant LinkedIn's backend had already crawled and updated the image.

🧩 [Screenshot: Post Inspector showing the updated OG image correctly]

🛠️ Solution: Cache Busting with [ ?v=2 ]

Turns out, LinkedIn aggressively caches images, even after you update them.

🔧 The Fix? A simple query string:

<meta property="og:image" content="https://ayushhardeniya.site/assets/website-pw-1.png?v=2">

Just by adding ?v=2 to the image URL, LinkedIn thinks it's a new resource.
I redeployed my website with the updated tag.

🧪 [Screenshot: Code editor showing updated OG tag with ?v=2]

✅ The Result: Success!

Went back to Post Inspector, ran the URL again, and... bam! The updated OG image finally showed up.

🎉 [Screenshot: LinkedIn showing the updated image after purging]

📚 What I Learned

• LinkedIn aggressively caches OG images (more than expected).

• Adding a simple ?v=2 or any version number is a clean way to bust cache.

• Tools like LinkedIn Post Inspector are gold for debugging social previews.

• Don’t forget to redeploy your site after editing meta tags.

💬 Final Thought

Small fixes like these often seem trivial, but the clarity they bring to your digital identity is huge.
It was a 10-minute fix, but I enjoyed learning something new.

~Ayush Hardeniya

Two days back, I received a mail from Google Search Console saying that two of my website pages weren’t being indexed. The report showed that both pages were stopped from being crawled due to an error.

📸 [Search Console error message]

🔍 Investigating the Issue

After some research, I discovered that this could be happening due to a redirecting issue. To fix it, I added a canonical URL to the <head> section of both HTML pages. This helps tell search engines the correct version of a page, avoiding confusion.

📸 [Canonical tag added in HTML]

🤔 And Then I Found Out About .nojekyll

While researching more about indexing issues on GitHub Pages, I came across something new – a file named .nojekyll.

.nojekyll is a special file you add to your GitHub Pages repo to tell GitHub not to use Jekyll processing.
Why? Because Jekyll, by default, ignores folders that start with an underscore (_), and we don’t want that.

📸 [Explanation of .nojekyll - Reference image]

💻 Making the Change Using Git (From VS Code)

Until now, I always created files manually using the cursor, but this time, I wanted to do it via the Git terminal inside VS Code.

At first, I ran:

add .nojekyll

But got an error because the file didn’t exist yet 😅

📸 [Git error for missing file]

💡 Learning to Create a File via Terminal

Then I Googled it, and finally discovered the correct way to create a new file using the command line:

echo > .nojekyll

And boom! File created 🎉

✅ Staging, Committing, and Pushing Changes

Once the file was there, I staged the change using:

git add .nojekyll

Staging simply tells Git: “Hey! This file exists now. I’m ready to save this change.”

Then committed it:

git commit -m "Added .nojekyll to disable jekyll processing"

And finally pushed to the main branch:

git push origin main

📸 [Staging + Commit + Push process]

🔁 Re-submitted to Search Console

After the file was live, I went back to Google Search Console and resubmitted both pages for indexing.

📸 [Reindexing request]

Still facing the issue? Here is the solution…

Final Cleanup & Indexing Success!

After adding the .nojekyll file and canonical URLs, I noticed that the real issue was with inconsistent URLs - especially those missing the trailing slash (like /about instead of /about/).

🔧 So here’s what I did next:

• ✅ Updated all internal links (e.g., /about → /about/)

• ✅ Fixed URLs in the sitemap.xml to include trailing slashes

• ✅ Set canonical tags with proper URLs (https://ayushhardeniya.site/about/)

• ✅ Re-submitted URLs and sitemap in Google Search Console

📸 [Updated Sitemap.xml with trailing slash]

🎉 Final Result?

Google indexed the pages successfully!
And I learned the importance of consistent URL formatting - especially on static site hosts like GitHub Pages.

📸 [Search Console showing indexed page confirmation]

This was one of those small but super insightful learning days, and I’m glad I documented it here!;

~Ayush Hardeniya

Today’s been super insightful - I finally set up a clean, structured GitHub flow and discovered a few cool things along the way. Here’s everything I explored, fixed, and learned - in a way that might help you too 🚀

🎯 The Goal

I've always worked on the main branch directly. It’s quick, but not the best way to handle updates - especially when you're preparing your repo for open source or GitHub Sponsors.
So today, I changed that. Here's what went down...

🛠️ Step-by-Step Process

1. Created a New Branch (No More Direct-to-Main!)

• Made a small fix and created a new branch: footer-fix

• Committed changes and opened a Pull Request (PR)

• Merged it smoothly into main - ✨ first clean PR flow

✅ Tip: Avoid pushing directly to main. Create a feature/fix branch, commit there, and raise a PR.
This not only keeps your workflow clean but also unlocks GitHub achievement badges!

2. 🏅 Unlocked GitHub Achievements

Because I used a new branch and successfully merged it via PR, I unlocked:

• YOLO - For creating and merging a PR

• Pull Shark - For merging a pull request 🎉

3. 💬 Enabled Discussions for the First Time

Since my repository is now open for contributions, I wanted a place where:

• Contributors could ask questions

• We could talk about ideas, bugs, or plans

So I went to the Discussions tab and:

• Created a General Discussion section

• Started a thread to say hello and invite engagement

🧠 Why This Matters

• Having a clean main branch avoids messy code and builds a habit of professional collaboration

• PR-based workflow helps when multiple contributors are involved

• GitHub Achievements feel rewarding and track your growth

• Discussions open up space for genuine community learning and feedback

🎯 Next Steps

• Set up labels like good first issue

• Invite others to check my repo → raise issues or suggestions

• Stay consistent with this hygiene to grow authentically

• and much more, looking forward to hear from you…

🌐 Want to Contribute?

If you find any bugs or design issues on my site, feel free to contribute!
📍 Click here to visit the repository

This was a tiny shift, but it taught me a lot about open-source etiquette, discipline, and creating space for others to collaborate.

More soon. Until then - keep learning and building!

~ Ayush Hardeniya

🌐 What is a Google Knowledge Panel - and Why It Matters?

Ever searched someone’s name on Google and seen that neat little box on the side with their photo, intro, social links, and more?

That’s called a Knowledge Panel - a structured, verified identity shown by Google/Gemini. It's how public figures, creators, entrepreneurs, or even students start appearing officially in search results.

Image Source: preferral.com

Think of it like your Google ID card on the internet.

So recently, I started working toward creating my own - not through ads or tricks, but through a real, structured and transparent process.

Here’s exactly how I did it step-by-step, using Wikidata and some smart tweaks - so that you can too.

🛠️ Step 1: Understanding the Backend - Wikidata

Google doesn’t just randomly pick stuff from the internet.
It relies on trusted databases like:

• Wikidata.org → for structured facts

• Wikipedia → for public notability (for public figures maybe appeared in articles/ magazines)

• Google Search Console → for your website structure

Out of these, Wikidata is the most accessible for individuals like us, while I have already done the Google Search Console thing.

Here, I created my Wikidata profile from scratch.

🧩 Step 2: Creating My Wikidata Profile

Once you’re logged into Wikidata, you can create an item by giving:

• A Label → Your full name (e.g., Ayush Hardeniya)

• A Description → A short, neutral description (e.g., Indian creattor and student)

  etc.

Once saved, Wikidata gives you a unique Q-ID (e.g., Q123XXX), which acts like your identity.

✍️ Step 3: Adding Statements to Define Myself

These statements are the backbone of your profile.
Click on
[+ add statement]
And-
Think of them as facts about you, like:

• Date of Birth

• Country of Citizenship

• Occupations

• Official Website

• Social Profiles

• Profile Picture

💡 Step 4: Occupation, Website, Social Links - With References

I added my roles like:

• Developer

• Creator

• Student

• Designer

And for each, I added a reference, usually linking to my website or GitHub profile - wherever these roles are actually mentioned.

🖼️ Step 5: Hosting My Profile Image on Wikimedia Commons

For your profile image to show up across platforms, it needs to be hosted publicly.
When I tried to add it by direct public link, hosted from drive, it showed an issue.
So I uploaded mine to “Wikimedia Commons”, which is trusted by Wikidata and Google.
To do it, you need to login on Wikimedia common from same account as that of Wikidata.
And then you can see like below-

After adding all required info, you’ll get the public hosted name of your image, like:

🚧 Bonus: Small Issues I Faced (and Fixed)

While adding statements, I ran into things like:

• “Should not use 'official website' as a source for DOB”
  ➤ Solution: I used just reference URL instead.

• “Social profile username should include start time”
  ➤ So I added a start time like “YYYY-MM-DD”.

• “File name not allowed due to slashes”
  ➤ So I renamed and re-uploaded the image on Wikimedia properly.

• Or maybe not adding language of work or name In the official website’s statement then it shows an issue generated-

  

These small bugs taught me a lot - and showed how detailed Wikidata really is.

🧬 Step 6: Connecting Everything Back to Google

After my Wikidata profile was ready:

1. I submitted my site to Google Search Console

2. I embedded my JSON-LD schema (structured data for Google)

3. I added my Wikidata link to my website's <head> as <link rel="me" href="...">
   The code snippet is-
   [<link rel=”me” href=”https://www.wikidata.org/wiki/QXXXXXXXX" /> ]

4. I plan to publish this blog on Medium too (external mentions help!)

✅ What’s Next?

Now that everything is in place, it’s just about giving Google time to crawl it.

Eventually, if enough trusted sources reference you, and Google finds your structure clean, your Knowledge Panel starts appearing!
I’m excited for mine! 🤪

🙌 Final Thoughts

I’m still a student, still learning - but this little project taught me a lot about how digital identity works behind the scenes.

If you’re a creator, coder, or just curious, I hope this helped you understand how to start owning your name online.

Feel free to reach out if you want help doing the same! :)

Or Or Or
Just Google My Name- (just rtying to improve Google indexing with more searches from different IP addresses)😉

Ayush Hardeniya

Hey everyone!

Sometimes, random tasks come your way that turn out to be pretty cool learning moments. Today, I got assigned a simple but interesting task - to explain some basic Linux commands in a fun way.

Honestly, I didn’t expect to dive this deep, but it gave me a chance to explore Linux command line stuff I’d only heard about before. So here’s a quick recap of what I learned today - nothing too fancy, just the basics that actually make your life easier if you’re starting with Linux.

Why Linux Command Line?

If you’re new to Linux, the command line might look scary - a black screen with lots of text. But once you get the hang of it, it’s like having a superpower. You can do things faster and with way more control than just clicking around.

Today, I learned how some simple commands help you navigate files, create folders, move things around, and find stuff quickly.

Here’s What I Learned (With My Rough Notes)

Basic Commands in a Nutshell

• ls — Lists everything inside a folder. Think of it like scanning your fridge to see what snacks🍕 you have.

• pwd — Shows where you currently are in the folder system. Because honestly, getting lost in folders🗂 is way too easy!

• mkdir — Makes a new folder, giving your files a fresh new home, helping in organising things.

• cd — Moves you between folders, like teleporting around your kitchen🔪 and bedroom🛏️ (quick & familiar).

• rmdir — Deletes empty folders - kind of like cleaning up empty boxes after you’ve moved stuff
  or think of it like nature’s way with male honeybees🐝 after their job is done🤫.

• cp — Copies a file exactly as it is (like making a perfect photocopy of your exam paper - with no weird blurs or ink marks👣).

• mv — Moves or renames files - like tidying up your messy desktop.

• uname — Tells you what system you’re running - your OS introducing itself.

• locate — Finds files anywhere on your system, like having a digital assistant🤖 that knows where everything is.

Why This Matters

Learning these basic commands is a great first step if you want to get comfortable with Linux. It’s not just about using an OS; it’s about controlling your computer more smartly. Plus, it feels awesome when you realise how powerful simple commands can be.

Wrapping Up

So that was my quick Linux crash course, thanks to a random task! I’m attaching my handwritten notes - rough but real. If you’re just starting with Linux, try these commands yourself, and you’ll be surprised how fast you can get things done.

Feel free to ask if you wanna know more or share your tips!

Stay curious and keep learning!
—- Ayush Hardeniya

🌐 Step 1: Hosting GitHub Repository on Custom Domain

Problem:

I had an existing GitHub Page live at ayushHardeniya.github.io but wanted my site to show up at https://ayushhardeniya.site.

Solution:

1. Bought domain from a registrar (mine was BigRock).

2. Went to GitHub Repo > Settings > Pages.

3. Added ayushhardeniya.site in the Custom domain section.

4. Created a CNAME file in the root of my repo with this line:

ayushhardeniya.site

5. In domain DNS settings:

• Added A records pointing to GitHub IPs:

185.199.108.153
185.199.109.153
185.199.110.153
185.199.111.153

• Added a CNAME record pointing to ayushhardeniya.site

6. Waited until Enforce HTTPS became available.

📌 SEO Tip: Google loves HTTPS. Be sure to enable “Enforce HTTPS” in GitHub Pages once available. It might take some hours.

📮 Step 2: Setting Up Zoho Mail for Custom Email

Problem:

Needed to use custom email IDs like connect@ayushhardeniya.site.

Solution:

1. Signed up on Zoho.

2. Added TXT record to verify domain.

3. Set MX records as given by Zoho.

4. Created user mailboxes.

💡 Now I have working professional email addresses under my own domain.

☕ Step 3: Integrating Ko-fi Button & PayPal Payments

Problem:

Ko-fi kept showing errors:

"You cannot currently receive payments on your PayPal account..."

Detailed Fix:

🧩 Fixing PayPal Setup

1. Went to PayPal Business Setup.

2. Filled the form under Account Settings > Business Info:

Business Type: Individual
PAN: <My PAN Number>
Purpose Code: P0805 (Personal use/Design/IT Services)
Industry Type: Services
CC Statement Name: PAYPAL*AYUSH

3. Matched PayPal name EXACTLY with PAN.

4. Revisited KYC page: https://www.paypal.com/in/webapps/mpp/kyc

5. Used desktop browser - mobile submissions were buggy.

6. Cleared cache, logged out and in again.

📞 Optional but helpful: Contact PayPal support if stuck in loop.

🔄 Connecting with Ko-fi

• Back to Ko-fi Settings

• Clicked “Check if you're ready to go”

• Finally showed: ✅ Connected

📄 Step 4: Setting Up Contact Form with Google Sheets Integration

Problem:

My site had a contact form, but it failed to submit or redirected with an error.

Solution:

Replaced it with a working Google Sheet-based form using formsubmit.co or [Google Apps Script]. Here's a sample:

<form action="https://formsubmit.co/your-email@example.com" method="POST">
  <input type="text" name="First Name" required>
  <input type="text" name="Last Name" required>
  <input type="email" name="Email" required>
  <textarea name="Message"></textarea>
  <button type="submit">Submit</button>
</form>

✅ Simple. No backend. Automatically sends to mail or Google Sheet if configured.

📈 Step 5: Pushing to Google Search Console for SEO

1. Domain Verification

• Go to Google Search Console.

• Add new property > Choose domain method.

• Added TXT record in DNS:

TXT @ google-site-verification=xxxxxxxxxxx

• Verified successfully.

2. Sitemap Setup

• Added sitemap URL:

https://ayushhardeniya.site/sitemap.xml

✅ Suggestion- You can generate one using XML Sitemap Generator and add it to your repo.

🔍 Step 6: Optimizing SEO (Meta Tags + Schema + OG)

Page Title:

<title>Ayush Hardeniya - Developer, Creator & Explorer</title>

Meta Description:

<meta name="description" content="Explore the world of Ayush Hardeniya - a passionate developer, reader, and creator sharing blogs, gallery, values, and more." />

Meta Open Graph:

<meta property="og:title" content="Ayush Hardeniya - Official Website">
<meta property="og:description" content="My journey as a developer, reader, explorer & more">
<meta property="og:image" content="https://ayushhardeniya.site/preview.png">

Canonical URL:

<link rel="canonical" href="https://ayushhardeniya.site/" />

Schema.org JSON-LD:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Ayush Hardeniya",
  "url": "https://ayushhardeniya.site",
  "sameAs": [
    "https://github.com/AyushHardeniya",
    "https://twitter.com/ayushhardeniya"
  ],
  "image": "https://ayushhardeniya.site/profile.png",
  "jobTitle": "Developer & Creator"
}
</script>

🧾 Final Thoughts

This blog is a real reflection of what I have faced and sorted accordingly and even a student/freelancer/early-stage creator faces when integrating modern tools together. From DNS misconfigurations to payment integration and SEO indexing - this guide covers it all, from my own experiences.

If you’re going through the same, just follow the steps - or hit me up on Twitter or my contact page.

Author: Ayush Hardeniya
🌐 Website: https://ayushhardeniya.site
☕️ Buy Me A Coffee: https://ko-fi.com/ayushhardeniya

If you liked this blog or found it helpful, do consider sharing it. ❤️