For testing, return basic data such as: { meta: {}, data: [] }

Our first major UI implementation -- navigation.

Acceptance Criteria

• Create navigation that matches the attached image (and other images in the ui-designs directory)
• Any colors and common components should be treated generically

Notes

• Try to leverage props for any displayable pieces
• Use the prop-types package to type props

Create a basic hello world go server. I'd maybe use echo to do this.

Acceptance Criteria:

• Create a server with Go that, when running and requested at a specific port, returns a status code 200 and JSON response
• Add documentation to the README

Pull request templates help developers more readily know which items are important for reviewers and from a source revision documentation. Resolving this issue requires the assignee to create a pull request template. See docs below.

https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository

Description

This ticket is meant to be more of a discussion. The assignee will present their ideas for how they might go about implementing the Content View. Once all parties have signed off, this ticket is complete.

View:

Sign-off

• @JacobPernell
• @mskalandunas

Create a content collection view as per the designs here.

This page needs to do the following:

• Display a table with a list of Content that shows: which accounts the Content is posting/posted to; the Content description; the date the Content was scheduled/posted; labels; Content status (posted, scheduled, deleted); and edit icons ('Archive' and 'View' icons for posts that have the label Posted/Scheduled, and just 'View' for archived posts)
• Create dummy data object as temporary data to display/filter through (in a separate Issue in the future, will set up actual saving/editing of Content to the Server)
• Before this Content collection view is loaded, display a 'skeleton loader' to let user know content is being loaded
• Allow the user the ability to Filter Content by status (Posted/Scheduled/Archived), social media account (FB/Insta/Twitter/LinkedIn), and time range
• When displaying filtered Content collection, display individual tags for each filter that has been applied
• Allow user to input a search query to filter by keyword search (as part of this sub-task, determine if this will be querying only the Contents 'description' or if it will search through everything)

(Notes:

• Scheduling and editing individual pieces of content will be handled in a different Issue
• There might need to be a change in the design to differentiate Archiving vs. Deleting a piece of Content)

Because we'll most likely want to avoid a monolith upfront, we should conceptualize what services we may need. Add a list of potential services and a diagram describing the distributed system in the docs/engineering directory.

The goal of this is to send a POST request to our server that will then POST to a facebook wall.

Create a document under docs/engineering that outlines potential API endpoints for the UI given the following product features:

• Creating content
• Getting a content item
• Getting a collection of content
• Filtering content

We only need top-level endpoints (/api/v0/content etc), not any indication of what that endpoint requires or returns.