There's pretty good documentation on web extensions but it doesn't seem trivial to do. In particular, I think there would need to be some attention around anything that relies on calling the underlying static site generator (serving the preview, for example) and I'm not sure how tractable that is.
There's pretty good documentation on [web extensions][web-ext] but it doesn't seem trivial to do. In particular, I think there would need to be some attention around anything that relies on calling the underlying static site generator (serving the preview, for example) and I'm not sure how tractable that is.
[web-ext]: https://code.visualstudio.com/api/extension-guides/web-extensions
<!-- github-comment-id:1233208515 -->
Documentation is indeed pretty good, but it will require a significant rewrite or a separate extension with less functionality like, for instance custom scripts/actions. That can only be achieved when you have access to Node.js.
Documentation is indeed pretty good, but it will require a significant rewrite or a separate extension with less functionality like, for instance custom scripts/actions. That can only be achieved when you have access to Node.js.
<!-- github-comment-id:1233770137 -->
I think not having access to the SSG would be similarly problematic. Unless there's a way to combine it with a container I think the limitations are likely too many to make it feasible - but maybe still worth investigation?
I think not having access to the SSG would be similarly problematic. Unless there's a way to combine it with a container I think the limitations are likely too many to make it feasible - but maybe still worth investigation?
<!-- github-comment-id:1234285023 -->
It definitely makes sense, at least even a slimmed-down version. Having the option to manage the markdown and media might be enough in these scenarios and for that, a slimmed-down version works perfectly.
It definitely makes sense, at least even a slimmed-down version. Having the option to manage the markdown and media might be enough in these scenarios and for that, a slimmed-down version works perfectly.
<!-- github-comment-id:1234426829 -->
Hi @estruyf! First of all, thanks for all the great work on front matter!
I'm doing an exploratory work on this implementation today, I'll get back with what I find and how much work I need to do to make it work (or even if it is possible).
Hi @estruyf! First of all, thanks for all the great work on front matter!
I'm doing an exploratory work on this implementation today, I'll get back with what I find and how much work I need to do to make it work (or even if it is possible).
<!-- github-comment-id:1636739809 -->
FWIW, I've been using Front Matter with Code Spaces very successfully for the last few months. It involved a bit of setup in my repo, but it was worth it for me and my users.
Getting things working with Hugo and Front Matter was as straightforward as defining this devcontainer config:
FWIW, I've been using Front Matter with Code Spaces _very_ successfully for the last few months. It involved a bit of setup in my repo, but it was worth it for me and my users.
Getting things working with Hugo and Front Matter was as straightforward as defining this devcontainer config:
https://github.com/platenio/platen-template/blob/8a0c3dee463153c499c2645d8487ca2b6e5ae93e/.devcontainer.json#L1-L33
And I was able to walk my users through [getting setup with Front Matter in my getting started doc][01].
[01]: https://platen.io/getting-started/happy-path-setup/#setting-up-front-matter
<!-- github-comment-id:1638240255 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Adding support for vscode.dev so that the extension can run in the browser.
@estruyf thx for the url. i didn´t know this site till you mentioned it.
Happy coding :-)
There's pretty good documentation on web extensions but it doesn't seem trivial to do. In particular, I think there would need to be some attention around anything that relies on calling the underlying static site generator (serving the preview, for example) and I'm not sure how tractable that is.
Documentation is indeed pretty good, but it will require a significant rewrite or a separate extension with less functionality like, for instance custom scripts/actions. That can only be achieved when you have access to Node.js.
I think not having access to the SSG would be similarly problematic. Unless there's a way to combine it with a container I think the limitations are likely too many to make it feasible - but maybe still worth investigation?
It definitely makes sense, at least even a slimmed-down version. Having the option to manage the markdown and media might be enough in these scenarios and for that, a slimmed-down version works perfectly.
Hi @estruyf! First of all, thanks for all the great work on front matter!
I'm doing an exploratory work on this implementation today, I'll get back with what I find and how much work I need to do to make it work (or even if it is possible).
FWIW, I've been using Front Matter with Code Spaces very successfully for the last few months. It involved a bit of setup in my repo, but it was worth it for me and my users.
Getting things working with Hugo and Front Matter was as straightforward as defining this devcontainer config:
https://github.com/platenio/platen-template/blob/8a0c3dee463153c499c2645d8487ca2b6e5ae93e/.devcontainer.json#L1-L33
And I was able to walk my users through getting setup with Front Matter in my getting started doc.