To ensure newly added components integrate seamlessly and are properly visualized within the application, all steps below are mandatory. The steps may be completed in any order; however, each step must be followed for a successful contribution. A testing component, playground.vue
, is available to validate components under development without modifying the production configuration.
Important: Avoid merging or pushing changes to
playground.vue
, as it is intended solely for testing.
playground.vue
Use playground.vue
as a sandbox environment to build and validate your component’s functionality and styling. Here, you can interact with the component under real conditions, ensuring it behaves as expected before integration.
header
, your component should be 6.vue
)..vue
file, using the appropriate structure, conventions, and styling rules for the project..md
Documentation Filecontent/{element}/
directory, create a Markdown file with the same number as the component file (e.g., 6.md
if the component is 6.vue
)..md
file will utilize Nuxt Content to handle metadata (title, component number, description, and source code) for display.---
title: string
description: string
dark: boolean | false
animated: boolean | false
parent: string
component: number
preview: boolean | false
copied: boolean | false
---
```vue
<!-- Code here -->
```
.md
File.vue
component file and paste it into the .md
file inside Vue code blocks.```vue
<!-- Code here -->
```
/types/templates.ts
/types/templates.ts
.header
, footer
) to ensure proper typing and accessibility.export type FootersTemplates = '...' | '...' | '...' | 'new component name'
index.vue
for Component Loadingpages
directory and locate the folder for the target component type (e.g., header
, footer
).index.vue
file:
<!-- Example -->
<LazyElementsFooters6 v-if="..." />
After completing these steps, verify that:
Following this process will ensure your component is fully integrated and ready for use, with accessible source code and proper visualization.