This commit introduces adjustments to several UI elements, including title alignment, font sizes, and avatars loading. The updates aim to improve the overall visual appeal and user experience on the website. In addition, better error handling has been added to form inputs, including adding unique error IDs for each form's email input to enhance user feedback and accessibility.
Refactored multiple Astro UI components, including sections, buttons, and modals, with a focus on code cleanliness and efficiency. This included revising import statements, reordering and redefining CSS classes, and updating HTML elements. Enhanced inline comments to add context and explanations, especially registering the purpose of components and properties for improved understanding. The Accordion-related functionality was removed, pointing towards a redesign of its element usage. Moreover, TestimonialsSection2 was renamed to TestimonialsSectionAlt for better semantics.
The changes made include code refactoring and reformatting in several files for better readability, and to adhere to best practices. Detailed and intuitive comments were added to the code, improving clarity and understanding of the codebase. There were also some class adjustments and minor changes in several files ranging from reordering class listings to updating element selections. Import statements were also modified for clarity. Accordion functionality was removed, potentially indicating a pending replacement or enhancement.
Several component files have been refactored to improve code clarity and ease of maintenance. This includes introducing comprehensive comments explaining the functionality and purpose of sections of the code, as well as leveraging Astro.js for more streamlined data sourcing. The commit also includes the removal of redundant files from the vendor scripts directory as part of a general clean-up, improving overall codebase organization.
This commit refactors multiple component files for better understandability and maintainability. Detailed comments are added for enhanced readability. The data source is defined using Astro.js to simplify the process of acquiring data for the components. Unnecessary files like 'preline.js' from the vendor scripts directory are deleted as part of clean-up.
A new category called "Insights" has been added to the blog. New components such as individual insights page layout and individual insights card have been added. The new components also include astro content files for individual insight articles. This provides users with more in-depth information and can potentially increase user engagement.
Code has been updated to include insights as a new category of blog posts. Each blog post now also includes a related articles section at the bottom. The new feature enriches the content offering for users and potentially increases user engagement. The code has also been cleaned up for readability and consistency, improving maintainability long term.
A conditional chaining operator has been added while mapping over post data tags to handle cases where the 'tags' field might not be present. This prevents the application from crashing in case 'tags' is undefined for a particular blog post.
This code introduces new Astro components for the blog pages and avatar elements, along with their corresponding layout and display factors. It also includes relevant asset imports, formatting utility functions, and mapping of blog content collection for dynamic content presentation.
Replaced the image components with card components in the product section to enhance product display. Modified the grid layout for enhanced product representation. Also, implemented the complete functionality of the blog section by defining the blog collection, adding blog cards and content, and refining meta data in MainLayout for SEO optimization. Adjusted animation timeline and script paths for better load performance.
Updated 'src/pages/products/[...slug].astro' to conditionally render product images only when they exist. Prevents potential errors or breaks in layout when there is an absence of either 'first' or 'second' blueprint images for a particular product.
Introduced a new astro file 'src/pages/products/[...slug].astro' to handle individual product pages. This file imports necessary components and templates the main layout of a product page. The layout includes methods for fetching products, providing static paths, and scripts for page interactivity.
The 'prod.astro' page is deleted as a part of refactoring process. Also, title, src, alt, and url properties of ImgSmall and ImgWide components are now optional, which provides greater flexibility and reduces risk of errors when these components are used in various parts of application.
Product information previously stored in JSON files has been migrated to Markdown format for efficient content management. Additionally, added a new button component for 404 pages to improve navigation and user experience. Defined a new schema for product collections and included GSAP JavaScript library for future animations.
The paths referencing images in the product page were corrected. Initial paths were relative to the current file but they should be relative to the root directory, thus an additional navigation step with "../" was added for each import statement.
Removed blog and product pages and moved their contents to new blog and product directories, respectively. Added a new 404 error page for invalid routes. Updated server configurations in 'vercel.json' to leverage additional security by adding 'cdnjs.cloudflare.com' to Content-Security-Policy headers.
The new product file "b203.json" was added to the product description containing detailed descriptions, features and product aspects. In the "prod.astro" file, a product details page was implemented, which fetches data from the JSON file and presents it to the user. The changes also included the development of a "ProductTabBtn" component to improve code modularity and the user interface.
Refactored the image URL in testimonials and reduced redundancy in the FeaturesStats and accordion components, enhancing code readability. Also, implemented dynamic id generation in the FAQ component, improving scalability and maintainability. Added new pages to the website and updated the meta information, improving SEO.
Due to design changes, removed old authentication components and related configuration settings in .idea and .vscode folders. Changes include elimination of subscription input, email input, login and register modals, and user interface blocks. All changes aim to clean up the codebase and eliminate unused or unnecessary code.
Simplified image handling configuration in the "astro.config.mjs" by removing explicit sizing. Updated text sizing of PrimaryCTA and SecondaryCTA components to scale responsively in 2xl views. Aimed to improve the user interface and experience on larger screens.
Introduce an SVG icon to the project and establish a new web manifest containing app details and icon information. Add a Meta component to serve structured site metadata for better web presentation and search engine optimization. Include a new robot.txt to instruct web crawlers. The addition of these elements promotes better site recognition and SEO, enhancing user navigation and experience.
Refactored the names of the Testimonials and Pricing components to TestimonialsSection and PricingSection for better understanding. Also fixed the lack of newline at the end of file in SecondaryCTA component.
In this commit, the 'Clients' component has been renamed to 'ClientsSection' for improved clarity. Additionally, the formatting of comment blocks across multiple .astro files has been adjusted to keep the cade cleaner and more uniform across the project.
The index.astro page has been updated with the addition of several new components to provide more reusable structures. These components include MainLayout, Navbar, HeroSection, Clients, FeaturesGeneral, FeaturesNavs, Testimonials, Pricing, and FAQ, to form the structure of the landing page.
This commit includes the introduction of Astro project setup files, including the configuration. The main change is the addition of the configuration file `astro.config.mjs`, where Tailwind is set up for Astro integration. It also adds `.gitignore` files, a `package.json`, and setup files for VSCode and IntelliJ IDEA. The project includes a favicon and a simple Astro page. It comes with a `package-lock.json` file which locks down the versions of each dependency ensuring that installs generate the exact same tree across machines.
