Welcome to the ChipPrep Blog (Placeholder)
A short placeholder post that exists only to verify the MDX rendering pipeline. Real articles will replace this.
This is a placeholder post used during development to confirm that the MDX rendering pipeline produces the styling we want. It is not a real article and will be removed or replaced once real content ships.
A heading two for sectioning
Inline code looks like this: always @(posedge clk). It should render
with a soft blue chip background and no surrounding smart quotes.
A heading three for sub-sections
Below is a fenced Verilog code block. Shiki should syntax-highlight it
using the github-dark-dimmed theme and the dark wrapper from
globals.css should frame it.
module dff (
input wire clk,
input wire rst_n,
input wire d,
output reg q
);
always @(posedge clk or negedge rst_n) begin
if (!rst_n)
q <= 1'b0;
else
q <= d;
end
endmoduleA bulleted list — three items:
- One item
- Another item with a link to the practice page
- A third item
A numbered list — three steps:
- First, read the spec twice before writing any RTL.
- Second, draw the block diagram on a whiteboard.
- Third, code the sequential logic before the combinational logic.
A blockquote, just to verify the left-rule and italics:
If the data path is too slow, you fix the data path — never the clock.
That is every element the design system needs to render. Below this paragraph is the reusable CTA component, dropped straight into MDX:
Practice 400+ real hardware interview questions
Stop reading — start drilling. ChipPrep has VLSI, RTL, STA, SystemVerilog, and physical-design questions used at Intel, Qualcomm, Apple, NVIDIA, and Arm. Answers are graded by AI.
Start practicing →