Skip to content

v1 route diagram and core feature set #8

Description

@haustraliaer

Here is a basic model for the app as discussed:

————————————————————————— Admin Account
|  Brands
|  |   – [ Title ]
|  |   – [ Hero image ]
|  |   – [ List of pages ]
|  |   – [ Brand access password ]
|  |   
|  |  Pages
|  |  |   – [ Title ]
|  |  |   – [ Page image ]
|  |  |   – [ List of sections ]
|  |  |  
|  |  |  Sections (anchor linked via sub-menu)
|  |  |  |   – [ Asset Groups ]
|  |  |  |   – [ Markdown Blob ]
|  |  |  |   – [ File Upload - to link in markdown ]
|  |  |  |   – [ List of files ]
—————————————————————————

Core Functionality

  • Assets handled by S3, but only accessible by the app backend
  • Create / Edit / Delete brands, pages, sections...
  • Upload files to an "asset group", update / remove individual files.
  • Upload images to be linked in the markdown blob (not considered "assets")
  • Download files (pipes s3 reference through rails but not made available to client)
  • Create and email long hash routes to files, or file bundles [ can be deleted by admin ]

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions