npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

hexo-custom-fields

v1.1.1

Published

A Hexo plugin that allows the default Markdown source files to be used as custom fields

Downloads

3

Readme

hexo-custom-fields

npm
A Hexo plugin that allows the default Markdown source files to be used as custom fields

Motive

I am a front-end developer originally. I used many CMS throughout the years and with many of them it was common to have custom fields. Which is a functionality that allows the coder to be able to include just snippets of text or an image path into a template. I wanted to try a static-site generator more deeply and chose Hexo which I like so far. It is just missing an easy way to include custom fields directly from your Markdown source files. That's exactly what this plugin is trying to solve!

Installation

NPM

npm install --save hexo-custom-fields

Yarn

yarn add hexo-custom-fields

Usage

Insert the custom_field() tag in your templates (in this example with EJS):

<%- custom_field('posts|pages, 'title_in_the_front_matter', 'name_of_the_field') %>

Argument | Description -------- | ----------- first | 'posts' or 'pages' - this determines if the directory 'source/_posts' or 'source/' is used for that field - Read more about the location in the Hexo documentation second | 'title' value in the front-matter of the Markdown source file - Read more about the front-matter in the Hexo documentation third | the actual name of the chosen field. Below this table there is another one with possible options.

One can use the default fields provided by Hexo. The most important options for the third argument are these:

Option | Description -------- | ----------- 'any_field_name' | You can use an unlimited amount of custom fields in the front-matter of a source file. You can directly get these with their respective names - string 'content' | The rendered content of the Markdown file (so everything after the front-matter) - HTML 'title' | The given title - string 'date' | The date and time the source file was created at - formatted date (with timezone) 'updated' | The date and time the source file was last updated at - formatted date (with timezone) 'permalink' | The full URL of the post or page - URL '_id' | The unique ID Hexo assigned to the source file - string

Example:

Display the custom field 'birthday' from the Markdown source file 'front-page' in the 'source' directory (which makes it a 'page') Read more about the location in the Hexo documentation

<%- custom_field('pages', 'front-page', 'birthday') %>

License

MIT