feat!: Rename frontend -> frontend-plugin-sample

Why?

* frontend-plugin- is a fairly common prefix for plugins using
  Frontend Plugin Framework
* By including the word `sample`, it's more obvious for users of this
  repo how to adapt it into their own backend plugin (by replacing
  all occurances of "sample")
* When we include a frontend-base "plugin", we'll use the prefix
  frontend-app- (note that, in frontend-base all plugins are actually
  just apps).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Author: kdmccormick

.github/workflows/release.yml

@@ -151,12 +151,12 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v6
         with:
-          node-version-file: './frontend/.nvmrc'
+          node-version-file: './frontend-plugin-sample/.nvmrc'
 
       - name: Update the package version and publish
         run: |
           npm install --include=dev
           npm version ${{ needs.release.outputs.version }}
           npm run build
           npm publish
-        working-directory: './frontend'
+        working-directory: './frontend-plugin-sample'

CLAUDE.md

@@ -14,7 +14,7 @@ This is a **sample plugin repository** that demonstrates all major Open edX plug
 
 **Repository Structure:**
 - `platform-plugin-sample/` - Django app plugin with models, APIs, events, and filters
-- `frontend/` - React component for MFE slot customization  
+- `frontend-plugin-sample/` - React component for MFE slot customization  
 - `tutor/` - Tutor plugin for easy deployment
 - Each directory has comprehensive README.md files with TOCs
 
@@ -30,7 +30,7 @@ This is a **sample plugin repository** that demonstrates all major Open edX plug
 - `platform-plugin-sample/openedx_sample_plugin/pipeline.py` - Open edX Filters implementation
 - `platform-plugin-sample/openedx_sample_plugin/models.py` - CourseArchiveStatus model (business logic)
 - `platform-plugin-sample/openedx_sample_plugin/views.py` - REST API endpoints consumed by frontend
-- `frontend/src/plugin.jsx` - React component that replaces course list slot
+- `frontend-plugin-sample/src/plugin.jsx` - React component that replaces course list slot
 - `tutor/openedx_sample_plugin.py` - Deployment configuration (currently basic template)
 
 ## Build/Lint/Test Commands
@@ -61,7 +61,7 @@ Always run `make quality` and fix issues before creating a PR to ensure consiste
 - **Realistic Complexity**: Keep examples practical but not overly complex
 
 ### Code Relationships to Preserve
-- **Backend ↔ Frontend**: CourseArchiveStatus API in `views.py` consumed by `frontend/src/plugin.jsx`
+- **Backend ↔ Frontend**: CourseArchiveStatus API in `views.py` consumed by `frontend-plugin-sample/src/plugin.jsx`
 - **Events ↔ Models**: Signal handlers in `signals.py` can update models in `models.py`
 - **Settings ↔ Filters**: Filter registration in `settings/common.py` must match classes in `pipeline.py`
 - **Apps.py ↔ All**: Plugin configuration affects URL routing, settings, and signal registration

README.md

