On Sat, Mar 16, 2013 at 11:38 AM, Karen Coyle <[email protected]> wrote:
> Anand, is there any difference in the HTML/CSS that wraps them? I ask > because of that problem I ran into with editing the /developer pages -- > there is HTML there that displays the various developer links, and > that's not within the editable page. Presumably other pages would have > other HTML "wrappers". > If it's the nav bar that you're talking about, it's here: https://github.com/internetarchive/openlibrary/blob/master/openlibrary/plugins/upstream/macros/Subnavigation.html What needs to be changed besides the Launchpad link? I can create a pull request for Anand to merge. Tom > > kc > > On 3/16/13 8:30 AM, Anand Chitipothu wrote: > > No, they are essentially the same. Different types were used to allow > rendering the pages using different templates. At that time, it was the > only way to allow rending pages with different templates. We still have > that legacy. Ideally, we should convert all of them to /type/page and get > rid of all other types. > > > > Anand > > > > On 16-Mar-2013, at 9:32 AM, Karen Coyle wrote: > > > >> Ben, one difference seems to be that type/doc takes html markup, and > >> type/page uses MarkDown. When I look at the Infogami tutorial (type/doc) > >> in edit mode it appears as html. When I look at, say, the "Writing bots" > >> page (type/page) [1] I see what looks like MarkDown coding. > >> > >> I admit that I've never mastered MarkDown although, as with other wiki > >> markup rules, those who know it seem to love it. > >> > >> kc > >> [1] http://openlibrary.org/dev/docs/bots > >> > >> On 3/15/13 5:07 PM, Ben Companjen wrote: > >>> Hi Anand, all, > >>> > >>> I was wondering why there are separate types for "pages" and "docs". > >>> Both types have a title (a string) and a body (of type /type/text), > >>> but it seems that the text in a page is fully transformed from > >>> wikitext to HTML and docs are not, so that effectively, in docs only a > >>> subset of the wikitext is supported. > >>> > >>> I was doing a slight modification of the Infogami tutorial to make > >>> Firefox render it correctly, but noticed that a wikilink like > >>> [[/help]] was not turned into a link. However, the reason that Firefox > >>> underlined the whole table of contents when hovering over it was > >>> because <a ..></a> was transformed into <a/>. Linebreaks are also > >>> converted to <br>s (but possibly not always, must check this out a bit > >>> more). > >>> > >>> And then there is also /type/content (also just title and body), so > >>> I'm a bit confused with respect to the specific purposes that each of > >>> these types fulfill. > >>> > >>> Ben > >>> _______________________________________________ > >>> Ol-tech mailing list > >>> [email protected] > >>> http://mail.archive.org/cgi-bin/mailman/listinfo/ol-tech > >>> To unsubscribe from this mailing list, send email to > [email protected] > >>> > >> > >> -- > >> Karen Coyle > >> [email protected] http://kcoyle.net > >> ph: 1-510-540-7596 > >> m: 1-510-435-8234 > >> skype: kcoylenet > >> _______________________________________________ > >> Ol-tech mailing list > >> [email protected] > >> http://mail.archive.org/cgi-bin/mailman/listinfo/ol-tech > >> To unsubscribe from this mailing list, send email to > [email protected] > > > > > > -- > Karen Coyle > [email protected] http://kcoyle.net > ph: 1-510-540-7596 > m: 1-510-435-8234 > skype: kcoylenet > _______________________________________________ > Ol-tech mailing list > [email protected] > http://mail.archive.org/cgi-bin/mailman/listinfo/ol-tech > To unsubscribe from this mailing list, send email to > [email protected] >
_______________________________________________ Ol-tech mailing list [email protected] http://mail.archive.org/cgi-bin/mailman/listinfo/ol-tech To unsubscribe from this mailing list, send email to [email protected]
