This library generates string url path by getting entities and ids.
JSON schema generator based on draft-v4.
Determine if a function is a native generator function.
A function that returns the normally hidden `GeneratorFunction` constructor
An implementation of the WHATWG URL Standard's URL API and parsing machinery
utils for webpack loaders
A function that returns the normally hidden `AsyncGeneratorFunction` constructor
WebGL-accelerated signed distance field generation for 2D paths
RSS feed generator. Add RSS feeds to any project. Supports enclosures and GeoRSS.
Generate JSON schema from your Typescript sources
Index generator for Hexo.
Turns an AST into code.
Utility functions for converting to and from URLs that encode query string data into URL paths
A tiny (118 bytes), secure URL-friendly unique string ID generator
Helper function to remap async functions to generators
An implementation of the WHATWG URL Standard's URL API and parsing machinery, without unicode support
Check whether a value is a generator or generator function
Turn async generator functions into ES2015 generators
Helper function to remap async functions to generators
Turn async functions into ES2015 generators
Super fast, memoized `req.url` parser
Check whether a string is a URL.
The core `url` packaged standalone for use with Browserify.
A npm package wrapper for OpenAPI Generator (https://github.com/OpenAPITools/openapi-generator), generates which API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)
A more powerful path and url generator for Rails
Generate url and get filename from attachment path
SubdomainRoutes add subdomain conditions to the Rails routing system. Routes may be restricted to one or many specified subdomains. An URL will be recognised only if the host subdomain matches the subdomain specified in the route. Route generation is also enhanced, so that the subdomain of a generated URL (or path) will be changed if the requested route has a different subdomain to that of the current request. Model-based subdomain routes can also be defined.
SubdomainRoutes add subdomain conditions to the Rails routing system. Routes may be restricted to one or many specified subdomains. An URL will be recognised only if the host subdomain matches the subdomain specified in the route. Route generation is also enhanced, so that the subdomain of a generated URL (or path) will be changed if the requested route has a different subdomain to that of the current request. Model-based subdomain routes can also be defined.
SubdomainRoutes add subdomain conditions to the Rails routing system. Routes may be restricted to one or many specified subdomains. An URL will be recognised only if the host subdomain matches the subdomain specified in the route. Route generation is also enhanced, so that the subdomain of a generated URL (or path) will be changed if the requested route has a different subdomain to that of the current request. Model-based subdomain routes can also be defined.
SubdomainRoutes add subdomain conditions to the Rails routing system. Routes may be restricted to one or many specified subdomains. An URL will be recognised only if the host subdomain matches the subdomain specified in the route. Route generation is also enhanced, so that the subdomain of a generated URL (or path) will be changed if the requested route has a different subdomain to that of the current request. Model-based subdomain routes can also be defined.
SubdomainRoutes add subdomain conditions to the Rails routing system. Routes may be restricted to one or many specified subdomains. An URL will be recognised only if the host subdomain matches the subdomain specified in the route. Route generation is also enhanced, so that the subdomain of a generated URL (or path) will be changed if the requested route has a different subdomain to that of the current request. Model-based subdomain routes can also be defined.
SubdomainRoutes add subdomain conditions to the Rails routing system. Routes may be restricted to one or many specified subdomains. An URL will be recognised only if the host subdomain matches the subdomain specified in the route. Route generation is also enhanced, so that the subdomain of a generated URL (or path) will be changed if the requested route has a different subdomain to that of the current request. Model-based subdomain routes can also be defined.
SubdomainRoutes add subdomain conditions to the Rails routing system. Routes may be restricted to one or many specified subdomains. An URL will be recognised only if the host subdomain matches the subdomain specified in the route. Route generation is also enhanced, so that the subdomain of a generated URL (or path) will be changed if the requested route has a different subdomain to that of the current request. Model-based subdomain routes can also be defined.
Google_Maps_Embed is a versatile Ruby gem designed to simplify the generation of Google Maps URLs for embedding static and dynamic maps in web applications. Designed with Rails in mind. Key features include: - Flexible Configuration: Define map parameters dynamically, including center coordinates, zoom levels, markers, and paths. - API Integration: Seamlessly integrates with Google Maps API to generate reliable map URLs. - URL Signing: Optionally signs URLs for secure API usage when configured with a secret key. - Customization: Easily customize map dimensions, marker styles, and path configurations. - Simplified Usage: Streamlined methods for constructing map URLs, ensuring compatibility and consistency. Ideal for web developers seeking efficient map integration solutions.
Generates Xcode .xcassets ColorSet JSON files from color palette URLs. Extracts hex color codes embedded in URLs from palette tools such as: - Huemint (https://huemint.com) - RealtimeColors (https://realtimecolors.com) - Coolors (https://coolors.co) Any URL that encodes hex codes in its path or query string is supported. Dark mode variants are automatically calculated by inverting the HSL lightness of each light color — no manual dark palette needed. The generated Colors.xcassets folder can be dragged and dropped directly into Xcode's Assets catalog to use the colors in Swift/SwiftUI projects. Usage: colorset_generator "https://huemint.com/brand-2/#palette=2a3031-fafdfc-a19985" colorset_generator "https://coolors.co/c4f1be-a2c3a4-869d96-525b76-201e50" --output MyPalette.xcassets colorset_generator "https://www.realtimecolors.com/?colors=14140f-f8f8f6-9a9e79-aec4bd-8ea7ad" --no-dark
# 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.