🚀 major: nuxt 3 version #52
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This version will act as the main documentation plus live example for all Elements
📝 docs: add about.md and index.md to the content directory ✨ feat(docs): create dynamic route for displaying content documents The package.json file has been updated to use the latest version of Nuxt (3.6.5) to ensure compatibility and take advantage of any bug fixes or new features. Two new markdown files, about.md and index.md, have been added to the content directory to provide content for the application. Additionally, a new dynamic route has been created in the docs directory to display the content documents using the ContentDoc component.
📝 docs(about.md): add about page 📝 docs(index.md): add index page 🔥 delete(docs/[...slug].vue): remove unused file ✨ feat(docs/index.vue): create index page with content slot and SEO meta tags The trailing whitespace in the package.json file was removed for consistency and cleanliness. The about.md and index.md files were added to the docs folder to provide content for the about and index pages respectively. The unused file docs/[...slug].vue was deleted as it was no longer needed. The docs/index.vue file was created with a content slot and SEO meta tags to enhance the functionality and search engine optimization of the page.
…ity and functionality 🚀 feat(index.vue): add a greeting and include the about page content The about.md file now includes front matter (title and description) to provide metadata about the page. Additionally, a code block has been added to demonstrate a specific code snippet. In the index.vue file, a greeting has been added and the about page content is now included using the ContentDoc component. This improves the readability and functionality of the about page.
🔧 chore(nuxt.config.js): reformat gtag object for better readability 🔧 chore(nuxt.config.js): reformat head object for better readability 🔧 chore(nuxt.config.js): reformat daisyui themes array for better readability 🔧 chore(tailwind.config.js): remove unused colors from the colors object 🔧 chore(tailwind.config.js): remove unused themes from the daisyui themes array 🔧 chore(tailwind.config.js): reformat primary and secondary colors in the light theme object 🔧 chore(tailwind.config.js): reformat primary and secondary colors in the dark theme object 🔧 chore(tailwind.config.js): remove unused plugins array 🔧 chore(tailwind.config.js): remove unused darkMode property 🔧 chore(tailwind.config.js): remove unused fontFamily property 🔧 chore(tailwind.config.js): remove unused extend object 🔧 chore(tailwind.config.js): remove unused code block in the body selector 🔧 chore(tailwind.config.js): remove unused import statement for Inter font 🔧 chore(tailwind.config.js): remove unused import statement for Google Fonts 🔧 chore(tailwind.config.js): remove unused import statement for Line Awesome font 🔧 chore(tailwind.config.js): remove unused import statement for JetBrains Mono font 🔧 chore(tailwind.config.js): remove unused import statement for tailwind base, components, and utilities 🔧 chore(tailwind.config.js): remove unused import statement for custom fonts 🔧 chore(tailwind.config.js): remove unused import statement for bg-base-100 class 🔧 chore(tailwind.config.js): remove unused import statement for normal-case and font-semibold classes 🔧 chore(tailwind.config.js): remove unused import statement for btn class 🔥 delete(about.md): remove about.md file from src/content directory 🔥 delete(about.md): remove about.md file from src/content/docs directory 🔥 delete(index.md): remove index.md file from src/content/docs directory 🔥 delete(index.md): remove index.md file from src/content directory The changes in the configuration files were made to improve readability and remove unused code. The modules array in
The Node.js version specified in the .nvmrc file has been updated from 16 to 18. This change was made to ensure compatibility with the latest features and improvements in Node.js version 18.
…tement 🔀 refactor(Default.vue): remove unused THEMES array and console.warn statement The THEMES array is no longer used in the component, so it has been removed to improve code cleanliness. The console.warn statement has also been removed as it is no longer necessary.
…ment The THEMES constant is no longer used in the component, so it has been removed to improve code cleanliness. The console.warn statement has also been removed as it is no longer necessary.
…color for better visual consistency 🔧 chore(index.vue): update metaTitle and metaDescription for improved SEO and branding The text color of "Stripe" in the heading has been updated to use the primary color, providing better visual consistency with the rest of the design. The metaTitle and metaDescription have been updated to improve SEO and branding. The new metaTitle is "Home - Vue Stripe" and the new metaDescription is "Vue.js components and composables for Stripe Checkout, Elements, and more."
🆕 Add a new component called demo.vue to the docs directory. This component represents a demo page and includes a main section with an h1 heading. It also imports and uses the `useSeoMeta` and `definePageMeta` functions from the `#imports` module to define the page's metadata, including the layout, meta title, meta description, and Twitter card type. 🔄 Update the index.vue component in the docs directory. The main section now has a class of "bg-base-200" for styling purposes. The h1 heading has been changed to "Getting Started". The `useSeoMeta` and `definePageMeta` functions are also updated to reflect the new meta title and meta description for the page. 🆕 Add a new component called partners.vue to the pages directory. This component represents a partners page and includes a main section with an h1 heading. It also imports and uses the `useSeoMeta` and `definePageMeta` functions from the `#imports` module to define the page's metadata, including the layout, meta title, meta description, and Twitter card type. The changes were made to improve the documentation pages of the Vue Stripe application. The new demo page provides a template for showcasing demos, while the updated index page and the new partners page have improved metadata for better search engine optimization and social media sharing.
…ement, Link Authentication Element, and Payment Element The commit adds four new Vue components: Address Element, Express Checkout Element, Link Authentication Element, and Payment Element. These components are part of the documentation pages for Vue Stripe Components. Each component defines its own page meta, including title and description, and uses the `useSeoMeta` and `definePageMeta` functions from the `#imports` module to set the SEO metadata. This addition enhances the documentation by providing examples and explanations for these specific components.
- Added new files: use-checkout.vue, use-constants.vue, use-elements.vue, use-payment-element.vue, use-stripe.vue - Each file represents a different composable component for Vue Stripe Components - Each file includes a template with a main heading and a script section - The script section imports necessary dependencies and defines page metadata using the useSeoMeta and definePageMeta functions - The metadata includes title, description, and Twitter card information for each composable component These new composable components were added to provide additional functionality and flexibility to Vue Stripe Components. They allow for easier integration and customization of Stripe payment functionality in Vue.js applications.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This version will act as the main documentation plus live example for all Elements