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

Initial Implementation of SCS (structured content server) #1

Open
7 of 8 tasks
victorkane opened this issue Aug 30, 2018 · 2 comments
Open
7 of 8 tasks

Initial Implementation of SCS (structured content server) #1

victorkane opened this issue Aug 30, 2018 · 2 comments
Assignees

Comments

@victorkane
Copy link
Contributor

victorkane commented Aug 30, 2018

  • Perform initial analysis and design to determine the required content model
    • Create a frontend mock-up and abstracting the components and content mode (if unknown)
    • Design the content model via UML diagrams
  • Implement the content model using mongoose schemas
  • Create MongoDB database, in addition to user credentials on that database
  • Marshall environment variables (i.e. HOST, PORT, db and credentials) to parameterize each instance (dev, staging...).
  • Write a basic REST API for the content types including basic CRUD operations
  • Test the REST API CRUD operations using curl on the command line (or an initial version of the command-line CMS)
  • Develop in conjunction with the initial implementation of the CMS (content management system)
  • Develop in conjunction with the initial CWA (client web app) prototype
@victorkane victorkane changed the title Scaffold SCS (structured content server) Initial Implementation of SCS (structured content server) Aug 30, 2018
@victorkane
Copy link
Contributor Author

victorkane commented Aug 30, 2018

Content model analysis and design

@victorkane victorkane self-assigned this Aug 31, 2018
victorkane added a commit that referenced this issue Sep 5, 2018
…ongoose schema and REST API for author, publisher, book content types
victorkane added a commit that referenced this issue Sep 6, 2018
victorkane added a commit that referenced this issue Sep 7, 2018
@victorkane
Copy link
Contributor Author

Domain and App Content Type Roadmap

Which content types will actually have real content items created and edited in the CMS, upserted to the SCS and effectively hydrating the initial version of the DurableDrupal Content Migration Rescue website?

List for initial launch

  • article
  • author
  • case-study
  • video

List to be added incrementally on succeeding iterations

  • book
  • publisher
  • asset
  • event
  • user

Front end publishing content containers (future version)

  • page (routable display unit specifying current content as containers and components)
  • block layout compositions (responsive layout components)
  • blocks (individual content item container components)

victorkane added a commit that referenced this issue Sep 8, 2018
victorkane added a commit that referenced this issue Sep 11, 2018
victorkane added a commit that referenced this issue Sep 11, 2018
victorkane added a commit that referenced this issue Sep 18, 2018
victorkane added a commit that referenced this issue Sep 18, 2018
victorkane added a commit that referenced this issue Sep 18, 2018
victorkane added a commit that referenced this issue Oct 21, 2018
victorkane added a commit that referenced this issue Nov 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant