Skip to content

Latest commit

 

History

History
219 lines (161 loc) · 8.32 KB

README.md

File metadata and controls

219 lines (161 loc) · 8.32 KB

M Haidar Hanif Website based on 🚀 Astro + Tailwind CSS = AstroWind

This is the personal website of M Haidar Hanif made using Astro and Tailwind CSS.

Based on the AstroWind template, a free and open-source template to make your website using Astro + Tailwind CSS. Ready to start a new project and design taking into account best practices. Originally from onwidget/astrowind

AstroWind Lighthouse Score

License Maintained Contributions Welcome Known Vulnerabilities Prettier ESLint

Features

  • ✅ Integration with Tailwind CSS (@astrojs/tailwind) supporting Dark mode.
  • Production-ready scores in Lighthouse and PageSpeed Insights reports.
  • Fast and SEO friendly blog with automatic RSS feed (@astrojs/rss), MDX support, Categories & Tags, Social Share buttons, ...
  • Image optimization (@astrojs/images) and Font optimization.
  • ✅ Generation of project sitemap based on your routes (@astrojs/sitemap).
  • Open Graph tags for social media sharing.
  • Analytics built-in Google Analytics, and Splitbee integration.
Table of Contents

Live

📌 mhaidarhanif.com


Getting started

Project structure

Inside the template, you'll see the following folders and files:

/
├── data/
|   └── blog/
|       ├── post-slug-1.md
|       ├── post-slug-2.mdx
|       └── ...
├── public/
│   ├── robots.txt
│   └── favicon.ico
├── src/
│   ├── assets/
│   │   ├── images/
|   |   └── styles/
|   |       └── base.css
│   ├── components/
│   │   ├── atoms/
│   │   ├── blog/
│   │   ├── core/
|   |   └── widgets/
|   |       ├── Header.astro
|   |       ├── Footer.astro
|   |       └── ...
│   ├── layouts/
│   |   |── BaseLayout.astro
│   |   └── ...
│   ├── pages/
│   |   ├── [...blog]/
|   |   |   ├── [...page].astro
|   |   |   └── [slug].astro
│   |   ├── [...categories]/
|   |   |   └── [category]/
|   |   |       └── [...page].astro
│   |   ├── [...tags]/
|   |   |   └── [tag]/
|   |   |       └── [...page].astro
│   |   ├── index.astro
|   |   ├── 404.astro
|   |   └-- rss.xml.js
│   ├── utils/
│   └── config.mjs
├── package.json
└── ...

Astro looks for .astro or .md files in the src/pages/ directory. Each page is exposed as a route based on its file name.

There's nothing special about src/components/, but that's where we like to put any Astro/React/Vue/Svelte/Preact components.

Any static assets, like images, can be placed in the public/ directory if they do not require any transformation or in the assets/ directory if they are imported directly.

Edit on CodeSandbox

🧑‍🚀 Seasoned astronaut? configure config.mjs and contents. Have fun!


Commands

All commands are run from the root of the project, from a terminal:

Command Action
npm install Installs dependencies
npm run dev Starts local dev server at localhost:3000
npm run build Build your production site to ./dist/
npm run preview Preview your build locally, before deploying
npm run format Format codes with Prettier
npm run lint:eslint Run ESLint
npm run astro ... Run CLI commands like astro add, astro preview

Configuration

Basic configuration file: ./src/config.mjs

export const SITE = {
  name: 'Example',

  origin: 'https://example.com',
  basePathname: '/', // Change this if you need to deploy to Github Pages, for example
  trailingSlash: false, // Generate permalinks with or without "/" at the end

  title: 'Example - This is the homepage title of Example',
  description: 'This is the homepage description of Example',

  googleAnalyticsId: false, // or "G-XXXXXXXXXX",
  googleSiteVerificationId: false, // or some value,
};

export const BLOG = {
  disabled: false,
  postsPerPage: 4,

  blog: {
    disabled: false,
    pathname: 'blog', // blog main path, you can change this to "articles" (/articles)
  },

  post: {
    disabled: false,
    pathname: '', // empty for /some-post, value for /pathname/some-post
  },

  category: {
    disabled: false,
    pathname: 'category', // set empty to change from /category/some-category to /some-category
  },

  tag: {
    disabled: false,
    pathname: 'tag', // set empty to change from /tag/some-tag to /some-tag
  },
};

Deploy

Deploy to production (manual)

You can create an optimized production build with:

npm run build

Now, your website is ready to be deployed. All generated files are located in dist folder, which you can deploy the folder to any hosting service you prefer.

Deploy to Netlify

Clone this repository on your own GitHub account and deploy it to Netlify:

Netlify Deploy button

Deploy to Vercel

Clone this repository on your own GitHub account and deploy to Vercel:

Deploy with Vercel


Contributing

If you have any idea, suggestions, or find any bugs, feel free to open a discussion, or an issue, or create a pull request. That would be very useful for all of us and we would be happy to listen and take action.

Acknowledgments

Initially, the template was made by onWidget](https://onwidget.com) and maintained by a community of contributors.

Notes

Keep limax at ^v2.1.0 because v3.0.0 has breaking changes.

License

Licensed under the Unlicense license — see the LICENSE file for details.