A simple command-line utility that creates a new post for an Eleventy site from a template.
Doing this manually is not hard, all you have to to do is copy an earlier post or an empty post you keep lying around to the right location, rename the file and replace the post content with new stuff.
This package does all that, and a little more, automatically and faster. Here's what it does:
- Ensures that its running in an Eleventy site project
- Reads all of the post files in the project to build a list of all of the Categories in use in the site
- Prompts you to provide the title for the post
- Prompts you to select a single category for the post (you can add other categories when you edit the generated post file)
- Creates a new post file using a template file you provide, copies it to the correct
postsfolder, and, finally, sets the post file's title and category.
If you're generating dummy documents to test some aspect of a new site, you can optionally populate each generated post file with Bacon Ipsum content generated using the Bacon Ipsum JSON API.
Open a terminal window or command prompt and execute the following command:
npm install -g eleventy-new-postThis installs the package globally and adds a 11ty-np command you can use from anywhere on your system.
If you prefer not to install it, you can execute it at any time in a terminal window or command prompt using:
npx eleventy-new-postThe package uses a simple, self-generated configuration file to keep you from having to remember and use a variety of weird command-line options.
Open a terminal window or command prompt in an Eleventy project's root folder and execute the following command:
11ty-npThe package will check to see that you're running the command in an Eleventy project then look for its configuration file 11ty-np.json. If it doesn't find the file, you'll be prompted to create it as shown below:
┌───────────────────┐
│ │
│ 11ty New Post │
│ │
└───────────────────┘
by John M. Wargo (https://johnwargo.com)
Configuration file '11ty-np.json' not found
Rather than using a bunch of command-line arguments, this tool uses a configuration file instead.
In the next step, the utility will automatically create the configuration file for you.
Once it completes, you can edit the configuration file to change the default values and execute the command again.
? Create configuration file? » (Y/n)
Press the n key on the keyboard if you don't want to generate the configuration file, otherwise press y to generate the file:
┌───────────────────┐
│ │
│ 11ty New Post │
│ │
└───────────────────┘
by John M. Wargo (https://johnwargo.com)
Configuration file '11ty-np.json' not found
Rather than using a bunch of command-line arguments, this tool uses a configuration file instead.
In the next step, the utility will automatically create the configuration file for you.
Once it completes, you can edit the configuration file to change the default values and execute the command again.
√ Create configuration file? ... yes
Writing configuration file 11ty-np.json
Output file written successfully
Edit the configuration with the correct values for this project then execute the command again.
When the utility completes the process, you'll have a new file in the project's root called 11ty-np.json with the following or similar contents (depending on your project's folder setup):
{
"editorCmd": "code",
"openAfterCreate": true,
"paragraphCount": 4,
"postsFolder": "src/posts",
"promptCategory": true,
"promptTargetFolder": false,
"templateFile": "11ty-np.md",
"useYear": true
}Edit the configuration settings as needed for your project.
Now, lets talk about the configuration options (in alphabetical order)...
With openAfterCreate set to true, the utility opens the newly created post file after saving it using the editor executable provided here. The value defaults to code (Visual Studio Code).
Populate this setting using the executable name or executable file path required to launch the editor. You can configure Visual Studio Code so it's on the system path, so all you need is code to launch it. For a different editor, you may have to configure the full file path to the editor executable.
When true, the utility automatically opens the newly created post using editor specified in editorCmd.
The -p command-line flag (described below) enables generation of dummy content for new posts. As an example, if you were simply using the command to populate a site with a set of posts for testing or demonstration purposes.
The paragraphCount configuration option controls how many paragraphs of content to request from the Bacon Ipsum JSON API and add to a new post. The value specified here must be between 1 and 100.
Since the utility scans all existing post files to build the list of categories, it must know where to look for the content files to use to build that list. It also must know where to store the files it generates. The postsFolder configuration option describes that location.
When generating the configuration file, the command scans the local project for possible post folder options, so you may see that the configuration option is already populated with the correct value for your particular project. If not, populate this configuration variable with the correct folder location in the project; it should contain a relative path pointing to the project's posts folder.
Note: If the target posts folder doesn't exist, the utility will create it automatically.
Some Eleventy sites don't use Categories to, you know, categorize posts. Use the promptCategory configuration setting (set promptCategory to true) to enable prompting for the selection of one or more Categories during post creation. When promptCategory is false the utility skips building the category list and prompting the user to select categories.
When you're working in an Eleventy project that stores post content in multiple folders (for example posts and news), enable the promptTargetFolder option (set promptTargetFolder to true in the configuration file) to have the utility prompt you to select the target folder when creating a new post.
When you enable this option, the utility scans the folder location defined in postsFolder for sub-folders then displays the source folder plus the subfolder list when creating a new post as shown in the example below:
┌───────────────────┐
│ │
│ 11ty New Post │
│ │
└───────────────────┘
by John M. Wargo (https://johnwargo.com)
√ Enter a title for the post: ... Bonfire Planning
√ Select one or more categories from the list below: » People
? Select the target folder for the new post: » - Use arrow-keys. Return to submit.
> src\posts
src\posts\vacations
src\posts\purchases
src\posts\cars
After you select a folder name from the list, the utility writes the new post to the selected folder.
Note: The configuration settings useYear and promptTargetFolder are mutually exclusive; you can't enable both in your configuration.
The utility applies a template to every post it creates; the utility copies the content of the template file into every post it creates. The utility supports configuring a single template used for every post or allows you to configure multiple templates and select them at runtime.
Use the promptTemplateFile configuration option to control whether the utility uses a single template (the templateFile option described in the following section) or prompts the user to select a template during new post creation.
With promptTemplateFile set to false, the utility uses the templateFile configuration option as the template file name.
With promptTemplateFile set to true, the utility reads the project folder looking for all files in the folder matching the file name 11ty-np*.* (ignoring the 11ty-np.json file because that's the config file and can't be used as a template). If then displays the list of template files for you to select the correct template you want used for the current post.
Here's an example of what it looks like in the terminal:
┌───────────────────┐
│ │
│ 11ty New Post │
│ │
└───────────────────┘
by John M. Wargo (https://johnwargo.com)
√ Enter a title for the post: ... My New Post
√ Select one or more categories from the list below: » Dogs
√ Select the target folder for the new post: » src\posts\2023
? Select the template file to use: » - Use arrow-keys. Return to submit.
11ty-np-announce.md
> 11ty-np-news.md
11ty-np.md
For this example, I copied the default template 11ty-np.md and created two copies 11ty-np-announce.md and 11ty-np-news.md and modified the template content in each. With this in place, I can create new posts for my site selecting the default content for each post based on one of the three templates in the project folder. The announce version of the template may have special frontmatter settings or boilerplate content for product announcements while the news item may include disclaimer content in the post.
The utility applies a template to every post it creates; the utility copies the content of the template file into every post it creates. The utility supports configuring a single template used for every post or allows you to configure multiple templates and select them at runtime.
Use the templateFile configuration option to configure the template file you want used when generating posts and promptTemplateFile is false.
To configure the default template used for every post, create a template file using one of your existing posts as a starting point. Save the file to the Eleventy project's root folder and give it an appropriate file name (the default configuration uses 11ty-np.md). Remove everything from the template file except the content you want automatically copied into each post. Here's an example template markdown file called 11ty-np.md:
---
layout: default
title:
date:
categories:
---Eleventy has specific rules about how it uses a post file's date front matter property as described in Content Dates. For the purpose of this particular setting, it's important to note that Eleventy only cares about the post date, not any timestamp associated with it. So if you put a timestamp in the front matter's date property that looks like this: 2024-04-05T21:15:35.719Z, when you render the property on a page, Eleventy will only show the date portion.
If you want to display a post creation time, you must add an additional property to the post's front matter.
When you enable timeStamp in the configuration file ("timeStamp: true), the utility automatically adds the timestamp property to the post's front matter and sets it to the current date/time. You can then use that property to display both the post creation date and time in a site (and even include it in a RSS feed).
---
layout: default
title: Added TimeStamp
description:
date: 2024-04-05
categories:
- People
timestamp: 2024-04-05T21:21:09.591Z
---Some Eleventy site projects store posts in a separate folder per year, some don't - it's a developer choice and this tool has to be flexible. This configuration property controls where the program stores generated post files.
- Set
useYearset to false to store new posts in thepostsFolderfolder. Using the example configuration file above, this means new post files save to./src/posts. - Set
useYearset to true to store new posts in thepostsFolderfolder plus an additional subfolder for the year. Using the example configuration file above, this means new post files save to./src/posts/2024.
Note: If the target posts folder doesn't exist, the utility will create it automatically.
Note: The configuration settings useYear and promptTargetFolder are mutually exclusive; you can't enable both in your configuration.
With the configuration file properly configured for your Eleventy project, open a terminal window or command prompt in the project folder and execute the following command:
11ty-npThe program prompts you for the name for the article/post as shown below:
┌───────────────────┐
│ │
│ 11ty New Post │
│ │
└───────────────────┘
by John M. Wargo (https://johnwargo.com)
? Enter a title for the post: »
Enter A title for the post and press Enter; the program writes the title to the template file's front matter and uses the title for the file name.
If this is the first post in your site, at this point it will generate the post file and store it in the project using the location settings in the configuration file.
┌───────────────────┐
│ │
│ 11ty New Post │
│ │
└───────────────────┘
by John M. Wargo (https://johnwargo.com)
√ Enter a title for the post: ... Sample Post
Writing content to D:\dev\node\11ty-new-post\src\posts\2023\sample-post.md
When you generate a new post in a populated site, the program will prompt you to select a Category from the list of categories used in your site as shown below:
┌───────────────────┐
│ │
│ 11ty New Post │
│ │
└───────────────────┘
by John M. Wargo (https://johnwargo.com)
√ Enter a title for the post: ... Sample Post
? Select one or more categories from the list: »
Instructions:
↑/↓: Highlight option
←/→/[space]: Toggle selection
a: Toggle all
enter/return: Complete answer
( ) Cats
( ) Dogs
( ) Turtles
( ) Uncategorized
Use the arrow keys as directed in the prompt to select one or more categories from the list, then press Enter to continue. Press Enter without making a selection to assign no categories to the post. At this point, the program will write the generated post file to the project and close.
┌───────────────────┐
│ │
│ 11ty New Post │
│ │
└───────────────────┘
by John M. Wargo (https://johnwargo.com)
√ Enter a title for the post: ... Sample Post
√ Select one or more categories from the list: » Cats, Dogs
Writing content to D:\dev\node\11ty-new-post\src\posts\2023\sample-post.md
If you enable the -p (populate) flag as shown below:
11ty-np -pThe program will do all those things described above, then use the Bacon Ipsum JSON API to retrieve content paragraphs for the post and append them to the end of the template file.
┌───────────────────┐
│ │
│ 11ty New Post │
│ │
└───────────────────┘
by John M. Wargo (https://johnwargo.com)
√ Enter a title for the post: ... Populated Post
√ Select one or more categories from the list: » Dogs
Getting bacon ipsum text (this may take a few seconds)...
Writing content to D:\dev\node\11ty-new-post\src\posts\2023\populated-post.md
Here's the content of a populated post file. Notice how the title, date, and categories front matter properties are automatically populated for you.
---
layout: default
title: Populated Post
date: 2023-04-18
categories:
- Dogs
---
Bacon ipsum dolor amet rump beef ribs venison salami bacon jerky. Ribeye
leberkas cupim t-bone, salami rump prosciutto strip steak. Ham tenderloin
porchetta andouille buffalo. Pig kielbasa bacon beef ribs cupim pastrami
pork belly filet mignon. Landjaeger cupim rump capicola. Bacon landjaeger
strip steak, tail venison sirloin swine meatball turducken flank jowl
prosciutto.
Pig sirloin biltong hamburger venison drumstick, shank chislic ribeye
turducken jowl. Ham tongue bacon short ribs ham hock shankle turducken
fatback pork chop. Capicola bacon burgdoggen picanha, rump short ribs
short loin shankle filet mignon chuck kevin tongue porchetta. Filet
mignon jerky ham hock beef ribs short loin brisket shank turducken ball tip.
Cow boudin alcatra spare ribs. T-bone hamburger ground round picanha short
ribs, strip steak venison tri-tip pork sausage brisket swine kevin bresaola
capicola. Chicken pig ham hock biltong beef tongue. Pastrami drumstick
pig turducken ball tip tenderloin. Kevin hamburger jerky, pig meatloaf
picanha filet mignon turducken beef shank sirloin buffalo cow chislic turkey.
Corned beef chuck bacon shank shankle short ribs short loin tri-tip bresaola
salami.
Bresaola shank pig pork chop ham doner. Rump picanha chicken meatball, shank
pig pork. Tail picanha venison pork chop ham jowl kielbasa t-bone. Pork
loin ham beef ribs ribeye, tenderloin spare ribs shankle fatback short loin
tail andouille sirloin filet mignon. Salami prosciutto alcatra swine jerky
chicken short loin. Sausage landjaeger short ribs porchetta venison cow
doner filet mignon short loin.If something's not working like you expect or you think there's something wrong, you can enable Debug Mode using the -d flag on the command line:
11ty-np -dWith this enabled, the program writes more detailed information to the console as it executes.
Use GitHub Issues to get help with this utility.
Pull Requests gladly accepted, but only with complete documentation of what the change is, why you made it, and why you think its important to have in the utility.
If this code helps you, please consider buying me a coffee.
