Admin half in the fluentcms-plugin template
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Read docs/planning/admin-technical-spec.md sections 5.1, 6.2 and 10.4, then inspect templates/fluentcms-plugin and test-templates.sh. Confirm A-18 is available before implementing the manifest test; A-19 and A-22 are needed for the disabled-plugin acceptance check. Done means the generated template builds and tests with and without the admin half, its manifest test detects a removed contribution, and the referenced half uses only the two named FluentCMS packages.
Written by the indexing model from the issue text.
Description
Problem
Row 8.17 asks that the plugin template gives a working plugin. dotnet new fluentcms-plugin writes the server half only, so an author of a plugin has no example of an admin half, its manifest or its test.
Proposal
templates/fluentcms-plugingains{name}.Admin, a Razor Class Library that referencesFluentCMS.Admin.AbstractionsandFluentCMS.Admin.Componentsonly: a page with its menu item, a settings page for the plugin's area, a dashboard widget, its resources, andfluentcms-admin.json.- A test project with the manifest test of A-18 and one component test of the page.
- An option of the template leaves the admin half out, for a plugin without one.
test-templates.shbuilds and tests the output with and without the half.- The template's README says how an app references the half, since the first-party app holds the first-party halves only (6.3).
Acceptance
-
dotnet new fluentcms-pluginbuilds and its tests pass, with the admin half and without it - The half's manifest test passes as generated, and fails when a contribution is removed from the file
- An app that references the generated half shows its page, menu item, settings page and widget, and none of them in a site where the plugin is disabled (checked once A-19 and A-22 are merged, in the template's test or the end-to-end shard)
- The half references no FluentCMS package beside the two named
Design: docs/planning/admin-technical-spec.md, sections 5.1, 6.2 and 10.4 (A-23). Row 8.17. Needs A-18; the last acceptance row needs A-19 and A-22. Size: S.
- Dominant language
- C#
- Stars
- 569
- Forks
- 107
- Avg merge
- 2h 49m
- Merged PRs (30d)
- 397
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fluentcms/FluentCMS
-
area:host area:operations type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:build security type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:sdk security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:content security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area:build type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in fluentcms/FluentCMS
Similar issues
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
microsoft/microsoft-ui-reactor#1567 ·
Maintainers usually reply within 1 day
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw-windows-node#2287 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
kind:ux needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
elsa-workflows/elsa-foundation#4742 ·
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
enhancement good first issue help wanted new-language
Difficulty 2/5 1-3 hours Newbie friendliness 82/100