lumeland / lume.land Goto Github PK

View Code? Open in Web Editor NEW

68.0 68.0 67.0 62.65 MB

The website of lume.land

Home Page: https://lume.land

License: MIT License

TypeScript 6.38% CSS 81.91% JavaScript 11.71%

lume-website

lume.land's People

Contributors

Stargazers

Watchers

Forkers

utamori jppope kkga doujinreviewers bryophyta morrisonak reeseschultz buildcore altesispro kbaba1001 noveogroup-amorgunov officialrajdeepsingh binyamin jennyriess dringtech naltun lemonadern simplerethink uta8a kjlew79 gilesdring hyakt scarf005 bglw segundofdez nubunto leodog896 aurorahharmony severindupouy pvillaverde thiagojedi dominickp nonwiz stead08 ngdangtu-vn kwaa salvaft aeshus mustafaelms weakish uppajung rix1 jackfiszr ek-an carlrafting andrei0x309 mash-graz quadratz rnmwmd rgbcube hellopavelzinoviev hpfast tekeinhor furiouzz rafaelnl84 a1ca7raz arnavk-09 iacore ptrottier jyodann ebullient philhawksworth atlas48 iainsgillis w-haibara ooker777 dogfuntom

lume.land's Issues

Incorrect Link Rendering on UnoCSS Plugin Page

On the page https://lume.land/plugins/unocss/, the intended hyperlink https://unocss.dev/guide/config-file is incorrectly displayed as {@link https://unocss.dev/guide/config-file}.

Light mode code block syntax highlighting appears to be broken by AI widget

Hi there,

I was poking around the Lume docs and I noticed that some of the syntax blocks appear to be light text on a light background.

It seems that the recently added AI widget created an inline <style> block that overrides anything using the .hljs class which can be seen near the top of the script: https://cdn.glimelab.ai/widget/1.0.0/widget.js

Move Highlight.js theme to a separate file

For code-clarity. Also, so people can find it and reuse it.

PR incoming 😉

Fix dead link for vento

@oscarotero

It appears you forgot to replaced a (now dead) link to https://oscarotero.github.io/vento/ with https://vento.js.org/, leaving folks who learn about Vento on the Lume site unable to find out more about Vento

https://github.com/lumeland/lume.land/blob/c38ea1b11500a4f430f1082aa67c1b3bce5c1ea6/plugins/vento.md?plain=1#L12C1-L12C45

Do not use code ligatures in documentation

I was reading the search plugin page and it took some time until I noticed that I had to use != instead of ≠ in the code. 😅

Add sitemap.xml

I will add the missing sitemap.xml using my plugin from the experimental repo.

Use tsx over jsx in documentation

Summary

import type { Data, PageHelpers } from 'lume/core.ts';

export default (
    { title, children }: Data,
    filters: PageHelpers
) => (
  <html>
    <head>
      <title>{title}</title>
    </head>
    <body>
      {children}
    </body>
  </html>
);

replace examples in jsx, jsx preact with tsx.

Motivation

majority of template engines lume supports does not have type system (nunjucks, liquid, etc...). however, users of tsx and tsx preact could benefit by using typescript definitions. for example, it would be helpful to show that layouts uses Data type.

Documentation specifies "Nunjucks", while providing documentation examples in Vento

When following the setup documentation as a new user, I am instructed to "Create a new directory _includes and the file layout.vto inside it. The .vto extension is for Nunjucks: a template engine supported by default by Lume." - See source

This instruction has two issues:

.vto is not the extension for Nunjucks. It is the extension for Vento
It creates an error:

