Skip to content

betahero-org/site

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

26 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

🦸 BetaHero

BetaHero Lighthouse Score

BetaHero is based of a free and open-source template using Astro + Tailwind CSS.

Features


BetaHero Theme Screenshot


Table of Contents

Getting started

Project structure

/
β”œβ”€β”€ 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.

πŸ§‘β€πŸš€ Seasoned astronaut? Delete this file. 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

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

  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 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


Roadmap

  • Project:
    • (DONE) Reduce the complexity in the components folder and simplify the other folders to make it very easy to use.
    • Create simple and clear strategy to get template updates
    • Move specific configurations to a specialized file
    • Fix some bugs with prettier
    • Make the use of images clean and intuitive
  • SEO:
    • (DONE) Add support to easily manage SEO meta-tags (title, description, canonical, social sharing, ...)
  • Blog:
    • (DONE) Support to Fast and SEO friendly blog
    • (DONE) Add support for categories and tags.
    • Improve blog design
    • Create component or utilities for latest posts
    • Create component or utilities for related posts
    • Add more shortcodes or embed functions to posts in Markdown: (eg video, tweet...)
  • More widgets:
    • Add more Tailwind components useful for most scenarios (Features, Contact, Call to Actions, Content, FAQs ...)
    • Create external library or place with useful Tailwind components
  • More Examples: Add commonly used example pages (Ex: About, Terms, Services...)
  • Documentation: Create detailed documentation with best practices and redesign tips

Frequently Asked Questions

  • Why?

Contributing

If you have any idea, suggestions or find any bugs, feel free to open a discussion, 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.

License

BetaHero is licensed under MIT β€” see the LICENSE file for details.