dotCMS / dotCMS/core

SDK: Add Function to Open Edit Content on specified Content Type

Open
#31,409 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

OKR : User Experience Priority : 3 Average Team : Scout Type : New Functionality
Dominant language
Java
Stars
970
Forks
486
Avg merge
3d 33m
Merged PRs (30d)
170

Description

Parent Issue

TBD

User Story

As a developer, I want to be able to add a button using a function provided by dotCMS that allows the content author to create an specific content without having to search for the correct Content Type.

Acceptance Criteria
  • This function should be available to use in Headless and Traditional Rendering
  • This function should have a macro version for non developer persona to use in their VTLs
  • This function should be included in our headless examples and starter to serve as a guide on how to use it
Proposed Objective

User Experience

Proposed Priority

Priority 3 - Average

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
Assumptions & Initiation Needs
  • You understand how the pages communicates with the UVE
  • You understand how the macros work on dotCMS
Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files, tests, or entry points are named. Start by reading the UVE communication and macro documentation, then trace how Headless and Traditional Rendering expose authoring actions; done means the function works in both modes, has a VTL macro, and is demonstrated in the headless examples and starter.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend-api-design, content
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.