| Age | Commit message (Collapse) | Author |
|---|
|
Added a flag to allow turning on sourcemap in ESBuild. The current support
can only support inline or true as value for sourcemap. This is because
the way ESBuild is invoked it doesn't have a separate output path
to write the mapfile external to the asset pipeline. Add disable for "" and "0".
Add test script and make sure mage check passes.
Fixes #7607
|
|
Closes #7517
|
|
fixes a bug in list item parsing
|
|
|
|
See #732
|
|
Fixes #7321
|
|
Fixes #7442
Fixes #7443
|
|
- Add support for image links (i.e. link with image as description)
- Kinda breaking: Wrap headlines and headline+content in containers as emacs
Org mode does. Could break people's styles - I don't expect it, but who knows
what counts as sane when it comes to css.
Before:
```
<h2 id="headline-1">FOO</h2>
foo bar
```
After:
```
<div id="outline-container-headline-1" class="outline-2">
<h2 id="headline-1">FOO</h2>
<div id="outline-text-headline-1" class="outline-text-2">
foo bar
</div>
</div>
```
|
|
- Add support for #+MACRO
- fix a bug with #+LINK (edge case, should never happen anyways :TM:)
- Make title export optional (add export option)
- Remove cosmetic whitespace added by go-org (for easier visual
diffing) inside p tags (<p>\nfoo\n</p> => <p>foo</p>)
(should make `white-space: pre` on p look more in line with expectations)
- implement table separators via multiple tbodies (the html spec is ok with
that)
|
|
See https://github.com/yuin/goldmark/releases/tag/v1.1.31
See #7289
|
|
The new version of chroma includes a fix to not emit styles for tokens
without a class (which is invalid).
Fixes #7207
|
|
Fixes #6699
|
|
Fixes #7231
|
|
Recreate #7027
Fixes #6596
|
|
- inline source blocks and exports
- result blocks and source block :exports parameter
- fix: html escaping in example blocks
- #+LINK based links
|
|
Chroma was updated to include a new function to output all CSS
classes without skipping any considered redundant with the current
style.
This will modify the `hugo gen chromastyles` command to use this new
function by default, which avoids potential problems if the style is
later modified.
Also includes requires the updated Chroma (v0.7.2).
Resolves #7167
|
|
Fixes #7113
|
|
The main use case for this is to use with resources.PostProcess and resources.PostCSS with purgecss.
You would normally set it up to extract keywords from your templates, doing it from the full /public takes forever for bigger sites.
Doing the template thing misses dynamically created class names etc., and it's hard/impossible to set up in when using themes.
You can enable this in your site config:
```toml
[build]
writeStats = true
```
It will then write a `hugo_stats.json` file to the project root as part of the build.
If you're only using this for the production build, you should consider putting it below `config/production`.
You can then set it up with PostCSS like this:
```js
const purgecss = require('@fullhuman/postcss-purgecss')({
content: [ './hugo_stats.json' ],
defaultExtractor: (content) => {
let els = JSON.parse(content).htmlElements;
return els.tags.concat(els.classes, els.ids);
}
});
module.exports = {
plugins: [
require('tailwindcss'),
require('autoprefixer'),
...(process.env.HUGO_ENVIRONMENT === 'production' ? [ purgecss ] : [])
]
};
```
Fixes #6999
|
|
|
|
Fixes #6985
|
|
This fixes a bug, so there's a small change to tests.
|
|
Fixes #7039
|
|
See #6901
|
|
Fixes #6885
|
|
Fixes #6862
|
|
v1.1.22 has a fix for issue where links with newline in the title
don't get parsed correctly. Reference:
https://github.com/yuin/goldmark/issues/94
Signed-off-by: Bhavin Gandhi <bhavin7392@gmail.com>
|
|
Closes #6791
|
|
This more or less completes the simplification of the template handling code in Hugo started in v0.62.
The main motivation was to fix a long lasting issue about a crash in HTML content files without front matter.
But this commit also comes with a big functional improvement.
As we now have moved the base template evaluation to the build stage we now use the same lookup rules for `baseof` as for `list` etc. type of templates.
This means that in this simple example you can have a `baseof` template for the `blog` section without having to duplicate the others:
```
layouts
├── _default
│ ├── baseof.html
│ ├── list.html
│ └── single.html
└── blog
└── baseof.html
```
Also, when simplifying code, you often get rid of some double work, as shown in the "site building" benchmarks below.
These benchmarks looks suspiciously good, but I have repeated the below with ca. the same result. Compared to master:
```
name old time/op new time/op delta
SiteNew/Bundle_with_image-16 13.1ms ± 1% 10.5ms ± 1% -19.34% (p=0.029 n=4+4)
SiteNew/Bundle_with_JSON_file-16 13.0ms ± 0% 10.7ms ± 1% -18.05% (p=0.029 n=4+4)
SiteNew/Tags_and_categories-16 46.4ms ± 2% 43.1ms ± 1% -7.15% (p=0.029 n=4+4)
SiteNew/Canonify_URLs-16 52.2ms ± 2% 47.8ms ± 1% -8.30% (p=0.029 n=4+4)
SiteNew/Deep_content_tree-16 77.9ms ± 1% 70.9ms ± 1% -9.01% (p=0.029 n=4+4)
SiteNew/Many_HTML_templates-16 43.0ms ± 0% 37.2ms ± 1% -13.54% (p=0.029 n=4+4)
SiteNew/Page_collections-16 58.2ms ± 1% 52.4ms ± 1% -9.95% (p=0.029 n=4+4)
name old alloc/op new alloc/op delta
SiteNew/Bundle_with_image-16 3.81MB ± 0% 2.22MB ± 0% -41.70% (p=0.029 n=4+4)
SiteNew/Bundle_with_JSON_file-16 3.60MB ± 0% 2.01MB ± 0% -44.20% (p=0.029 n=4+4)
SiteNew/Tags_and_categories-16 19.3MB ± 1% 14.1MB ± 0% -26.91% (p=0.029 n=4+4)
SiteNew/Canonify_URLs-16 70.7MB ± 0% 69.0MB ± 0% -2.40% (p=0.029 n=4+4)
SiteNew/Deep_content_tree-16 37.1MB ± 0% 31.2MB ± 0% -15.94% (p=0.029 n=4+4)
SiteNew/Many_HTML_templates-16 17.6MB ± 0% 10.6MB ± 0% -39.92% (p=0.029 n=4+4)
SiteNew/Page_collections-16 25.9MB ± 0% 21.2MB ± 0% -17.99% (p=0.029 n=4+4)
name old allocs/op new allocs/op delta
SiteNew/Bundle_with_image-16 52.3k ± 0% 26.1k ± 0% -50.18% (p=0.029 n=4+4)
SiteNew/Bundle_with_JSON_file-16 52.3k ± 0% 26.1k ± 0% -50.16% (p=0.029 n=4+4)
SiteNew/Tags_and_categories-16 336k ± 1% 269k ± 0% -19.90% (p=0.029 n=4+4)
SiteNew/Canonify_URLs-16 422k ± 0% 395k ± 0% -6.43% (p=0.029 n=4+4)
SiteNew/Deep_content_tree-16 401k ± 0% 313k ± 0% -21.79% (p=0.029 n=4+4)
SiteNew/Many_HTML_templates-16 247k ± 0% 143k ± 0% -42.17% (p=0.029 n=4+4)
SiteNew/Page_collections-16 282k ± 0% 207k ± 0% -26.55% (p=0.029 n=4+4)
```
Fixes #6716
Fixes #6760
Fixes #6768
Fixes #6778
|
|
Not really a new major version but it's used in production and apparently that
means it should be a 1+. Will try to follow semver better from now on.
Changes:
- `#+OPTIONS: toc:1` now supports not just true/false but numbers to limit
headline levels included in table of conents
- bug fix latex fragment parsing
|
|
This new release improves YAML syntax highlighting.
|
|
Fixes #6756
|
|
This is the first version of Goldmark that supports all the
Smartypants-style typographic punctuation transformations. Now, a
straight single quote in the middle of a word is translated into a curly
quote (e.g. "that's" becomes "that’s"). Earlier versions leave
them untouched. This brings Goldmark in line with Blackfriday.
Fixes #6571.
|
|
|
|
Closes #6719
|
|
Updates ##6719
|
|
golang.org/x/sys is an indirect dependency and needs to be updates as such.
This reverts commit aead8108b80d77e23c68a47fd8d86464310130be.
|
|
Update #6719 6719
|
|
Fixes #6649
|
|
- export #+TITLE (front-matter title) as `<h1>` and demote all normal headlines
by 1 accordingly (i.e. a normal top level headline now becomes a `<h2>`
rather than a `<h1>`)
- preserve whitespace in paragraphs - this allows rendering meaningful
whitespace when wished for using e.g. css `white-space: pre;` (e.g. in verse
/ quote blocks)
|
|
Fixes #6641
|
|
Fixes #6626
|
|
It was accidently pulled back to an old version earlier today.
|
|
This commit also removes support for Ace and Amber templates.
Updates #6594
|
|
|
|
Fixes #6565
|
|
Fixes #6557
|
|
Fixes #6475
|
|
Fixes #6549
Fixes #6551
|
|
Closes https://github.com/yuin/goldmark/issues/36#event-2832923993
|
|
See https://github.com/yuin/goldmark/issues/36
This reverts commit 8221912869cf863d64ae7b50e0085589dc18e4d2.
|
