Use slug cleanup for publishing paths
A permalink problem is different from a markup problem even when both start with plain text.
The current text section focuses on three practical publishing tasks: preview simple Markdown as HTML, clean small HTML snippets into Markdown-like text, and turn headings into URL slugs.
Decision layer
The visible text catalog is intentionally narrow. It focuses on URL slugs and markup conversion, so the category should frame those jobs directly instead of pretending to be a full writing toolkit.
A permalink problem is different from a markup problem even when both start with plain text.
Markdown-to-HTML and HTML-to-Markdown solve opposite publishing boundaries.
These routes remove mechanical cleanup work but do not replace content review or style decisions.
The maintained text category is stronger when it groups the visible tools around publishing decisions instead of acting like a generic text playground.
Publishing
Use the slug route for the path layer, not for broader editorial cleanup that belongs in the CMS.
Markup
Use a markup route when the structure needs to cross tools, docs systems, or CMS boundaries.
Open a direct text route when the publishing boundary is already obvious.
You need a URL-safe permalink from a finished title
Open Text to SlugUse the slug route when the goal is path cleanup rather than content editing.
You need to preview or move Markdown into an HTML surface
Open Markdown to HTMLGo directly to the markup converter when the source format is already settled.
You pasted HTML but need a Markdown-friendly version back
Open HTML to MarkdownUse the reverse route when the publishing flow moves from rendered markup back to editing text.
These pages represent the currently maintained text routes and define the real scope of the visible text category.
Use these guides when the next route is still unclear or you need adjacent workflow context first.
These sections stay aligned to the live tools in text tools. They explain the tasks users can actually complete on the visible pages today.
Use Markdown to HTML when the source is a short note, docs fragment, or CMS snippet that fits the current lightweight Markdown subset. This route is useful for browser-side previewing when you want to see simple headings, emphasis, links, and line breaks become readable HTML without opening a larger editor. The category page now frames that tool honestly as a quick publishing helper for small content blocks, not as a full Markdown engine for every document shape.
Recommended tools: Markdown to HTML, HTML to Markdown, Text to Slug
HTML to Markdown is the reverse cleanup route for copied snippets that still carry light markup from a CMS, email draft, or docs fragment. It works best when the HTML is short and made of common tags, because the point is to recover something readable and editable quickly. That is a narrower and more useful promise than pretending the page rebuilds full layouts, nested structures, or complex semantic HTML into perfect Markdown every time.
Recommended tools: HTML to Markdown, Markdown to HTML, Text to Slug
Text to Slug belongs in the same category because publishing work often ends with a title that still needs a clean URL token. The tool is useful for turning a heading, post title, or label into a lowercase hyphenated draft that is easier to reuse in links or filenames. On this category page, the slug workflow is described as a simple final cleanup step, not as a multilingual CMS policy engine or a full SEO suite for every naming rule on the web.
Recommended tools: Text to Slug, Markdown to HTML, HTML to Markdown
These tools also work well together in sequence. A user can clean copied HTML into editable Markdown-like text, preview the revised Markdown as HTML, and then generate a slug from the final title without leaving the browser. That gives the text category a real aggregation role even though it only surfaces three tools today. The page becomes a compact publishing workflow hub rather than a thin archive that still talks about hidden case converters or retired text utilities.
Recommended tools: HTML to Markdown, Markdown to HTML, Text to Slug
The visible text category is intentionally narrow. It now centers on markup preview, markup cleanup, and slug drafting because those are the routes users can actually open from this page today. Keeping the category copy aligned to the retained tools makes the hub easier to trust, easier to scan, and more useful for search intent. It also avoids the old problem where category language promised a much broader text toolbox than the primary display surface was willing to show.
Recommended tools: Markdown to HTML, HTML to Markdown, Text to Slug