The actual option is called showSortButtons not showSortingButtons. See https://jsonforms.io/docs/uischema/controls

See eclipsesource/jsonforms#1198 for more context

Should happen automatically on push to master

Aka web component usage.

Might actual be an JSON Forms issue.

There are multiple small issues in the Examples:

• Name of page and entry in navigation are mostly inconsistent
• The max length of 5 does not make any sense in the array control example. It seems weird that the example contains initial invalid data
• Categorization example is currently broken. It only renders No applicable renderer found.
• Inferring a UI schema and Inferring both schemata are partially broken. For one of the elements they also render No applicable renderer found.
• The star renderer in custom control example does not properly showcase how a good custom renderer should look like. A label (for example Rating) is missing. Also the cursor on the star renderer looks weird.

Also see eclipsesource/jsonforms#853 and eclipsesource/jsonforms#854

To demonstrate the various UI schema elements.

We should somehow sync the state between the seed and the listings on the website. Copy & paste is probably not the best approach.

We should display the version of the framework on the website.

• highlight currently selected entry in AppBar
• hightlight AppBar entries on hover

Redux is now a peer dependency. The tutorial should point out the it must be installed

When generating API docs via

lerna run build
lerna run doc

within $JSONFORMS_REPO it's tedious to copy the docs over to the website by hand. What I currently do is:

rm -rf $WEBSITE_REPO/public/api/{core, vanilla, material}
cp -r $JSONFORMS_REPO/packages/core/docs $WEBSITE_REPO/public/api/core
cp -r $JSONFORMS_REPO/packages/vanilla/docs $WEBSITE_REPO/public/api/vanilla
cp -r $JSONFORMS_REPO/packages/material/docsl $WEBSITE_REPO/public/api/material

It'd great if we could automate these steps.

The description of the Rule example (examples/rule) says:

This example uses a Rule to display an additional selection control if the 'Is Alive' checkbox is unchecked. If is is checked the control will be hidden. Give it a try!

However, in the example, the additional selection control is enabled when the 'Is Alive' checkbox is checked and is disabled (not hidden) when the checkbox is unchecked.

The example or the description should be updated.

When selecting a date in the Landing Page Form, the currently selected date in the popup is invisible.

In the attached screenshot, 14 is currently selected.

• Visit http://jsonforms.io
• Click on any input in the presented form
• The console is full of errors

May be related to #27

Check if site works in FF.

Looking at the 'Create a renderer', 'Create a tester', 'Register the renderer' sections, there's no mention about where the listed code should go e.g. index.js, rating.control.js etc.

It was added due to the mos recent MUI update, but it shouldn't be actually necessary.

Landing Page

• Get Started Button on landing page does not work
• Read the Docs Button on landing page does not work

Examples

• Array Example missing the Wrapper to show data, schema and jsonschema
• Rule Example missing the Wrapper to show data, schema and jsonschema
• Categorization Example missing the Wrapper to show data, schema and jsonschema
• Example landing missing
• Inferring a UI schema Example missing
• Inferring both schema Example missing
• Custom controls Example missing

Docs

• Landing page : This page lists important articles to get started below. A list of all available articles is available to the **left**. Will there be an additional list or should this point to the list on the right?
• Getting started -> Usage with existing redux store I don't get the last sentence, maybe I just miss react knowledge.
• Layouts
  • http://jsonforms-beta.de/docs/uischema/controls does not work if opened in new tab
  • http://jsonforms-beta.de/examples/layouts#horizontal-layout does not work if opened in new tab
  • http://jsonforms-beta.de/examples/layouts#vertical-layout does not work if opened in new tab~~
  • http://jsonforms-beta.de/examples/layouts#group-layout does not work if opened in new tab, but the id is missing anyway
  • http://jsonforms-beta.de/api/core/interfaces/group.html should be http://jsonforms-beta.de/api/core/interfaces/grouplayout.html
  • Categorization section is different from the other three, also has an inline demo instead of a link
• Rule
  • http://jsonforms-beta.de/examples/rule does not work if opened in new tab
  • TODO: do we describe anywhere how to initially hide elements? I don't really get what you want to achieve
  • a link to http://jsonforms-beta.de/api/core/interfaces/rule.html would be good as done in the Layouts section
• Custom Renderers
  • Core concepts about rendering the list is not inlined and stands out, looks weird
  • contains TODOs

Support

• missing

General

• Can't click on the JSONForms Text in the title, only on the image
• Copyright and imprint need spacing

• Fix spacing for installation instructions
• Use create-react-app to scaffold react app

See https://github.com/eclipsesource/jsonforms/pull/1522/files

