Identifying Customer Needs

Here is the first part

Here is the last part is in this sentence.

Links to Databricks Resources

• https://docs.databricks.com/administration-guide/workspace/index.html

PlantUML Insertions

• https://plantuml-documentation.readthedocs.io/en/latest/diagrams/sequence.html
• https://crashedmind.github.io/PlantUMLHitchhikersGuide/

PlantUML Diagrams

@startuml
'left to right direction
skinparam actorStyle awesome

actor Guest as g


package Professional {
  actor Chef as c
  actor "Food Critic" as fc
}
package Restaurant {
  usecase "Eat Food" as UC1
  usecase "Pay for Food" as UC2
  usecase "Drink" as UC3
  usecase "Review" as UC4
}

fc --> UC4
g --> UC1
g --> UC2
g --> UC3

:User: --> (Use)
"Main Admin" as Admin
"Use the application" as (Use)
Admin --> (Admin the application)

@enduml

Project Management

Look for the Microsoft Project file in the root of the repository.

How to build documentation

Use a makefile that will run the pure pdoc API documenation separate from the other documentation.This will allow us to have a single source of truth for the API documentation and the other documentation. The rest of the documentation will be built using docusaurus and will link to the pdoc documentation.

Next Steps

Does this show up in Marked2?