Skip to content

BlueWallet/Website

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

668 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

BlueWallet Website

Static site for bluewallet.io, built with Jekyll.

Prerequisites

  • Ruby 3.x (tested with Ruby 3.4)
  • Bundler (gem install bundler)

Setup

Clone the repository and install dependencies:

git clone https://github.com/BlueWallet/Website.git
cd Website
bundle install

Always run Jekyll through Bundler so the correct gem versions from Gemfile.lock are used:

bundle exec jekyll <command>

Development

Start a local development server. Jekyll defaults to the development environment, which skips production-only features such as Google Analytics.

bundle exec jekyll serve

The site is served at http://localhost:4000. Jekyll watches for file changes and rebuilds automatically.

Useful options:

# Preview unpublished drafts from _drafts/
bundle exec jekyll serve --drafts

# Bind to all interfaces (useful for testing on other devices on your network)
bundle exec jekyll serve --host 0.0.0.0

# Use a different port
bundle exec jekyll serve --port 4001

Note: Changes to _config.yml are not picked up while the server is running. Restart jekyll serve after editing the config.

LiveReload

Jekyll has built-in LiveReload support. It injects a small script into pages and refreshes the browser when the site is rebuilt.

bundle exec jekyll serve --livereload

By default:

  • The site is served on port 4000
  • LiveReload listens on port 35729

If the LiveReload port is already in use, pick another one:

bundle exec jekyll serve --livereload --livereload-port 35730

No browser extension is required — Jekyll handles reloads automatically.

Production

Build the static site for deployment. Set JEKYLL_ENV=production so production-only logic is enabled (for example, analytics and Disqus comments when configured in _config.yml).

JEKYLL_ENV=production bundle exec jekyll build

Output is written to the _site/ directory. Serve it locally to verify the production build:

JEKYLL_ENV=production bundle exec jekyll build
bundle exec jekyll serve --skip-initial-build --no-watch

Or use any static file server:

cd _site && python3 -m http.server 4000

Project layout

Path Description
_config.yml Site configuration
_posts/ Blog posts
_docs/ Documentation pages
_data/ YAML data files (navigation, features, etc.)
_includes/ Reusable HTML/Liquid partials
_layouts/ Page layouts
_sass/ SCSS stylesheets
assets/ CSS, JavaScript, and images
_site/ Generated output (do not edit)

Troubleshooting

Could not find jekyll-... or gem errors

Run bundle install in the project root.

About

No description, website, or topics provided.

Resources

License

Stars

20 stars

Watchers

4 watching

Forks

Releases

No releases published

Packages

 
 
 

Contributors