Hi everyone,
I made a fresh (advanced) resume build example for metalsmith: https://github.com/webketje/metalsmith-starter-resume
Published under personal account for testing with repl.it, and it works great! Repl.it allows to preview metalsmith (or any Node) projects' static files.
Which means you can totally have a look and fiddle with it without installing anything: https://repl.it/@webketje/metalsmith-starter-resume
I made a fresh (advanced) resume build example for metalsmith: https://github.com/webketje/metalsmith-starter-resume
Published under personal account for testing with repl.it, and it works great! Repl.it allows to preview metalsmith (or any Node) projects' static files.
Which means you can totally have a look and fiddle with it without installing anything: https://repl.it/@webketje/metalsmith-starter-resume
1 reply
Got permission from 3rd Wave Media by mail to use the CV template as an example for metalsmith
I'd definitely like to split metalsmith.io into smaller pages.
Hi Woody, long time no talk. What is your opinion on Metalsmith's long term chances of survival? I haven't done any work with it for a while. Customers want Gatsby. But IMHO Metalsmith is still the very best for small/medium size sites. It is just so simple... I am mostly concerned that the available plugins will eventually not be updated as Node and it's ecosystem moves on.
@wernerglinka_twitter, perhaps if metalsmith had near the same amount of marketing & budget backing it, it would be able to compete with Gatsby :) . But yeah, hype-driven tech choices hiding layers upon layers of abstraction.. recently joined the metalsmith org to commit to:
- revamping the website (a11y, multi-page)
- address open issues and PR's on core, docs, core plugins
- improve the docs, provide more advanced examples
- consolidate the official repo, plugins on Github (metalsmith org) and NPM (@metalsmith)
- invest in community (gitter chat, issues/ PR's to / adoption of existing plugins)
According to npm-stat, metalsmith's popularity has actually risen until 2018, and plateaued the last 2 years:
https://npm-stat.com/charts.html?package=metalsmith&from=2015-08-31&to=2020-08-31
https://npm-stat.com/charts.html?package=metalsmith&from=2015-08-31&to=2020-08-31
@webketje Thanks for the reply. I hear you but, having a company committed to it, a very active and large user community and React will do that. My last large website build was a 2.0 version build in Gatsby because the CTO wanted a large community and active development. Although I had build the first website with Metalsmith almost 4 years ago and it worked well, that was not enough.
@wernerglinka_twitter
because the CTO wanted a large community and active development
Yes that is unfortunately the circular argument which prevents me too from working with the technologies I like to use, again and again. (circular because if every CTO uses it, ofc. adoption will never grow)
@wernerglinka_twitter I can't see any plugins becoming obsolete due to newer node versions. CTOs will often cover their decisions that way, rightly or wrongly. Metalsmith is great at what it does, there are advancements that we can and will make but the core is solid and the core plugins can also be relied upon.
@woodyrew @webketje Thanks for your responses... but you are preaching to the choir ;-) I am using MS mostly for non-profit work now and plan to continue to use it. There is one thing that we as a community might want to consider and that is building MS starters like the Gatsby community is doing. These provide an easy way for people to get started... some thing to think about.
@wernerglinka_twitter I am aware, and I am working on that. See my second post in this room:
[...] resume build example for metalsmith: https://github.com/webketje/metalsmith-starter-resume
you can totally fiddle with it without installing anything: https://repl.it/@webketje/metalsmith-starter-resume
Also for my plugin metalsmith-taxonomy, there are some pretty elaborate up-to-date examples: https://github.com/webketje/metalsmith-taxonomy/tree/master/example
@metalsmith/default-values is published in the npm org now: https://www.npmjs.com/package/@metalsmith/default-values
Particularly I'd like to address some shortcomings of metalsmith (at least I perceive them as such)
- confusion between metalsmith.src() and working directory (among plugin authors)
- selling point (why metalsmith over plain Node/NPM or vs other static site generators or stuff task-runners like gulp etc)
- is it ES6-ready? (e.g. is it safe to deconstruct like
const metalsmith = { path, src, dest })
I'm a total beginner to this
I can't give you the reason/ solution right away, but I will test it and report here. In the meantime, it would be good to see more about your setup. You could set up a .replit and paste the link here.
When you choose a new project, you can import your local folder, just don't import the node_modules. Instead add a file at the root called .replit with these contents:
language = "nodejs"
run = "PORT=8080 HOST='0.0.0.0' npm start"(and make sure npm start script executes your metalsmith file)
Here is an example: https://repl.it/@webketje/metalsmith-starter-resume
I took your repl and added the multi language plugin, added some stuff (<html lang="">), but as far as I can see it works? I see no empty pages. The
index.html is one folder up because it is the default language. Hit the Run button to re-build: https://repl.it/@webketje/Metalsmith-blog-2
@Cobradile_gitlab
@Cobradile_gitlab there is but you need to "fork" first (click fork, it will redirect).Then 1) Open the files tab, 2) Click the 3-dot menu, 3) Click "Download as ZIP", see screenshot: https://i.imgur.com/EYPuHjh.png. Then extract the ZIP somewhere, and you have it.
@webketje I downloaded the files and tried to build, but I got this error: https://pastebin.com/JU9qjj8V
8 replies
Is there a plugin that extracts metadata from all *.md files -- frontmatter, heading tags -- and makes it available globally?
@SrAceves There is no plugin that provides the markdown-heading-to-metadata feature. However you can easily make the frontmatter of each .md file available to global metadata with a custom plugin,eg. the plugin below will create a metadata key
markdowndata with an object with the filenames [src/posts/post1.md => post1] of all markdown files as keys, and assign their frontmatter (=metadata) to it:.use((files, metalsmith, done) {
const path = require('path');
const metadata = metalsmith.metadata();
metadata.markdowndata = {};
function filename(filepath) { return path.basename(filepath, '.md'); }
Object.keys(files)
.filter(key => key.endsWith('.md'))
.forEach(key => {
const filemetadata = Object.assign({}, files[key]);
delete filemetadata.contents;
delete filemetadata.stats;
metadata.markdowndata[filename(key)] = filemetadata;
});
});
done();
});
I truly love Metalsmith in combination with Fastify to create static sites. I have been playing with Nuxt and similar frameworks, but to in my opinion they are trying to do too much. If you just need a fully static site generator, using Metalsmith seems to be the best and more straight forward options. I would like to see it grow more and have more support from the community. How can I help spread the word?
Did you know? The first version of the VueJS CLI tool used metalsmith to generate component templates! https://github.com/vuejs/vue-cli/tree/v2#user-content-metalsmith
Hello metalsmith-on-gitter! Still using metalsmith for two personal project :thumbsup: I think the Metalsmith project is great, but I do sometimes struggle as someone who isn't a professional developer. Some questions:
- What is the relationship between this metalsmith community and SegmentIO?
- I can imagine contributing to documentation (as I figure things out myself!) Should I just submit PRs?
- Where are the metalsmith.io source-files held?
Hey @BurgundyIsAPublicEnemy I just joined this gitter as I started working on some metalsmith project again. It looks like we're only 16 here, whereas there are 1,038 people on main Slack channel. However, Slack is quieter than here, and people have been encourage to migrate to Gitter.
@DougInAMug_gitlab @BurgundyIsAPublicEnemy The person on DevRant was me :). I'll try to address some of your questions. Segment no longer actively maintains metalsmith and seeks to transfer the rights to another legal entity. We've been in contact with Segment for about 6mo. and we are fleshing out the details for ownership and copyright transfers & migrations, but getting all stakeholders' agreement takes a lot of time and that is the reason development has stalled on the main repository.
@DougInAMug_gitlab There is no relationship between this Gitter and Segment (except some of the metalsmith ex-contributors are in as members) As for the metalsmith.io code you can find it at https://github.com/metalsmith/metalsmith.io, you can definitely submit PR's though I will eventually rewrite/ restructure the website when all the administrative hassle is over.
:tada: Great news @webketje ! Thanks so much for taking the initiative on this :pray: Keep us posted and let us know if/how we can meaningfully help.
(I just found the DevRant post I guess you and @BurgundyIsAPublicEnemy were talking about: https://devrant.com/rants/2935556/metalsmith-is-an-older-but-still-awesome-nodejs-static-site-generator-due-to-met )