@@ -32,7 +32,7 @@ This sample plugin showcases the **Open edX Hooks Extension Framework**, which a
 | **Django App Plugin** | Add models, APIs, views, and business logic | [How to create a plugin app](https://docs.openedx.org/projects/edx-django-utils/en/latest/plugins/how_tos/how_to_create_a_plugin_app.html) | [`platform-plugin-sample/`](./platform-plugin-sample/) | Adding new functionality, APIs, or data models |
 | **Events (Signals)** | React to platform events | [Open edX Events Guide](https://docs.openedx.org/projects/openedx-events/en/latest/) | [`platform-plugin-sample/openedx_sample_plugin/signals.py`](./platform-plugin-sample/openedx_sample_plugin/signals.py) | Integrating with external systems, audit logging |
 | **Filters** | Modify platform behavior | [Using Open edX Filters](https://docs.openedx.org/projects/openedx-filters/en/latest/how-tos/using-filters.html) | [`platform-plugin-sample/openedx_sample_plugin/pipeline.py`](./platform-plugin-sample/openedx_sample_plugin/pipeline.py) | Customizing business logic, URL redirects |
-| **Frontend Slots** | Customize MFE interfaces | [Frontend Plugin Slots](https://docs.openedx.org/en/latest/site_ops/how-tos/use-frontend-plugin-slots.html) | [`frontend/`](./frontend/) | UI customization, adding new components |
+| **Frontend Slots** | Customize MFE interfaces | [Frontend Plugin Slots](https://docs.openedx.org/en/latest/site_ops/how-tos/use-frontend-plugin-slots.html) | [`frontend-plugin-sample/`](./frontend-plugin-sample/) | UI customization, adding new components |
 | **Brand Packages** | Customize theming | [Open edX Brand Package Interface](https://github.com/openedx/brand-openedx) | [`brand/`](./brand/) | UI theming |
 | **Tutor Plugin** | Deploy plugins easily | [Tutor Plugin Development](https://docs.tutor.edly.io/) | [`tutor/`](./tutor/) | Simplified deployment and configuration |
 
@@ -55,8 +55,8 @@ tutor mounts add "$PWD/platform-plugin-sample"
 tutor dev launch  
 
 # Frontend Plugin Setup (for learner-dashboard MFE development)
-npm install $PWD/frontend
-# Add env.config.jsx and module.config.js (see frontend/README.md)
+npm install $PWD/frontend-plugin-sample
+# Add env.config.jsx and module.config.js (see frontend-plugin-sample/README.md)
 npm start
 ```
 
@@ -94,7 +94,7 @@ Use the table above to identify which type of plugin matches your needs. You can
 - **Backend**: Start with [`platform-plugin-sample/openedx_sample_plugin/apps.py`](./platform-plugin-sample/openedx_sample_plugin/apps.py) to understand plugin registration
 - **Events**: Examine [`platform-plugin-sample/openedx_sample_plugin/signals.py`](./platform-plugin-sample/openedx_sample_plugin/signals.py) for event handling patterns
 - **Filters**: Review [`platform-plugin-sample/openedx_sample_plugin/pipeline.py`](./platform-plugin-sample/openedx_sample_plugin/pipeline.py) for behavior modification
-- **Frontend**: Explore [`frontend/src/plugin.jsx`](./frontend/src/plugin.jsx) for UI customization
+- **Frontend**: Explore [`frontend-plugin-sample/src/plugin.jsx`](./frontend-plugin-sample/src/plugin.jsx) for UI customization
 
 ### 4. Run This Sample
 Follow the [Quick Start Guide](#quick-start-guide) to see everything working together.
@@ -118,7 +118,7 @@ sample-plugin/
 │   │   ├── settings/                  # Plugin settings configuration
 │   │   └── urls.py                    # URL routing
 │   └── tests/                         # Comprehensive test examples
-├── frontend/
+├── frontend-plugin-sample/
 │   ├── README.md                      # Frontend plugin detailed guide
 │   ├── src/
 │   │   ├── plugin.jsx                 # React component for MFE slot
@@ -148,11 +148,11 @@ sample-plugin/
 
 1. **Setup**: Follow frontend setup in [Quick Start](#quick-start-guide)
 2. **Development**:
-   - Modify React components in `frontend/src/`
+   - Modify React components in `frontend-plugin-sample/src/`
    - Test with local MFE development server
 3. **Testing**: Integration testing with MFE
 
-**Detailed Guide**: See [`frontend/README.md`](./frontend/README.md)
+**Detailed Guide**: See [`frontend-plugin-sample/README.md`](./frontend-plugin-sample/README.md)
 
 ### Full-Stack Plugin Development
 
@@ -174,7 +174,7 @@ class CourseArchiveStatusViewSet(viewsets.ModelViewSet):
 ```
 
 ```jsx
-// frontend/src/plugin.jsx - Consumes API
+// frontend-plugin-sample/src/plugin.jsx - Consumes API
 const response = await client.get(
   `${lmsBaseUrl}/sample-plugin/api/v1/course-archive-status/`
 );

frontend/.gitignore frontend-plugin-sample/.gitignorefrontend/.gitignore renamed to frontend-plugin-sample/.gitignore

@@ -314,7 +314,7 @@ if (response.data && Array.isArray(response.data)) {
 
 ```bash
 # In your MFE directory (e.g., frontend-app-learner-dashboard)
-npm install /path/to/sample-plugin/frontend
+npm install /path/to/sample-plugin/frontend-plugin-sample
 ```
 
 #### Step 2: Create env.config.jsx
@@ -356,7 +356,7 @@ module.exports = {
   localModules: [
     {
       moduleName: '@openedx/sample-plugin',
-      dir: '/path/to/sample-plugin/frontend'
+      dir: '/path/to/sample-plugin/frontend-plugin-sample'
     },
   ],
 };