Comment

Comment by insky

+1 for having a usable demo to play with off the bat.

I tried to publish a simple page from the demo. But I did have problems:

I created a callout, and then created a page. I then tried to add the callout to the page. And save as published. But I was hit with a message: need to commit first? I didn't get that.

I then saved as a draft, and then hit commit. Not sure what was happening.

I then tried to view the page, but got a 'No content' message.

I then added something to the main content of the page. And saved. No change.

I then commited again. But still had the 'no content' message.

I then tried the commit and approve, which seemed to finally publish the page.

Confusion lies in the commit part, or in the publishing process, order of process. Some buttons looked deactivated, but actually you can click on them, like the 'Commit and approve' button. I was a little perplexed.

The demo then reset itself before I could test a form!

All feels slow to me. But then again most online CMSs feel a little like that to me.

It was also quite difficult dumping widgets into areas. A little practice got there, but it wasn't the easiest of things for me to do.

parent insky 12 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton