Ashwin Maroli

Results 72 issues of Ashwin Maroli

- This is a 🔨 code refactoring. ## Summary The code in `Jekyll::Regenerator` was a tad hard to wrap one's head around in spite of inline comments. This PR attempts...

refactor

## Problem `Tags::IncludeTag#parse_params` is called from within the `:render` method. to generate the Hash object for `context["include"]` from string markup by using a regex. Consequently, if an include is rendered...

micro-optimization
memory-optimization :zap:

Under certain circumstances. the following methods can result in wastage of resources: https://github.com/jekyll/jekyll/blob/62959527dd870691107739724c23b51ba03828f3/lib/jekyll/entry_filter.rb#L45-L53 For example: ```ruby entry = 'about.md' entry == File.basename(entry) # => true entry.eql? File.basename(entry) # => true...

has-pull-request
up-for-grabs :coffee:
pinned

## Summary Employ `find` filters in documentation site ## Context Requires the following PRs merged to `master` first: - [x] #8171 — Introduces `find` filter. - [x] #8126 and #8201...

optimization :zap:
site

**What problem is this PR intended to solve?** This pull request adds a GitHub Actions Workflow that profiles memory usage from using Nokogiri to parse and serialize HTML content. The...

meta/discussion
topic/memory

## Summary Use source files in branch `demo-site` to build demo site and deploy via GitHub Pages. A separate branch allows *customizing source dir contents* without affecting theme. Though this...

## Key points - Generate a complete CSS file for each skin: - `assets/css/style.css` (default stylesheet / *classic* skin) - `assets/css/dark.css` (*dark* skin) - `assets/css/solarized.css` (*solarized* skin) - `assets/css/solarized-dark.css` (*solarized-dark*...

has-pull-request

The theme (adapted from Minima) will allow developing and testing API endpoints for editing layouts (and in future includes) via the front end. Having a fixture theme instead of using...

Simplifies the implementation logic. @mertkahyaoglu Was there a reason why you originally chose to go with the current implementation instead of using the `'path'` package?

(Contains diff from #344 as well) Front-end support to easily **view** templates within theme-gems via the interface. -- @benbalter I'm proposing a set of front-end code to **demonstrate** my intention...