roll

Possible improvements to the first screen of the website

1

# Overview ## Currently It's nice and solid but might be not eye-catching for some users and it doesn't say anything about our work mostly so one can just close...

# Overview Based on Livemark (see the discussion on Slack)

Deprecate create.frictionlessdata.io in favor of Frictionless Application

2

Currently, it's blocked by the Application not being released yet but we can do so in a few months

# Overview It's very fast and provides a simple python bindings: - https://github.com/kindly/datapackage_convert_py/ - https://github.com/kindly/datapackage_convert

Currently, it's blocked by the Application not being released yet but we can do so in a few months

# Overview Currently, it's integrated using https://github.com/leonsteinhaeuser/project-beta-automations that require some workflows boilerplate to connect all the needed repos. Hopefully, Github Projects will evolve soon to improve the way of "inboxing"...

https://frictionlessdata.slack.com/archives/C0369HZ2SLT/p1655534563876419

Schema editor integration

7

# Control flow - we listen for `#field-schema[-url]/[-json]` changes - on changes we render `tableschemaUI.EditorSchema` with url/File/text as descriptor and `onSave` callback - user do her schema edits - on...

Renaming master branch to main

3

Hi @cpina, We're doing this renaming org-wide as per https://github.com/frictionlessdata/project/issues/537. Can you please take a look? It's as easy as updating the branch name here - https://github.com/frictionlessdata/schema-collaboration/settings/branches - no more...

# Overview It's a long-shot and research but we can consider building a report site into a branch instead of using https://repository.frictionlessdata.io/pages/dashboard.html. It will solve the problems with artifacts not...