~M•29
Published on

Project 05 - Can we autogenerate a workflow ID for new projects?

Authors
  • avatar
    Name
    MDolce
    Twitter
Table of Contents

Problems we need to solve:

Introducing a category field type for ContentLayer. [Concept Only]

At some point, we should consider adding a database manage content created using ContentLayer. Currently, the Shipixen app uses tags as fields to search and sort content. We have added a workflow naming convention that are manually created. However, it may be possible to use nanoid to autogenerate the workflow naming convention.

The goal is to make it easier to track and associate related content beyond just using tags and links.


Establishing requirements for our methodology:

  1. Generate a workflowID for Blogs using nanoid.
  2. Add the workflowID to the search provider component.
  3. Create a function to generate the workflowID with established naming conventions.

Challenges:

  • Dynamically adding the workflowID to the front matter
  • Updating source code to recognize the workflowID in the search component

Solution?

TBD

REF(s):

Internal Pages

Project 03: Established UAT

Project 04 - Thinking About Case Studies

External Site Reference & Functional Concepts

Contentlayer: defineNestedType | https://contentlayer.dev/docs/reference/source-files/define-nested-type-eeeb4ab5

Contentlayer: Field Types Reference | https://contentlayer.dev/docs/reference/source-files/field-types-defe41e9

Cules Coding: Lesson 04 - MDX, MongoDB Static Homepage | https://www.youtube.com/watch?v=kPG07USpnes