Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,81 @@
---
title: 'Interview questions in 2026: A Practical Guide'
description: 'A comprehensive guide to interview questions for modern frontend development in 2026.'
date: '2026-07-03'
tags: ['Interview questions', 'Frontend', '2026']
published: true

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: This post is added under content/blog-post-2026-07-03, but the content collection only indexes content/blog/**/*.mdx, so this article will never be loaded or rendered even though it is marked published. Move it into the indexed content/blog/ tree (and matching image location) so it is actually shipped. [incomplete implementation]

Severity Level: Critical 🚨
- ❌ Blog listing omits this published interview guide.
- ❌ Homepage latest posts never include this article.
- ❌ Article missing from RSS feed and sitemap output.
- ⚠️ Tags page ignores tags defined for this post.
Steps of Reproduction ✅
1. The Velite content config at `velite.config.ts:11-28` defines the `posts` collection
with `root: 'content'` and `pattern: 'blog/**/*.mdx'`, so only files under `content/blog/`
matching `**/*.mdx` are indexed into `#site/content`.

2. This PR adds the article file at
`content/blog-post-2026-07-03/interview-questions-in-2026-a-practical-guide.mdx` with
frontmatter `published: true` at line 6 in the diff, placing it under
`content/blog-post-2026-07-03/` instead of the indexed `content/blog/` tree.

3. When the Next app builds and imports `posts` from `#site/content` (for example in
`app/blog/page.ts:1-7` and `app/page.ts:3,95-107`), Velite only includes MDX files
matching `blog/**/*.mdx`, so this new article is absent from the `posts` array despite
being marked published.

4. At runtime, visiting `/blog` (`app/blog/page.ts:27-93`), `/` (`app/page.ts:94-129`),
`/tags` (`app/tags/page.tsx:15-32`), the RSS feed `/feed.xml`
(`app/feed.xml/route.ts:3-32`), or individual blog routes
(`app/blog/[...slug]/page.ts:71-80`) shows that this article never appears in listings,
feeds, sitemap entries, or static post pages because it is not indexed.

Fix in Cursor Fix in VSCode Claude

(Use Cmd/Ctrl + Click for best experience)

Prompt for AI Agent 🤖
This is a comment left during a code review.

**Path:** content/blog-post-2026-07-03/interview-questions-in-2026-a-practical-guide.mdx
**Line:** 6:6
**Comment:**
	*Incomplete Implementation: This post is added under `content/blog-post-2026-07-03`, but the content collection only indexes `content/blog/**/*.mdx`, so this article will never be loaded or rendered even though it is marked published. Move it into the indexed `content/blog/` tree (and matching image location) so it is actually shipped.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix
👍 | 👎

image: './images/post-image.png'
---

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Referenced image asset is missing

The frontmatter specifies image: './images/post-image.png', but no images/ directory or image file was added alongside this MDX file. Other posts (e.g., in content/blog/) include a corresponding image directory. If the directory issue is resolved and the post is moved into content/blog/, the build will fail or the image will render as broken unless ./images/post-image.png is also committed.


Comment on lines +1 to +9

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Post will never be rendered — wrong content directory

The Velite config (velite.config.ts) collects posts with the pattern blog/**/*.mdx under the content/ root, meaning only files inside content/blog/ are indexed. This file lives in content/blog-post-2026-07-03/, which does not match that glob. At build time, Velite will silently ignore it — the post will not appear in the blog listing, will not be routable at /blog/..., and will not be included in the sitemap or RSS feed. Move the file to content/blog/interview-questions-in-2026-a-practical-guide.mdx to match the collection pattern.

Comment on lines +1 to +9

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Duplicate slug with an existing post

A file with the identical name interview-questions-in-2026-a-practical-guide.mdx already exists at content/blog-post-2026-06-09/. If both files were ever moved into content/blog/, they would share the same slugAsParams value, causing Velite to produce two entries that map to the same URL — resulting in unpredictable routing behavior (whichever entry is found last would win). The two posts should be deduplicated or one should be renamed.

# Interview questions in 2026: A Practical Guide

