Obtaining drop-in index.html
#541
Replies: 1 comment 19 replies
-
|
I’m not familiar with Astro to be honest. Perhaps you could search for issues to get an idea? Either way, you need to manually initialize the CMS using the API if you use the npm version. Here’s our work-in-progress documentation: |
Beta Was this translation helpful? Give feedback.
-
|
Things would be much simpler if you used the CDN version in a static Personally I have never used Astro because I’m mostly in the Svelte world, but I know it’s the most promising meta framework. I’ll consider some form of better official integration after the 1.0 release. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, cdn makes much more sense considering your clip of releases... |
Beta Was this translation helpful? Give feedback.
-
|
The question about admin.html is not related to Astro, I'd say. It's mostly on having a completely local bits without having to rely on unpkg/another domain or external scripts (I experienced once when unpkg was slow for access from Europe). In the ideal regime, one could even launch such admin.html from file:/// - like a PWA. And this self-contained HTML can be obtained by simply inlining of the Sveltia script / or using rollup (I came up with one of the ways in the comments above). I guess if GitHub releases are automated with GitHub Actions, adding/publishing such HTML should not be an issue or require any additional labor... |
Beta Was this translation helpful? Give feedback.
-
|
Regarding Astro integration, it could be awesome to somehow support Astro components as blocks, and allow to at least insert/reorder the blocks. And then ideally to WYSIWYG-display/edit them without extra clicks. Like so, one could edit the landing page, reorder the sections and so forth At least, to allow editing rich text in such html-with-custom-elements pages while preserving the custom-elements (even if not allowing to edit nicely the custom-elements/blocks themselves) Maybe one could also somehow get inspired from WP Gutenberg blocks editor or similar Probably technically this should entail to hacking Facebook Lexical to represent any top-level custom-element as some catch-all Lexical Node... Or use MDX Editor (although it seems to have a quite complex architecture) |
Beta Was this translation helpful? Give feedback.
-
So I made the following ---
---
<html>
<script>
import CMS, { init } from '@sveltia/cms';
init()
</script>
</html> |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
I've followed the
npm install @sveltia/cmspath (for my Astro blog).How can I get a fully self-contained
admin/index.htmlfile which I can place inpublic/admin/index.html?Ideally, I'd like to build it from my npm-installed version of sveltia.
For now I've used:
Is it also possible to just download this js and inline it in the script tag?
Would it be possible to provide a ready index.html artifact in GitHub releases?
But I'd like to serve the CMS from my domain and not use and extra CDN.
Ideally, I'm searching for some npx/package.json command which could take an admin.html with manual init code and produce a final self-contained index.html which I can place into my public/admin/index.html. Or so that this building process can be directly integrated into
npm run buildprocess of the Astra blog (with npm-integrated build process, I can easily update the version of sveltia)Thanks!
Beta Was this translation helpful? Give feedback.
All reactions