hugo list expired List all posts already expired Synopsis List all of the posts in your content directory which has already expired. hugo list expired [flags] Options -h, --help help for expired Options inherited from parent commands --clock string set the clock used by Hugo, e.g. --clock 2021-11-06T22:30:00.00+09:00 --config string config file (default is path/config.yaml|json|toml) --configDir string config dir (default "config") --debug debug output -e, --environment string build environment --ignoreVendorPaths string ignores any _vendor for module paths matching the given Glob pattern --log enable Logging --logFile string log File path (if set, logging enabled automatically) --quiet build in quiet mode -s, --source string filesystem path to read files relative from --themesDir string filesystem path to themes directory -v, --verbose verbose output --verboseLog verbose logging SEE ALSO hugo list - Listing out various types of content

hugo list future List all posts dated in the future Synopsis List all of the posts in your content directory which will be posted in the future. hugo list future [flags] Options -h, --help help for future Options inherited from parent commands --clock string set the clock used by Hugo, e.g. --clock 2021-11-06T22:30:00.00+09:00 --config string config file (default is path/config.yaml|json|toml) --configDir string config dir (default "config") --debug debug output -e, --environment string build environment --ignoreVendorPaths string ignores any _vendor for module paths matching the given Glob pattern --log enable Logging --logFile string log File path (if set, logging enabled automatically) --quiet build in quiet mode -s, --source string filesystem path to read files relative from --themesDir string filesystem path to themes directory -v, --verbose verbose output --verboseLog verbose logging SEE ALSO hugo list - Listing out various types of content

hugo mod Various Hugo Modules helpers. Synopsis Various helpers to help manage the modules in your project’s dependency graph. Most operations here requires a Go version installed on your system (>= Go 1.12) and the relevant VCS client (typically Git). This is not needed if you only operate on modules inside /themes or if you have vendored them via “hugo mod vendor”. Note that Hugo will always start out by resolving the components defined in the site configuration, provided by a _vendor directory (if no –ignoreVendorPaths flag provided), Go Modules, or a folder inside the themes directory, in that order....

hugo mod clean Delete the Hugo Module cache for the current project. Synopsis Delete the Hugo Module cache for the current project. Note that after you run this command, all of your dependencies will be re-downloaded next time you run “hugo”. Also note that if you configure a positive maxAge for the “modules” file cache, it will also be cleaned as part of “hugo –gc”. hugo mod clean [flags] Options --all clean entire module cache -h, --help help for clean --pattern string pattern matching module paths to clean (all if not set), e....

hugo mod get Resolves dependencies in your current Hugo Project. Synopsis Resolves dependencies in your current Hugo Project. Some examples: Install the latest version possible for a given module: hugo mod get github.com/gohugoio/testshortcodes Install a specific version: hugo mod get github.com/gohugoio/[email protected] Install the latest versions of all module dependencies: hugo mod get -u hugo mod get -u ./... (recursive) Run “go help get” for more information. All flags available for “go get” is also relevant here....