Yes. The base page owns the syntax highlighter, typically Prism, Shiki, or Highlight.js. Selector mapping injects the snippet text into a code element with the language class derived from a paired language column. The highlighter runs at render time on every /tutorial/{slug}/, so every lesson uses the same theme and language coverage with no per-lesson configuration drift.

Carry snippets as an array column with each entry containing language, filename, and code separated by delimiters. List mapping renders each entry as its own pre and code block with a filename heading. For lessons with three or four snippets this works cleanly. For lessons with fifteen interleaved snippets, write the body in HTML in a content column and let it carry the structure.

Yes, that is the JSON-file source pattern. Check a curriculum.json file into the theme repo. Adding or reordering a lesson is a pull request that includes the row change. Engineering review catches breakages before they hit prod, and git history is the audit log. Editorial teams who prefer Sheets can use that, but engineering-led tutorial sites benefit from in-repo JSON next to the example code.

Both come from columns. Prerequisites is a pipe-separated list of slugs the lesson depends on. The next-lesson link reads from a single column. Reordering the curriculum is updating those columns. The structural pattern means a moved lesson updates its incoming and outgoing links once at the source, not in every Gutenberg block on every affected post.

Yes. Add HowTo JSON-LD to the base page for step-driven lessons or Course JSON-LD for the overall curriculum hub. Each schema block reads fields from the row via selector or meta mappings. Validate once with the Rich Results Test, then trust the structural pattern: every lesson ships consistent schema because every lesson reads the same template.

Carry a minutes column and a level column (Beginner, Intermediate, Advanced). Surface them as pills near the lesson title via selector mapping. Sort the curriculum by minutes for an audit of suspicious estimates, and use both fields in HowTo JSON-LD's totalTime and educationalLevel properties for richer search results.

No. The lesson body, code, and explanations come from your team. SleekRank places the content into the template. Pair with SleekAI to draft initial outlines, but a subject-matter expert should always review before publishing. The plugin's value is removing the publishing friction so authoring focuses on substance, not on managing the lesson library.

Add a status column with values like current, deprecated, archived. Filter the page group to only render current rows. Set up a 301 redirect from the deprecated URL to a replacement lesson via your redirect plugin. The deprecated row stays in the source as historical record while readers are routed to the canonical content for that topic.