Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Epic] MVP of the Frontend v3 app: home, showcase, org and search pages #9

Closed
26 of 29 tasks
lauragift21 opened this issue Jun 3, 2020 · 2 comments
Closed
26 of 29 tasks
Assignees
Projects

Comments

@lauragift21
Copy link
Contributor

lauragift21 commented Jun 3, 2020

We want to build an MVP of a data portal frontend using Next.js. Data can be mocked or come from demo.ckan.org.

MVP URL: https://portal.datopian1.now.sh/

Acceptance

This would be the core of an MVP

  • showcase
    • dataset - can model layout on top part of datahub.io showcase pages
    • resource page - a dedicated resource page
  • org profile page with list of datasets
  • search page for searching datasets (this could be dynamic/pure client side JS or could be server side)
  • home page (semi-optional for now in fact)

Dataset and Resource page

Tasks

Showcase page(s)

  • Stub a page /@myorg/mydataset that is empty
  • Copy over and convert nunjucks template from current frontend-v2 into jsx template (omitted all the preview stuff and resource display)
    • Copy the preview material into a /@myorg/mydataset/r/myresource template
  • Refactor the JSX into templates so we move away from "inheritance" towards "composition" in how we build pages
    • Simplest to start would be to move everything into a component "DatasetShowcaseCore"
  • Stub out the frontpage from frontend v2
  • Replace hard coded page data with hardcoded data in the "controller"
  • Replace hard coded data with real data from a live source ...

Organization page(s)

  • page with a list of all organizations
  • page with a list of related datasets under an org.

How do we have /@myorg/mydataset => lookup data via fetch API from the right place?

We want /@myorg to be dynamic. Creating a dynamic route might work and setting up fetch API to pull data from the dynamic source (more research to be done here)

@lauragift21 lauragift21 changed the title MVP of the Fronend v3 app: home, showcase, org and search pages [Epic] MVP of the Fronend v3 app: home, showcase, org and search pages Jun 3, 2020
@anuveyatsu anuveyatsu changed the title [Epic] MVP of the Fronend v3 app: home, showcase, org and search pages [Epic] MVP of the Frontend v3 app: home, showcase, org and search pages Jun 8, 2020
@anuveyatsu anuveyatsu self-assigned this Jun 15, 2020
@anuveyatsu anuveyatsu added this to Prioritized in v1 Overview via automation Jun 15, 2020
@anuveyatsu anuveyatsu added this to the Sprint - 26 Jun 2020 milestone Jun 15, 2020
@anuveyatsu anuveyatsu moved this from Prioritized to In progress in v1 Overview Jun 15, 2020
@rufuspollock rufuspollock moved this from In progress to Prioritized in v1 Overview Jun 15, 2020
@anuveyatsu
Copy link
Member

v1 Overview automation moved this from Prioritized to Done Jul 7, 2020
@rufuspollock
Copy link
Member

@anuveyatsu can we make sure all the unchecked items in this issue are definitely captured iin one of the follow up issues (and could you note that in your fixed comment, when done).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
v1 Overview
  
Done
Development

No branches or pull requests

3 participants