can an experience site template be in a managed package?

Open
  • Is something wrong?
#88 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
release

Research direction

Compare the earlier versions in GitHub to understand how the experience site template was included, then investigate whether managed packages support packaging it. If access to the org is provided, attempt the packaging workflow; done means a confirmed feasibility result and, if supported, an installable package containing the template.

Written by the indexing model from the issue text.

Description

enhancement

I could not figure out how to include an experience site template in the managed package. Earlier versions do include a template (can find in github) but that was not packageable. It makes it slightly easier to install if the template is included. This would be primarily a research project unless because I am not sure that anyone else can try to actually package it again. If someone is familiar or wants to learn managed packages, I can give them access to the org that would be a project for a developer.

Dominant language
Apex
Stars
9
Forks
22
Avg merge
2d 22h
Merged PRs (30d)
3

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No 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.

More from SFDO-Community/UnsubscribeLink

All issues in SFDO-Community/UnsubscribeLink

Similar issues

More Release issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.