Interview questions continues to evolve in 2026, and staying current with the latest patterns and best practices is essential for building modern, performant web applications. In this guide, we'll explore practical techniques you can implement today.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: There is an obvious grammar typo: the singular verb does not agree with the plural subject, which reduces content quality in a published article; update the sentence to proper subject-verb agreement. [typo]

Severity Level: Minor 🧹
- ⚠️ Blog article text contains visible grammar mistake.
- ⚠️ Reduces perceived quality of interview guide content.
Steps of Reproduction ✅
1. Inspect the MDX source for the new post at
`content/blog-post-2026-07-03/interview-questions-in-2026-a-practical-guide.mdx` and
locate line 12 in the diff, which contains the sentence starting with `Interview questions
continues to evolve in 2026`.

2. Observe that the grammatical subject `Interview questions` is plural, while the verb
form `continues` is singular, yielding incorrect subject verb agreement directly in the
stored article content.

3. Once the file is moved into the indexed `content/blog/` tree and included in `posts`
from `#site/content` (used in `app/blog/[...slug]/page.ts:75-110` to render `post.body`
via `MDXContent`), visiting the generated blog route for this article will render that
exact sentence at the top of the page.

4. On every view of this article page, the opening paragraph displays the subject verb
agreement error, reducing perceived professionalism of the interview guide content even
though functionality works.

Fix in Cursor Fix in VSCode Claude

(Use Cmd/Ctrl + Click for best experience)

Prompt for AI Agent 🤖
This is a comment left during a code review.

**Path:** content/blog-post-2026-07-03/interview-questions-in-2026-a-practical-guide.mdx
**Line:** 12:12
**Comment:**
	*Typo: There is an obvious grammar typo: the singular verb does not agree with the plural subject, which reduces content quality in a published article; update the sentence to proper subject-verb agreement.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix
👍 | 👎


## Why Interview questions Matters

Understanding interview questions is crucial for frontend developers who want to build responsive, accessible, and maintainable applications. Whether you're working on a small project or a large-scale enterprise application, these concepts apply.

## Key Concepts

### 1. Foundation Principles

The core principles behind interview questions remain consistent, but implementation details have evolved. Here's what you need to know:

```typescript
// Example of modern interview questions pattern
function useModernPattern() {
// Implementation example
return {
apply: () => {
console.log("Applying modern interview questions pattern");
}
};
}
```

### 2. Common Pitfalls to Avoid

- **Ignoring performance**: Always measure before optimizing
- **Over-engineering**: Start simple, add complexity when needed
- **Not following conventions**: Stick to established patterns in your codebase

### 3. Best Practices

1. Start with the basics before moving to advanced patterns
2. Test your implementations thoroughly
3. Document your code for future reference
4. Keep performance in mind throughout development

## Real-World Example

Here's a practical example you can adapt for your projects:

```typescript
// Real-world application example
interface Props {
data: string[];
onUpdate: (value: string) => void;
}

function Component({ data, onUpdate }: Props) {
return (
<div>
{data.map(item => (
<button key={item} onClick={() => onUpdate(item)}>
{item}
</button>
))}
</div>
);
}
```

## Conclusion

Interview questions is an essential skill for modern frontend developers. By understanding these patterns and implementing them in your projects, you'll build better applications that are more maintainable and performant.

Start with the basics, practice regularly, and gradually incorporate more advanced techniques into your workflow. The key is consistency and continuous learning.

---

Have questions or want to share your experience? Join the discussion in our community!
Comment on lines +11 to +81

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Content is unfilled template placeholder — no actual interview questions present

Despite the title promising "A Practical Guide" to interview questions, the body contains no interview questions whatsoever. Sentences like "Interview questions continues to evolve in 2026", section headings like "Foundation Principles behind interview questions", and code comments like "Applying modern interview questions pattern" are artifacts of a content template where a topic keyword was substituted verbatim without authoring real content. The TypeScript examples are completely generic and unrelated to interview preparation. Compare with the existing substantive post at content/blog-post-2026-06-09/interview-questions-in-2026-a-practical-guide.mdx, which covers React 19, Next.js 15 hydration, INP, and CSS Container Queries with worked answers. This file should not be published as-is.

Loading