For example the Create a JSON Forms App tutorial does not allow the user to modify the given data. This was reported in https://spectrum.chat/jsonforms/general/bug-in-create-a-json-forms-app-tutorial~8af86298-7878-4238-8ddd-f4b20cb94094

In the seed, the RatingControl looks like this https://github.com/edgarmueller/jsonforms-react-seed/blob/master/src/rating.control.js, while in the tutorial it is different (see below).

• The site needs some overhaul regarding the theme
• The embedded examples work but throw errors when switching tabs

• Link to Landing page should be on Full Logo including text in the upper left corner (see #16)

• Tag line: Complex forms in the blink of an eye

• Remove Read the Doc button from landing page

• Add correct fav icon

• Disclaimer on Landing page: Currently we support primarily

• Getting started:

  • How do I get an empty react app
  • In case of create-react-app demo app where do I put my store? (=> index.js)
  • DispatchRenderer should be named JSONForms (moved to JSON Forms, see here).
  • Provide import code snippet:
    import Provider from 'react-redux';
    import DispatchRenderer from '@jsonforms/core';
  • Rewrite to match what needs to be done based on empty react app
  • Comments on text in this GDOC:
    https://docs.google.com/document/d/1QPlxKM4YjjttWfdbwoHeGmmy9bvY4fdzYiagepbPhec/edit?usp=sharing (please see my comments within the doc)

• http://jsonforms-beta.de/docs/uischema: Box in Blue with info symbol

• Docs: Indentation of the 2nd level items in the navigation should be increased otherwise they are on indentation level as selected items in the 1st level.

• If possible simply: http://jsonforms-beta.de/docs/uischema should also list on the detail page all subitems as links. (simple, if duplicated, which I did for now)

• Why does API doc open in separate window?

• At the end: Trigger Website review by Sage (define boundaries!) (see #19)

Add to the support page what we had on http://jsonforms.io/#/support (see #15)

Examples:
http://jsonforms-beta.de/examples/categorization => broken (see respective JSON Forms issue #686)
http://jsonforms-beta.de/examples/custom-controls => Date control broken (fixed in JSON Forms)

Add Twitter link

• There should be a little more whitespace within the white banner to not look cramped.
• The icons are of different height. This leads to an uncomfortable viewing experience.
• The links in the top right corner are not visible enough for my taste. Maybe style them bold?

To avoid jumping menus etc when it is toggled between pages

• Visit http://jsonforms.io
• Form input Age is presented with a validation error is a required property
• Enter a valid value for Age in the presented form (e.g. 89)
• Remove the value again
• The form shows a new validation error should be <= 100 should be >= 18 should be integer
• The form is now completely broken and can no longer be used. The console is full of errors.

Failed to minify the code from this file:

    ./node_modules/@jsonforms/core/node_modules/uri-js/dist/esnext/uri.js:42 

Can we pre-render the landing page?

Major

• Cookie banner is shown often:
  1. /docs/api banner is shown
  2. select Core
  3. use back button, banner is shown again
• API links in /docs/available-actions link to localhost
• /docs/available-actions "ref resolving" link in text points to non-existing path
• /docs/tutorial: Materal UI link is broken
• /docs/uischema/layouts: Links to layouts are broken

Minor

• /docs/available-actions multi line API specification should be styled differently
• /docs/custom-renderers: NOT_APPLICABL -> NOT_APPLICABLE
• /docs/custom-renderers: switch -1 with NOT_APPICABLE
• /docs/custom-renderers: enumeration has different font and is misaligned
• /docs/getting-started: enumeration has different font and is misaligned
• /docs/renderer-sets: Material ui link should link to its main site, not next.
• /docs/uischema/layouts: First paragraph (in each section) is styled differently
• /docs/uischema/layouts: There is only one demo link for one type of layout
• /docs/uischema/rules: First paragraph is styled differently
• /docs/what-is-jsonforms: How does it work, 2nd paragraph is styled differently
• /examples/categorization: Should show both categories initially, looks broken with only one
• /examples/categorization: Weird empty horizontal space before first category
• order of doc sections is alphabetically sorted instead of content-wise

Nice to have

• Add landing pages for docs and examples as the menus in the middle of the screen look weird
• /docs/renderer-sets: There should be at least some words about other renderer sets than material and vanilla.
• /docs/getting-started: command line should be npm ci instead of npm install
• /docs/custom-renderers: command line should be npm ci instead of npm install
• /docs/getting-started: getting started and the starting section in /docs/custom-renderers are redundant. Suggestion: Remove the one of /docs/custom-renderers and link to /docs/getting-started or extract a common component and reuse that in both.
• /docs/available-actions API anchors will not survive any api change, see /docs/available-actions#initdata-any-schema-jsonschema-uischema-uischemaelement-options-initactionoptions--ajvajv

Add them on a single page