amelki / cms-json Goto Github PK

When setting the type to a number, nothing happens and it remains a string. The number type also does not appear in the drop down list.

@amelki would be a great help if you could deploy a quick update to fix this :)

hitting save triggers a 404 and no data is saved

One should be able to export a data file from the UI

Hello, is there please a way to access the data via rest API: cms-json --schema data/schema.json --data data/data.json --port 3000?
Or do I have to use a json-server for that json-server data/data.json --port 3001?

curl "http://localhost:3000/node/meetings"
curl "http://localhost:3000/meetings"

Thanks.

It should be easier to start the server without any schema/data file - building them from scratch.

If one define:

{
  pages: [
    home: {
      title: "Home page",
      content: "the content"
    }
  ]
}

It would be very convenient to be able to create another node under 'pages' (eg 'about') that obey to the same structure (same fields, same subtree).
This would mean supporting JSON schema definitions/$ref, and be able to define and use these via the UI.

@amelki, the domain (i.e. tenorcms.com) for your playground link seems to have expired this week.

Be able to create different types of objects in a list or in an object map.
Eg:

{
  assets: {
    key1: {
      type: "image",
      src: "foo.png",
      width: "100px",
      height: "100px"
    },
    key2: {
      type: "link",
      url: "http://helloworld.com",
      target: "_blank"
    }
  }
}

First off, I think this is a great project you're working on! Perfect for small-infrequently changing websites like I need. I'm having some issues getting up and running though.

• I cannot add a top level node (same in demo http://tenorcms.com/)
• Because you cannot add nodes, starting with empty json files means you can't do anything
• hitting save triggers a 404 and no data is saved. URL changes to http://localhost:3001/node//new_tree# and UI goes blank
• deep linking does not persist on reload (e.g. navigating directly to /node/pages results in blank page.)

Thank you so much!

Deep linking does not persist on reload (e.g. navigating directly to /node/pages results in blank page.)

There should only be one 'Add node' button, instead of the current 'Add Node', 'Add List', 'Add String Map', 'Add Object Map'.
The selection of the type of node to add should be done in a dialog, that would better explain what each type of node is about.

Use case:
I'd like to be able to create different pages with components

Issue:
At the child level the array only supports strings, so there is no way to create a different page layout as far as I can tell

Desired outcome
Being able to generate something like the following would be great:

"pages": [
  {
    "key": "Home",
    "heading": "Home Page",
    "items": [
      {
        "id": "1"
        "type": "carousel",
        "images": [
          { src: "", alt: ""},
        ]
      },
      {
        "key": "2",
        "type": "table",
        "title": "my table"
        "items": [
          {
            "type": "tableRow"
            "title": "My title",
            "description": "My description"
          }
        ]
      }
    ]
  },
  {
    "key": "About Us Page",
    "heading": "About Us",
    "items": [
      {
        "key": "2",
        "type": "image",
        "src": "",
        "alt": "",
        "caption": "My image caption"
      },
      {
        "id": "1"
        "type": "markdown",
        "markdown": "My markdown text"
      }      
    ]
  }
]

I'm trying to create a model that allows a user to enter in a comma-separated list of items which will then populate data.json with an array. Looking at the available types, I don't really see a clear cut way to do this.

Hey there. I tried to run it but getting error

module.js:549
    throw err;
    ^

Hey, stumbled upon this and it seems like something I would have a need for. I do have a few questions if you would be kind enough to answer :)

My use-case would be a single-deploy react + node app, where the backend would consist of pretty much only the json-cms. I would imagine using it something like this:

• Expose a route for the admin UI at e.g. /api/admin
• Expose a route for getting all of the json data in one request at e.g. /api/data
• Have a default data.json & schema.json stored in version control, which does not overwrite any changes made on the deployed version of the app on new deploys

As for the questions:

• Is it possible to run this as a module inside of a node.js app? How does that work?
• Does the library expose some sort of api for accessing the cms data, or do I need to create my own routes for accessing certain parts of the data?
• Is it possible to persist changes made via the visual editor between deploys, or will it always replace the data with whatever is in version control?

Thanks in advance :)

List items often need to be ordered (think header nav links for instance). The UI should allow ordering via drag and drop.

Currently, a field can only have a primitive type (string, string[], boolean).
It should be possible to define some sub-objects and arrays of sub-objects and use them as field types
eg:

{
  pages: [
    home: {
      title: "Home Page",
      seo: {
        keywords: ["foo", "bar", "hux"],
        canonicalUrl: "http://acme.com/home"
      }
    }
  ]
}