-# Creating an anchor in Markdown
+# Creating an [[anchor]] in Markdown
-Is it a native Markdown "tag" for creating an anchor? Unfortunately,
+Is it a native Markdown "tag" for creating an [[anchor]]? Unfortunately,
I haven't any information about it at
[Markdown syntax](http://daringfireball.net/projects/markdown/syntax) page.
--[[Paweł|ptecza]]
+> Just found out that headers are already indexed with `index1h1 ... indexMhN`.
+> So one can link to headings with `\[[page|#index2h3]]` for example.
+> It would be much easier though if it was translated to the heading's name,
+> so on could to `\[[page#name]]`. --Timoses
+
+>> That's [[plugins/headinganchors]]. --smcv
+
> No such syntax exists in markdown. ikiwiki could certainly have a
> [[preprocessor_directive|directive]] for it, though.
> --[[JoshTriplett]]
>> Fixed that --[[Joey]]
+>>> Sorry to bring this up (1 year since last change in this page) but what is the status of this? Can we use anchors like it's in [[wikilink]]? This discusion is tagged as wishlist, but isn't listed in [[wishlist]]. What is "fixed that" then? Again, sorry if this is a dead issue, but I have a tendency to create big wiki pages, and anchors are very needed for me, but I've spent all morning trying to make it work and it just doesn't. TY. --rbern
+
+The 'name' attribute of the 'a' element is a depracated way to create a named anchor. The right way to do that is using the 'id' attribute of any element. This is because an anchor may refer to a complete element rather than some point in the page.
+
+Standard purity aside, if you define an anchor (using either 'a name' or 'id') to a single point in the document but refer to a complete section, the browser may just show that specific point at the bottom of the page rather than trying to show all the section.
+--[[tzafrir]]
+
---
Considering a hierarchy like `foo/bar/bar`, I had the need to link from the
> Not yet. :-) Any suggestion for a syntax for it? Maybe something like \[[|foobar]] ? --[[Joey]]
I like your suggestion because it's short and conscise. However, it would be nice to be able to refer to more or less arbitrary meta tags in links, not just "title". To do that, the link needs two parameters: the page name and the tag name, i.e. \[[pagename!metatag]]. Any sufficiently weird separater can be used instead of '!', of course. I like \[[pagename->metatag]], too, because it reminds me of accessing a data member of a structure (which is what referencing a meta tag is, really). --Peter
+
+> I dislike \[[pagename->metatag]] because other wikis use that as their normal link/label syntax.
+> I'm not sure that it is a good idea to refer to arbitrary meta tags in links in the first place - what other meta tags would you really be interested in? Description? Author? It makes sense to me to refer to the title, because that is a "label" for a page.
+> As for syntax, I do like the \[[|foobar]] idea, or perhaps something like what <a href="http://www.pmwiki.org">PmWiki</a> does - they have their links the other way around, so they go \[[page|label]] and for link-text-as-title, they have \[[page|+]]. So for IkiWiki, that would be \[[+|page]] I guess.
+> --[[KathrynAndersen]]
+
+----
+
+I am thinking that it would be useful to parse parts of one wiki page into another. Here something like `\[[page=anchor]]` would be really nice to simply parse the content of that section, as opposed to `\[[page#anchor]]` which only creates a link to that section. -- [[Timoses]]
+
+> When you say "parse parts" do you mean taking a section of a wiki page and including its text
+> in a different wiki page? So for instance you might want `/installation` to include the
+> `Downloading binaries` section of `/download`, but not the rest of that page?
+>
+> That's really a separate feature request (inlining isn't linking), and is also rather difficult
+> to do in IkiWiki's processing model: at the time that [[wikilinks|ikiwiki/wikilink]] and
+> [[directives|ikiwiki/directive]] are processed, the page content is still Markdown or
+> whatever other format is relevant, not HTML. That makes sections difficult to identify.
+>
+> I would suggest making the desired section a separate page (for example you might
+> call it `/download/binaries`), and including that whole page everywhere it should
+> appear (for example in both `/download` and `/installation`) using
+> `\[[!inline pages="download/binaries" raw=yes]]`. --[[smcv]]