Project requirements

[strangeTany]

[15] At least these four pages :

• [x] [1] Homepage (static content)
• [x] [1] About page (static content)
• [x] [8] Items collection list page (from CMS), e.g., list of blog posts
• [x] [5] Single item details page (from CMS), e.g., a single blog post

[strangeTany]

• [x] [10] CMS items’ forms have controls and validation (frontend) e.g., form field validation, error messages, or input masking

[strangeTany]

• [x] [10] Use SvelteKit or Next.js.

• Single Page Application (SPA) with Client-side Routing and prefetching.

• If you would like to use another framework, check with us first. It would need to meet the other SEO and deployment requirements.

[strangeTany]

[10] Use proper tools setup

• [ ] [5] Must use TypeScript, and follow best practices. e.g., not using any
• [x] [2] ESLint
• [x] [2] Prettier (or ESLint formatting rules)
• [x] [1] Valid and semantic HTML (W3 Validator).

[strangeTany]

• [x] [10] Deploy the SvelteKit project on Cloudflare pages, or Next.js on Vercel (or any other platform that meets the requirements.

• [ ] [5] Continuous Integration (CI). With linting and format checking at the minimum.

[strangeTany]

• [x] [2] Code formatting: Prettier and ESLint with formatting rules enabled.

• [x] [2] Editor configuration should include:

  • Format on save enabled.
  • Recommended extensions to have for project.
  • New line at the end of file.
  • Spacing configuration (tab size) compatible with Prettier.

• [x] [1] The editor configuration should be version controlled and used by all team members. i.e., the .vscode folder in git

[strangeTany]

• [ ] [2] CMS item pages should have unique and descriptive titles and (meta) descriptions.
• [ ] [1] Item pages have Open Graph previews (tags). i.e., pasting the link in Telegram shows the item’s title and description.
• [ ] [5] Use Server-side Rendering (SSR) to serve the dynamic pages HTML.

[strangeTany]

Bonuses:

• [ ] [2] Deployment of previews for pull requests in GitHub.

• [ ] [3] Feature Sliced Design (FSD). Should be demonstrated in presentation.

• [ ] [4] Server-side validation:

  • [ ] [2] Integrating the CRUD security rules with user authentication. e.g., Firebase security rules.
  • [ ] [2] Validating the data on the backend (security rules). e.g., Firebase security rules.

• [ ] [5] Testing (and piepeline step in CI).