Dev.to

#wecode Landing Page - WeCoded Challenge March 2025

This is a submission for the WeCoded Challenge: Celebrate in Code Repository: deathcrafter / wecoded-landing React + TypeScript + Vite This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules. Currently, two official plugins are available: @vitejs/plugin-react uses Babel for Fast Refresh @vitejs/plugin-react-swc uses SWC for Fast Refresh Expanding the ESLint configuration If you are developing a production application, we recommend updating the configuration to enable type-aware lint rules: export default tseslint.config({ extends: [ // Remove ...tseslint.configs.recommended and replace with this ...tseslint.configs.recommendedTypeChecked, // Alternatively, use this for stricter rules ...tseslint.configs.strictTypeChecked, // Optionally, add this for stylistic rules ...tseslint.configs.stylisticTypeChecked, ], languageOptions: { // other options... parserOptions: { project: ['./tsconfig.node.json', './tsconfig.app.json'], tsconfigRootDir: import.meta.dirname, }, }, }) You can also… View on GitHub Preview: Covered: Look and feel. Functionality. Not covered: Responsiveness ARIA-based accessibility. Small things like navbar and footer as I felt like those are supposed to be handled by the platform, e.g. would be identical to the one in primary site.

Mar 8, 2025 - 06:07

This is a submission for the WeCoded Challenge: Celebrate in Code

Repository:

deathcrafter / wecoded-landing

React + TypeScript + Vite

This template provides a minimal setup to get React working in Vite with HMR and some ESLint rules.

Currently, two official plugins are available:

@vitejs/plugin-react uses Babel for Fast Refresh
@vitejs/plugin-react-swc uses SWC for Fast Refresh

Expanding the ESLint configuration

If you are developing a production application, we recommend updating the configuration to enable type-aware lint rules:

export default tseslint.config({
  extends: [
    // Remove ...tseslint.configs.recommended and replace with this
    ...tseslint.configs.recommendedTypeChecked,
    // Alternatively, use this for stricter rules
    ...tseslint.configs.strictTypeChecked,
    // Optionally, add this for stylistic rules
    ...tseslint.configs.stylisticTypeChecked,
  ],
  languageOptions: {
    // other options...
    parserOptions: {
      project: ['./tsconfig.node.json', './tsconfig.app.json'],
      tsconfigRootDir: import.meta.dirname,
    },
  },
})

You can also…

View on GitHub

Preview:

Covered:

Look and feel.
Functionality.

Not covered:

Responsiveness
ARIA-based accessibility.
Small things like navbar and footer as I felt like those are supposed to be handled by the platform, e.g. would be identical to the one in primary site.