The [docs](https://docs.astro.build/en/guides/cms/) for AstroJS have a dedicated section called "Use a CMS with Astro" which is currently missing Umbraco. I've started putting together a repo of documentation around such an integration to eventually submit for inclusion and would humbly request anyone who knows anything about the topic to consider contributing! I know folks such as @rickbutterfield, @Louie and @Prenders have dabbled somewhat, so was hoping for a collaborative effort with putting some instructions together. Some guides are just stubs, but some ("Storyblok", "Contentful" and "ButterCMS") are so robust that the Astro docs puts them first in the ordering (they're specifically listed in this array!). The repo I've put together for the documentation is here, readily awaiting your PRs: https://github.com/jacksorjacksor/astrojs-with-umbraco-cms-docs https://cdn.discordapp.com/attachments/1217409689588072519/1217409690305167450/astro-icon-light-gradient.png?ex=6603ec20&is=65f17720&hm=35f6517d81ac9ca764e9d2d2928e183d06823afc1dc790b74eb51132bef0c6ae&

This is awesome @jacksorjacksor (Richard Jackson). Would be great to have Umbraco feature on the Astro site.

I know @Louie is having the time of his life in Australia.. so it might be a while before he picks this up

Agreed, would love to contribute to this!

@rickbutterfield Yep - so my thinking is: - Use the repo I've put together as a starting point for gathering info/workarounds/issues/tips/links to other blogs/videos/resources - Clean that up to match an Astro-docs style formatting - Fork/PR/chat w Astro team

Spot on!

Sound's great. This will actually be a really useful exercise for my Astro talk too. Would be great if we can get it into the Astro docs for a reveal at Code Garden 🙂

Will also reach out to Mikkel Keller (of Umbraco Spark fame - https://umbracospark.com/media/0i1dni4h/spark-2024-sustainability-at-scale_novicell_mks.pdf )

Looking at a few of the others, I think there's a few routes we could potentially take. Either live

fetch

the data (like the WordPress example) or do something like generating an OpenAPI client like I detailed in my blog (Ghost example does something similar)

I feel that the OpenApi (codegen) approach that you went through in you blog would be a good one. That said, I wonder if there is more of a 'Quick Start' that is less involved for people just tinkering.

Agreed, just running

fetch()

queries against the API will give you JSON you can render out much quicker

Exactly. Sounds like a good move.

Also it was nice to see Louis put together a basic Typescript Umbraco client in his Skrift article (god bless Skrift): https://24days.in/umbraco-cms/2023/sustainable-performant/astronomically-performant/

@UMB.FYI tip

Thanks for the tip

^FYI @Joe Glombek

Hey all... I was just going to make a start on fleshing out a structure. Just checking that no one else is working on it at the moment so we're not treading over the same ground.

Brilliant, thank you so much @Prenders !

hey all, I'm happy to help contribute, I'm just about to start looking at integrating umbraco cd api with astro... built a couple of sites with astro now (one with squidex), and looking forward to integrating umbraco following your articles etc...

@garpunkal nice! Yeah @rickbutterfield 's article's a great primer on the TypeScript model creation, plus uses "openapi-generator-cli" which is used by the Umbraco team for v14 (so is useful for us to be more aware of in general!) https://rickbutterfield.dev/blog/typescript-openapi-umbraco-content-delivery/

amazing! that's what I needed... I've created my site in astro/typescript and tailwind... now looking to integrate umbraco api. I'll happily provide any learnings I have

Starting with the docs, then we'll see! Currently the Astro site doesn't include Umbraco as a CMS in its "[Use a CMS with Astro](https://docs.astro.build/en/guides/cms/)" page, so we're starting there.

If you have specific questions, happy to try and answer them. We’ve written a few sites that build static html through Astro—but those lessons are “write an API” and now with 13 fully released and content API available, less and less need for custom API endpoints. Advanced topics may include integrations with specific platforms like Netlify and how you use staging and production pushes. But everything is very well documented-another thing that makes Astro great 🙂

@Mark Drake Nice one, thanks so much!

@marcusjmsweden this may be of interest to you

Ah thanks Rick

@marcusjmsweden Ah would LOVE to see this with Blazor tbh

I tried to make jondjones do a video 😉

Me too!! Hey it's us! ([here]()) https://cdn.discordapp.com/attachments/1217409689588072519/1220391756713955418/image.png?ex=660ec564&is=65fc5064&hm=9ccb59d4dd758416e15f36861349a02f01808c8816b7aa8d2bf00aac2f3612f2&

In my current project i am using blazor as components but I am debating whether it would make sense to make the entire frontend blazor and use the content delivery api

Well I've been chatting wtih Kenn Jacobson about this and he put together this blog on the train ride home!! https://kjac.dev/posts/quick-n-dirty-blog-with-astro-and-umbraco/

This is awesome! Thanks for sharing

Encouraging to see we're pretty much all on the same page for a basic/no frills set up

It totally is. I have to say, when I first put in the talk submission for this, I had no idea how many of us were looking into it. I was like "this will be novel and unique". Since then I've accumulated so much great stuff from the community - which is just amazing and I can't thank you all enough 🙂 Gotta love the Umbraco community and its openness to share and support each other.

@rickbutterfield I saw the mass of

../../

and thought of your path aliasing https://cdn.discordapp.com/attachments/1217409689588072519/1220669718311206944/image.png?ex=660fc843&is=65fd5343&hm=e042b374a8a08c525d3b39cae17747e2b6d396304f070071cfcaf4280b6d15eb& https://cdn.discordapp.com/attachments/1217409689588072519/1220669718554218526/image.png?ex=660fc843&is=65fd5343&hm=4f54ccb4d8754d1db5a1ab7d30e01563525bd5ea8646ccce9f6c83453bd0cfd9&

That aliasing tip will change your life. I have the following setup for my current project: https://cdn.discordapp.com/attachments/1217409689588072519/1220674140021850153/image.png?ex=660fcc62&is=65fd5762&hm=7c4681a942256b9b7b5a08b330bd980a6d206ee3ff85e1bb85ce8dba7ceba181&

@marcusjmsweden Have you seen this? https://github.com/YodasMyDad/UmbracoBlazor I thought it was pretty cool the first time I saw it. If you can live with the new SSR mode in Blazor 8 then you can skip all the workarounds.

Yes that was like the "original" :). Seems this has been taken off a bit now

This seems to go off topic from Astro now, Blazor is it's own interesting topic but that's not the point here 😅

Ok maybe you could divide it into two topics?

This is great! I hear he's planning more posts and I need to play with this now. I think I've struggled most with getting a dynamic navigation set up from the Umbraco content, but I just got a hint from him earlier..

bransching off from ricks reply

Discord can't do that.

How do we create a similar topic under help-with-other?

He said > The Delivery API can do that. Fetch all with no properties included. > You'll be slightly overfetching stuff like create and update dates, IDs and so, but nothing terrible > Mind you though, for static rendering you need all the content anyway 😄 Makes good sense to me!

Blazor+UmbracoCMS

Start a new topic 😂 😅 🙈

Yes but I would like the replies with it

okay but that's not possible 🤷

@rickbutterfield I created a new subtopic. Maybe we can get that link over to that one?

I'd love a discussion focused on Blazor though! Start a topic, @ mention everyone who was interested earlier, take screeenshots of existing replies maybe?

I did now

Following this subject with great interest. 🙂 The examples I've seen so far have only dealt with generating Astro pages from Umbraco content, any media being linked to the original Umbraco site. A suggestion would be to add optional media handling (as in copying and relinking) to the documentation. EDIT: noted that Kenn wrote about it in his blog, would be good to have more info about it in the finished documentation though.

Hi @janosbananos - absolutely, the next step for me is looking into media linking (images ofc but areas such as audio too). If you're able to test anything please consider adding your input to the docs!

My 10 cents on Media would be to have it remain in the Umbraco domain in terms of management, then ideally have it served via a CDN to the Astro app. For example Azure Blob storage with a CDN. The media can then be read from the Content Delivery API and prefixed with the appropriate URL. In terms of this initial Astro Documentation - at least for the first pass anyway, we should keep it as simple as possible in line with the other CMS's featured on the Astro Docs. We can then hopefully then get our shoe in the door and expand where required. For now, I think blogs are the best place to explore tinkering, experimentation and edge cases. All that said, I'm totally blown away by the interest in this ❤️

@Prenders Go for it! A problem I had last night is using the auto-generated Typescript classes in place of Kenn's mapped classes (what post is mapped to at the bottom of the attached) - specifically I had issues with casting date and getting the image URL. Will write up more details later on. https://cdn.discordapp.com/attachments/1217409689588072519/1221036737732542505/image.png?ex=66111e14&is=65fea914&hm=f57d42c7cc62504baa7dab310947ddf7c4c4babfd0c9b5cd0b7c46341a1b49ec&

Just replied on the GitHub issue for us to wrap our head around this one. I like the idea of branching off this thread and into a GitHub issue to keep conversation focused. Shall we do that for any areas that are likely to grow legs.

Yeah I think creating issues on the GitHub repo is the best way currently, honestly.

That’s effectively what I’m doing on my site. Using Astro’s own Image component referencing the Umbraco media URL, which helps with caching on build.

For anyone checking this thread out please take a look at @Prenders 's latest contribution, putting in the building blocks for "Building a blog with Umbraco and Astro": https://github.com/jacksorjacksor/astrojs-with-umbraco-cms-docs

Spotted a few typos on my self review 🙈. I'll get those sorted in a second pass.

Completely standard!

A bit of quick feedback while I'm following [the guide](https://github.com/jacksorjacksor/astrojs-with-umbraco-cms-docs?tab=readme-ov-file) (I can make a PR later, just jotting things down): 1. To get started I need an Astro project --> I chose to go with a Blank one, but I guess I should have gone for the Blog template when asked? 2. when listing the folder structure you used:

src/
│   index.astro
│   [...slug].astro

but it should be

src/pages/
│   index.astro
│   [...slug].astro

3. When the Layout gets added it's listed as

import Layout from '../../layouts/Layout.astro';

but layouts live in the

src/pages/layous

directory, the reference should be

import Layout from '../layouts/Layout.astro';

4. The contents of

Layout.astro

is unknown? Could be because I chose the wrong thing in step 1. I made it this to have some valid html:

html
---
---
<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="utf-8">
    <title></title>
</head>
<body>
    <main>
        <slot />
    </main>
</body>
</html>

5. You refer to the RTE content with

<div set:html={article.properties.content?.markup}></div>

but that requires the delivery api to be properly configured, I'd change the first example in the prerequisites from

json
      "DeliveryApi": {
        "Enabled": true
      }

to:

json
      "DeliveryApi": {
        "Enabled": true,
        "PublicAccess": true,
        "RichTextOutputAsJson": true
      },

Note also

PublicAccess

is set to true so we don't have to juggle API keys.

do you want to suggest [...path] too? as this allows any depth of url

Also, @garpunkal I can't remember where you asked but I would love to see a tutorial on Typescript types as well!

yep, I mentioned it in here, but deleted it, as work came up. I've built a complete headless client using that approach above... I've got this [...path].astro file:

javascript
---
import Generic from "@layouts/Generic.astro";
import { GetAllRoutes, GetContentItemByPath } from "@scripts/clients/UmbracoClient";

export async function getStaticPaths() {    
    const pages = await GetAllRoutes();
    if (pages?.items === undefined) return [{ params: { id: "" } }];
    return pages?.items?.map((page) => ({
        params: { path: page?.route?.path },
        props: page?.properties,
    }));
}

export const prerender = import.meta.env.DISABLE_SSR as Boolean;

const page = await GetContentItemByPath(Astro.url.pathname);

---
<Generic page={page} />

this allows you to either prerender (staticpaths) or ssr. based on ENV variable. You can use different layouts per umbraco template. I've then got a file to render the block list, which then determines what blocklist to render.

Thanks @garpunkal I'll have to check it later, moving on to Bellissima for now 😅

happy to help with questions on this though if anyone has any

This is all awesome... and good spot on those issues in the docs @Sebastiaan. I'll update shortly. The initial plan was to keep the first pass in line with the other guides on the Astro docs (hopefully to give use a good chance of getting it up with the least resistance). https://docs.astro.build/en/guides/cms/ We can then expand and add more advanced setups as required (Swagger, CodeGen, Navigation, etc.) What do you all think?

sounds good to me, good to get a presence up on Astro. I'm more than happy to help where I can too. Definitely been some interesting learnings over the last couple of weeks with Astro.

Nice one @garpunkal. Yeah, I've been on a bit of a journey with it myself and migrating a few projects from Gatsby. 🙌

ah nice 🙂 how have you found it?

Yeah, great! I'm using Netlify for handful and some on Azure Static Web Apps. So far, so good 🙂

are you just using astro? or a different tech like react?

Astro for the most part, with some React (dynamic "islands").

ah cool

That's pretty much what my blog post covers, using the same tech that the new backoffice is using to talk to the management APIs https://rickbutterfield.dev/blog/typescript-openapi-umbraco-content-delivery/

ah nice 🙂 didn't see that

@jacksorjacksor (Richard Jackson) Created a PR for the points @Sebastiaan raised https://github.com/jacksorjacksor/astrojs-with-umbraco-cms-docs/pull/7 Point 2: updated incorrect folder structure Point 3: updated incorrect Layout reference path Point 4: added basic Layout.astro markup Point 5: added

PublicAccess: true

to Content Delivery API setup For discussion: Point 1: the other CMS guides do not reference which project template to use. Do we need to? Point 5: I'm currently setting

RichTextOutputAsJson

as

false

which gives the raw markup. Setting to

true

provides structured JSON which maybe useful in some scenarios, but I don't think it would work with the raw

set:html

directive.

@Prenders have PRed - will look into the two points this evening. Thanks for raising!

Wow! I was going to raise a PR myself, but this is even better 😮 Thanks all! Will look into strongly typed models when I get a chance. In my head I am comparing this to strongly types models for Razor, so making the TS models is like Umbraco's Modelsbuilder making the C# models, right?

Pretty much! Once you combine the Delivery Api Extensions package with some sort of client generator you get strong types

ts
// The `type` here has been automatically added by VS Code Intellisense
import { OpenAPI, ContentResource, type BlogPostContentModel } from '@/api';

<section>
{
  blogPosts.items.map((blogPost: BlogPostContentModel) => (
    <article>
      <h2><a href={blogPost.route.path}>{blogPost.name}</a></h2>
      ...content
    </article>
  ))
}
</section>

yep it's very straightforward

I had a few issues using the Delivery Api Extensions models, but that was entirely based on my own inexperience with Typescript. Will write up more formal issues as they might be useful for visibility

It's amazing.

Also shout-outs to @Sebastiaan for giving this feedback 👏 ON 👏 HIS 👏 BIRTHDAY 🎂

FYI Team Astro... I'm heading to the Welsh Hills for a long needed break next week. DM me if you would like any second opinion on any docs stuff. 🏔️🌳😌

Awesome to hear!! I was super excited about the Delivery API coming out, but when I saw there were no typed models (when I was building my Blazor demo), I was a bit sad... Then my partner @Vitor Rodrigues , which was more familiar with OpenApi specs, did a quick POC for my demo and we made it a package. So, on the bright side, it was a great opportunity for us to build our first package! (to be honest we were hoping for this to someday be included in the core 😉)

@rickbutterfield I have some absolute newbie questions and comments for your article! -

import.meta.env.PUBLIC_BASE_URL

- where do I set this base url? I have an

env.d.ts

but it doesn't seem to be the right place - at the

Usage

section of your post I had no idea where to put these things, would good to note that this is happening in the frontmatter of the

.astro

file - Why

getContent20

? I can see there is a

getContent

but it is obsolete. It feels yuck to me to have versioning in method names (functions I know) -

@/api

didn't work for me, I had to give it a path

../api

(I've attached a screenshot of what my setup looks like) https://cdn.discordapp.com/attachments/1217409689588072519/1223215793530208276/image.png?ex=66190b7b&is=6606967b&hm=32d6365a79a446c8a0b641a2e25e9747789eccab8aeb74507905765cc1f286cf&

Public base URL can be set in a .env file. Getcontent20 is generated from the swagger. @api is an alias setup in typescript config

Thank you for the nudge @Sebastiaan! @jacksorjacksor (Richard Jackson) had some similar questions so I've just updated my blog post to answer them, mainly these bits... Pro tips Two very quick tips to make your development experience even better when working with these examples! Firstly, in my

.env

file at the root of the project I'm set up to connect to either my local Umbraco environment or my live one for testing content from production. These variables can then be picked up inside Astro using `import.meta.env.VARIABLE_NAME`:

sh
PUBLIC_BASE_URL=http://localhost:20625
PUBLIC_BASE_URL_HTTPS=https://localhost:44389

# PUBLIC_BASE_URL=https://my.live.env
# PUBLIC_BASE_URL_HTTPS=https://my.live.env

Secondly, use TypeScript path aliases! Rather than having lots of

../

in import statements like

import { file } from '../../../../../api'}

you can alias these folders inside your

tsconfig.json

.

diff
{
  "compilerOptions": {
    ...
+    "paths": {
+      "@/*": [
+        "src/*"
+      ]
+    },
    ...
  }
}

Then inside one of my Astro pages (

/src/pages/index.astro

for example) I can reference both my API and the environment variables we've previously set. And then this bit about the `getContent20()`: > The

getContent20()

is used as the name generated from the Content Delivery API as it's versioned as v2.0, so you will find you have an obsolete

getContent()

function in your generated API too. Kevin Jump has a [great example in his TimeDashboard demo](https://github.com/KevinJump/TimeDashboard/blob/master/TimeDashboard.Client/Configuration/ConfigureSwaggerGenOptions.cs#L21-L23) of how you can remove the versioning from each function name.

Thanks, very helpful! I'll look at the generated name later. And for the tsconfig, this is the only way I could make it work:

{
  "extends": "astro/tsconfigs/strictest",
  "compilerOptions": {
    "baseUrl": "./src",
    "paths": {
      "@/*": [
        "*"
      ]
    }
  }
}

@rickbutterfield - that @Kevin Jump link to remove the version number is so good

Awesome... this is great, and agreed on keeping v1 super simple to have least resistance getting it onto the Astro site. We can then look at extending going forward (Webhooks, TypeScript, etc.)

Fab - I'm going to look into putting in a PR for this today and we'll see what happens

Sweet! Keep us updated.

PR: https://github.com/withastro/docs/pull/7879

This looks brilliant @jacksorjacksor (Richard Jackson) and thanks all for the contributions! Hope this gets a review in the next few weeks, I'm excited! 🙌

Update from Sarah Rainsburger (Astro Docs Lead) https://github.com/withastro/docs/pull/7879#issuecomment-2062626256 https://cdn.discordapp.com/attachments/1217409689588072519/1230414326628876308/image.png?ex=66333ba3&is=6620c6a3&hm=1e9805a83f9a67948ad45e1058bd7debd122128f24b2cdd661e1887399cd02de&

Sweet... good progress at least.

Nice writeup

finally got my headless sandbox public: https://github.com/garpunkal/Umbraco-Headless-Sandbox, would love any feedback on the approach... 🙂

Nice work @garpunkal ! Do let us know how you found the process/what you'd then look to achieve as a result etc.

yeah, I'll write something up when I have chance, just wanted to get it out there really.. I'm sure things aren't 100% so if you have any suggestions on improvements, would love to hear them... I'm not sure if this is hte best place for astro discussion? or if there is another channell

Here is definitely good for Umbraco + Astro related things!

After a few issues I have UmBootstrap building to a dist directory. However, locally it runs as /dist/index.html which then breaks the generated paths as links for child pages e.g. /features/feature-rich-text-editor/ Is this something I should even try and fix locally as it's really intended for a remote server?

You should be able to use

astro dev

or

astro build

followed by

astro preview

to run it on a local server

Ahh good point, I'm use Live Server extension, I'll try the cli

Thanks @Prenders - @Dean Leigh do keep us updated please!

It seems

npm run preview

works perfectly thank you

Sweet. Would love to play around with the Vercel tool at some point too. Although I suppose that only makes sense if you use that for hosting

Because I am using the Free Azure Static Web Apps with GitHub Actions for CI/CD for all my other experiments I will stick to that for now. I was originally trying to get HTMX working in Astro but only got so far so thought I had better learn some Astro basics first 🙂

Nice. Would love to know a bit more about HTMX... keep us posted if you have any joy

Every few weeks I see HTMX mentioned and I look at it again and then I try to figure out what I would need it for and then I give up since I can't see a need. It's probabably super useful, but I haven't found the link yet that explains why to a non-frontender.

If you have a SSG you can have live data in plain HTML pages. That alone is amazing. For example the list of Features in this page comes from Umbraco CD API. If I add a new Feature page it will be dynamically updated without the need to build and publish the page. https://nice-smoke-0659ba11e.5.azurestaticapps.net/

Yes, so here I am wondering what the difference is between that and Astro islands?

Seeing as I've only been using HTMX for 3 weeks and Astro for 2 I may not be the best person to ask 🤣 But… I think if you want dynamic React for example then you would use Astro Islands but you can use HTMX in Astro Page Partials. In fact that is what I have been trying to get working this week but then started getting into routing and SSR. Lots of fun learning this stuff though.

@jacksorjacksor (Richard Jackson) / @garpunkal crazy thought... what if you merged the two of your concepts together? A "living" documentation of how to implement Umbraco & Astro that outputs a site, built on Umbraco & Astro explaining concepts etc.

I'm halfway there @Sean Thorne I have: An UmBootstrap site running on Azure as the Content Delivery API: https://content-delivery-api-01.azurewebsites.net/ A static site rendering content from it: https://nice-smoke-0659ba11e.5.azurestaticapps.net/ And now have an Astro site running locally rendering the same content using Astro (I have the HTMX JSON coming in as well but need to work out how to render it in Astro): https://cdn.discordapp.com/attachments/1217409689588072519/1233428347237961769/image.png?ex=662d0f29&is=662bbda9&hm=1770f3f35bfed0588240c593a64bc9de4e2359dd91b1af2a6de27217fd910a7a&

Does any of these samples play with the authentication aspects?

Auth is definitely possible with Astro. There is some great documentation on the site. https://docs.astro.build/en/guides/authentication/ I have a potential project coming up that would require Firebase auth. Will report back if it comes to fruition. https://docs.astro.build/en/guides/backend/google-firebase/#adding-authentication-with-firebase

it would be nice to see how it works with the default umbraco membership

https://ahastack.dev/ explains how HTMX can be a part of a simpler, more efficient, web stack. I typically go with UHA though 🙂

Looks great! https://cdn.discordapp.com/attachments/1217409689588072519/1235493399646175273/image0.gif?ex=66349264&is=663340e4&hm=f1bbe624bcbdec4a913a72fb9b7a09460201fb8e4ad4d0cf85d5f859cf900fba&

@skttl There was some talk about that in a reacent blazor standup on dotnet too

Delighted to announce that the AstroJS + Umbraco CMS guide has been officially accepted and merged into the Astro documentation! Huge thanks to everyone involved in this project, notably @Prenders & @rickbutterfield. Job done! Guess I need to sort out my own blog now....! https://docs.astro.build/en/guides/cms/umbraco/ https://cdn.discordapp.com/attachments/1217409689588072519/1236613938440048691/image.png?ex=6638a5fa&is=6637547a&hm=3630cdfefca445457133f18b653d5100ebbb60ea5d66ae611e9d6cdddd531659&

That's amazing @jacksorjacksor (Richard Jackson) ! I joined a JavaScript meetup the other day and got to demo using Umbraco Content Delivery API with HTMX and Astro. Great feedback from my JavaScript tutor on ease of UX in UmBootstrap. Big shoutout to @rickbutterfield for Block Preview. I hope we can recreate this in Belissima.

Ah sweet! Really fantastic news! Thanks so much for setting up this initiative @jacksorjacksor (Richard Jackson) 🙌

Oh amazing! Has happened quicker than I thought. Great work team, and thanks @jacksorjacksor (Richard Jackson) for organising it all

Love it! Great work everyone! 🎉

Hi everyone! @cultiv.dev has now marked the initial Umbraco Spark Hackathon "issue" for the docs as Closed, and thus this project is completely finalised! Huge thank you to everyone who's contributed, most notably @Prenders and @rickbutterfield - it was strangely emotional to see this project being completed, and it couldn't have been without you. For anyone using Astro, a platform which continues to grow and develop by the day (they've just announced a Content Layer) do please let us know how it goes! Happy Friday and thank you x https://github.com/umbraco-community/spark-hackathon-2024/issues/10 https://cdn.discordapp.com/attachments/1217409689588072519/1251063419243593738/Screenshot_20240614_083314_GitHub.jpg?ex=666d371a&is=666be59a&hm=e4befbfdbdecb36b419081f2c43f0fb4eaa398e1a6c34a00a2e658838c100338&

@jacksorjacksor (Richard Jackson) a little late to the party but just wanted to say thanks for your great work on this. Astro and Umbraco really works great together.

I'd create a new thread with details of what you're doing and where it fails.

Not so much failure but learning :). Well, learning by failing perhaps haha. I really like this Project and I hope it continues to grow. Good topic for meetups.

@marcusjmsweden Ah thank you so much!