cortex icon indicating copy to clipboard operation
cortex copied to clipboard

:pencil: A headless, multitenant dynamic content platform powered by Rails, GraphQL and Elasticsearch

Results 23 cortex issues
Sort by recently updated
recently updated
newest added

**Purpose** Capistrano script + related changes to deploy to EC2 **JIRA** **Changes** * Improvements and fixes * * Changes to developer setup/environment * * Architectural changes * * Migrations or...

The logic for the current `ContentItem` State system is brittle, mostly hardcoded and must be completely rebuilt. There are several avenues we can take, including: * Using a library such...

proposal

They're complicated, unwieldy and slow! More details forthcoming.

Q3 2017

While our current WYSIWYG Widget system isn't terrible, it also: * is in need of many new features * is difficult to manipulate and ensure data integrity for (its structure...

proposal

Please see: https://github.com/rmosolgo/graphql-ruby/blob/master/CHANGELOG.md#180-17-may-2018 This is what we've been holding our breath for, and will enable us to have flexible schema definitions. We'll be able to dynamically, at runtime, determine what...

enhancement
technical debt
infrastructure

To ensure data integrity and performance, we need to: * Ensure all relevant indexes are also unique * Set up partial indexes so `deleted_at` records are not considered for uniqueness...

performance
technical debt

We need to create a data structure that could support saving and rendering data for UI elements like: http://experiments.wemakesites.net/css3-treeview-with-multiple-node-selection.html **Current Tree Field Type Data Structure:** `Categories` Field: ```ruby name: "Categories",...

technical debt
infrastructure

Currently, seed tasks are happening in all the wrong places in Cortex. We should abstract most of them to our engines, and rebuild them using [DSLs](https://github.com/cbdr/cortex/issues/549) or with a helper...

technical debt
shame

Placeholder for future discussion. For now, it's a dumping ground for ideas: * https://github.com/exAspArk/graphql-guard

security
infrastructure
proposal

Currently, the structure of `Decorator` and `FieldItem` `data` fields is the wild west - you pass the JSON values directly to the model with no guardrails preventing invalid or extraneous...

infrastructure
proposal