/plebnet-dev-website

plebnet.dev website

Primary LanguageAstroMIT LicenseMIT

Plebnet.dev website

Build the Future with Plebnet.dev on bitcoin and lightning.

IMPORTANT BUILD NOTE: As of 31 OCT 2023

Use Node version - lts/hydrogen -> v18.16.1

 npm install astro
 npm install

This is the main website.

Screenshot 2023-06-18 at 9 37 38 PM

🚀 AstroWind

AstroWind Lighthouse Score

🌟 Most starred & forked Astro theme in 2022. 🌟

AstroWind is a free and open-source template to make your website using Astro 2.0 + Tailwind CSS. Ready to start a new project and designed taking into account web best practices.

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, ...
  • Image optimization (astro:assets) 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.


onWidget License Maintained Contributions Welcome Known Vulnerabilities Stars Forks


Table of Contents

Demo

📌 https://astrowind.vercel.app/


Getting started

AstroWind tries to give you quick access to creating a website using Astro 2.0 + Tailwind CSS. It's a free theme focuses on simplicity, good practices and high performance.

Very little vanilla javascript is used only to provide basic functionality so that each developer decides which framework (React, Vue, Svelte, Solid JS...) to use and how to approach their goals..

Project structure

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

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

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 AstroWind on CodeSandbox

🧑‍🚀 Seasoned astronaut? Delete this file. Update 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

const CONFIG = {
  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', // Default seo title
  description: 'This is the homepage description of Example', // Default seo description
  defaultImage: 'image.jpg', // Default seo image

  defaultTheme: 'system', // Values: "system" | "light" | "dark" | "light:only" | "dark:only"

  language: 'en', // Default language
  textDirection: 'ltr', // Default html text direction

  dateFormatter: new Intl.DateTimeFormat('en', {
    // Date format
    year: 'numeric',
    month: 'short',
    day: 'numeric',
    timeZone: 'UTC',
  }),

  googleAnalyticsId: false, // Or "G-XXXXXXXXXX",
  googleSiteVerificationId: false, // Or some value,

  blog: {
    disabled: false,
    postsPerPage: 4,

    post: {
      permalink: '/%slug%', // variables: %slug%, %year%, %month%, %day%, %hour%, %minute%, %second%, %category%
      noindex: false,
      disabled: false,
    },

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

    category: {
      pathname: 'category', // Category main path /category/some-category
      noindex: true,
      disabled: false,
    },

    tag: {
      pathname: 'tag', // Tag main path /tag/some-tag
      noindex: true,
      disabled: false,
    },
  },
};

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 at dist folder, which you can deploy the folder to any hosting service you prefer.

Deploy to Netlify

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

Netlify Deploy button

Deploy to Vercel

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

Deploy with Vercel


Frequently Asked Questions

  • Why?

Related projects

  • TailNext - Free template using Next.js 13 and Tailwind CSS with the new App Router.
  • Qwind - Free template to make your website using Qwik + Tailwind CSS.

Contributing

If you have any ideas, suggestions, or find any bugs, feel free to open a discussion, an issue, or create a pull request. Your contributions are valuable, and we're eager to hear from you and take action.

Blog Posts

Creating a blog post is an excellent way to contribute and complete your first pull request! Here is some helpful information to get you started:

Blog posts are written in Markdown and are automatically converted to HTML. To get started, add a new file your_blog_post_name.md inside the directory src/content/post. Don't forget to include metadata in the frontmatter fields at the beginning of your post. Select a single category to represent the main topic or theme of the post.

---
publishDate: 2023-10-07T20:22:00-05:00
title: Your Blog Post Title
author: Your Name
description: Short description on blog
image: ../../images/your_image_here.png
categories:
  - Conferences
tags:
  - TABConf
---

Categories

Choose one category that best represents the main topic of your blog post:

  • Community: For discussions, events, and networking within the Bitcoin community.
  • Conferences: Content related to Bitcoin conferences, meetups, and event experiences.
  • Development: Technical aspects and updates related to Bitcoin development.
  • Education: General educational content covering foundational knowledge about Bitcoin.
  • Guides and Tutorials: Step-by-step guides, how-tos, and practical tutorials for hands-on learning.
  • News and Updates: Posts providing news, updates, and current events in Bitcoin.
  • Opinion: Personal viewpoints and insightful commentary on various aspects of the Bitcoin ecosystem.
  • Projects and Applications: Real-world projects and applications built on Bitcoin.
  • Research and Insights: Discussion of research findings and insights in the Bitcoin space.

Tags (Choose 1-3)

Please choose 1-3 tags that best describe the specific topics or keywords covered in your blog post. Tags help readers find relevant content. Remember to keep tags concise and avoid redundancy.

Acknowledgements

Initially created by onWidget and maintained by a community of contributors.

License

AstroWind is licensed under the MIT license — see the LICENSE file for details.