Error: Error rendering the layout of this page
- page: /index.md
    at (https://deno.land/x/[email protected]/core/renderer.ts:160:19)
Caused by Error: There's no handler for this layout format
    at eventLoopTick (ext:core/01_core.js:197:13)

- layout: layout.vto
    at Renderer.#renderLayout (https://deno.land/x/[email protected]/core/renderer.ts:242:15)
    at (https://deno.land/x/[email protected]/core/renderer.ts:143:52)
    at concurrent (https://deno.land/x/[email protected]/core/utils.ts:152:33)
    at eventLoopTick (ext:core/01_core.js:197:13)
    at async Renderer.renderPages (https://deno.land/x/[email protected]/core/renderer.ts:139:7)
    at async Site.#buildPages (https://deno.land/x/[email protected]/core/site.ts:615:5)
    at async Site.update (https://deno.land/x/[email protected]/core/site.ts:583:9)
    at async Events.dispatchEvent (https://deno.land/x/[email protected]/core/events.ts:49:11)
    at async callback (https://deno.land/x/[email protected]/core/watcher.ts:96:24)
Changes detected:
- /index.md

I believe this error occurs as Lume still uses Nunjucks by default. As the documentation has been converted to using Vento instead of Nunjucks, It may be a good idea to add a page to the "Getting Started" section with instructions to install Vento (if Lume does not plan to configure it by default).

Propose I18n system

Adding a translation system allows more people to discover Lume

Incorrect syntax for Nunjucks

It seems that that {% ... %} has also been replaced with {{ ... }}, resulting in incorrect syntax for Nunjucks. See an example here

Most documentation seems to have this issue, and I imagine it has the same cause as #70. in this commit

Improve documentation for index files

i'm not sure if i should move this issue to https://github.com/lumeland/lume, but i guess it belong here since it's related to documentations.

Summary

improve documentation for index files by adding section to describe

how lume finds and uses index files
which file extension will be accepted as valid index file (index.templ.ts, index.tsx, etc)
how could user load custom index file to lume() (like lume.data())

Motivation

sometimes how lume works feels automagical, and documentation often does not fully address lume's internals.

today i was trying to use index.tsx file, and somehow it failed to load. i searched through the docs yet the only example was using with 'index.md'. only after reading deno blog post i could be certain that other index files were supported.

Same LICENSE as Lume?

Hey, Lume & Lume.land look great! Could I use this repo as a starter for my documentation?

That would be cool, but I really need to see a license to feel good about it.

I see Lume is MIT?
Any chance you want to release this as MIT also?
If yes, could you please add a file?
Thanks for sharing this cool work.
Cameron

Pagefind doesn't work without `--allow-run` but the error message is not helpful

How to reproduce:

Install Simple Blog theme using the deno run -A https://lume.land/init.ts.
In lume task change permissions to --allow-net --allow-read --allow-write=./_site --allow-sys=homedir --allow-env --allow-run=git.
Attempt to run. The error like below will be there.
Remove the =git part. No error will be there.

The error is:

TypeError: Cannot read properties of null (reading 'on')
    {{# I omitted a few lines here. #}}
    at https://deno.land/x/[email protected]/plugins/pagefind.ts:139:40
    at Processors.run (https://deno.land/x/[email protected]/core/processors.ts:32:13)
    at eventLoopTick (ext:core/01_core.js:168:7)
    at async Site.#buildPages (https://deno.land/x/[email protected]/core/site.ts:689:5)
    at async Site.build (https://deno.land/x/[email protected]/core/site.ts:532:9)

add option to use local decap_cm.js instead of CDN

Hi,
The wait time for unpkg.com, for decap_cms.js, can be long (a minute or more). This is annoying especially in local/dev mode, but it also sometimes affects my production deployment.

Would it be possible to make this configurable, so that the user can specify a local copy of the script if they want?

I'm having a hard time deciding how to do this, though. First I tried doing it just for my site by writing a processor that modifies the rendered /admin/ page, and rewrites the src of the script to a local url. This could be encaspulated in a plugin wrapping (or coming after) the DecapCMS plugin, and it could have the desired url as an option. But this seems like a non-starter because it seems like deno-dom doesn't know about document.scripts?

So the next thing I thought of was to make the DecapCMS plugin configurable: add an option localscript or some such which the page builder function checks here: https://github.com/lumeland/lume/blob/d5ac50063d60979124ef732121a7426fc9fb436e/plugins/decap_cms.ts#L88 and uses if defined, falling back to unpkg.

It feels a bit weird to me to make this an option, but I don't see how else to make something like this configurable since the url is hard-coded.

Would you:

a. be open to a pull request adding this option
b. have a suggestion for how else I could modify this?

Plugin text and example do not match

In https://github.com/lumeland/lume.land/blame/main/plugins/markdown.md#L64-L77 the text refers to the markdown-it-emoji plugin, but the example uses the markdown-it-anchor plugin.

lumeland / lume.land Goto Github PK

lume.land's People

Contributors

Stargazers

Watchers

Forkers

lume.land's Issues

Summary

Motivation

Summary

Motivation

Recommend Projects

Recommend Topics

Recommend Org