A simple tool to automate front-end development
`@cowave-front/cli` 是 Cowave Front CLI 的命令行入口，发布后提供 `cowave-front` 命令。
easy front cli
a front cli
egova front cli tool
gdh-basic-front-cli
szzt-front-cli
`@cowave-front/core` 是 Cowave Front CLI 的公共基础包，提供多个包共享的轻量工具。
No description provided.
@hybrbase-front/cli auto generate templates or components
No description provided.
Extract YAML front matter from a string
No description provided.
To create a new project, run `front-cli <project-name> <template-name> `
hf-front-cli core
front cli tool
y-front-cli前端工程搭建脚手架工具
prints a dependency graph in dot format for your typescript or react project
## install
Parse front-matter from a string or file. Fast, reliable and easy to use. Parses YAML front matter by default, but also has support for YAML, JSON, TOML or Coffee Front-Matter, with options to set custom delimiters. Used by metalsmith, assemble, verb and
Plugin to process front matter container for markdown-it markdown parser
> TODO: description
xiaobaozi front client tools
zova cli-set-front
A simple front-end CLI to SSHFS
Provides a way inject vcr in front of any thor cli task
By default, if a page or a post in a Jekyll site has a syntax error in the front matter, Jekyll logs an error, does not render anything for the given page, and continues. The result is a site without any content for the page with the syntax error. This can be confusing for people who build sites without looking at the CLI, such as those of us whose sites build in a CI. In these cases, we may wish for our build to fail if there are front matter syntax errors. [This PR](https://github.com/jekyll/jekyll/pull/5832/files) seeks to add a config option for that, but in the meantime this plugin exists to fill the gap. This plugin may also be used to add the option to sites using an older version of Jekyll.
TKXXS provides a very simple and very easy to use GUI (graphical user interface) for Ruby; It gives you a persistent output window and popping up (modal) dialogs for input; For a screenshot, see: <tt>https://github.com/Axel2/tkxxs/blob/master/images/screenshot.png</tt>; I tested it on Windows, only; Got user report, that it works on Ubuntu, too. TKXXS shall: * improve the usability of little applications, which otherwise would use a command line interface (CLI); for example by a GUI-file chooser * give a simple GUI front-end for apps, which take parameters on the command line. (stdout can easily be redirected to the OutputWindow.) * take only little more effort and coding time over programming a CLI; * be able to easily upgrade existing CLI-applications; * be comfortable in use (e.g. provide incremental search, tool-tip-help, ...); * be easy to install. Drawbacks: * I'v tested it only on Windows, but got user report, that it works on Ubuntu, too.l * For sure some more drawbacks which I'm not aware of now. TKXXS uses TK (easy to install).
# Otto AsciiDoc-powered static site generator with Jekyll-style conventions: layouts, includes, data files, posts, drafts, permalinks, and custom collections. ## Install ```sh gem install ottogen ``` Requires Ruby 3.0 or newer. ## Quickstart ```sh mkdir mysite && cd mysite otto init otto build otto serve open http://127.0.0.1:8778/ ``` For a longer walkthrough including AsciiDoc syntax, see [GUIDE.md](GUIDE.md). ## Commands | Command | Description | |---|---| | `otto init [DIR]` | Scaffold a new site (current dir if omitted) | | `otto build` | Render the site to `_build/` | | `otto build --drafts` | Include posts from `_drafts/` | | `otto watch` | Rebuild on file change | | `otto serve` | Serve `_build/` on port 8778 | | `otto generate PAGE` | Create a new page in `pages/` | | `otto post "Title"` | Create a new dated post in `_posts/` | | `otto clean` | Delete `_build/` | | `otto doctor` | Sanity-check project layout | ## Project layout ``` my-site/ ├── .otto # marker ├── config.yml # site config ├── assets/ # copied verbatim into _build/ ├── pages/ # AsciiDoc pages, output mirrors path ├── _layouts/ # ERB layouts (.html.erb) ├── _includes/ # ERB partials ├── _data/ # YAML/JSON files exposed as site.data.* ├── _posts/ # YYYY-MM-DD-slug.adoc └── _drafts/ # undated drafts (excluded by default) ``` ## Configuration (`config.yml`) ```yaml title: My Otto Site description: Things I write url: https://example.com baseurl: "" permalink: /:year/:month/:day/:slug/ collections: recipes: output: true ``` `permalink` accepts these tokens: `:year`, `:month`, `:day`, `:slug`, `:title`. Templates ending in `/` produce pretty URLs (`<path>/index.html`). ## Pages and posts Both support YAML front matter: ```adoc --- layout: default title: Hello tags: [ruby, cli] --- = Hello Welcome to {site_title}. This page is at {page_url}. ``` Pages live under `pages/`; posts under `_posts/` with `YYYY-MM-DD-slug.adoc` names. Layouts wrap rendered AsciiDoc; partials in `_includes/` are pulled in via `<%= partial 'header.html' %>`. ## License MIT
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.