> But in difference to those other projects it did not progress visibly.

Perlmonks is much more than the "visible parts".

But FWIW regarding visible style, it's possible to turn TobyInk's bootstrap style (see screen shot) into a regular theme by applying a dedicated "generalParent_container".

This wouldn't be the default theme, but a good start to develop one (it still has several issues, like breaking other JS code° and we need backwards compatibility for (browser-)static HTML)

IMHO this theme should include a hook such that everyone could inject his own JS code from his Display Settings - like it's possible to inject one's own CSS - to allow further evolution.

(PMdev's can neither create or fork code-nodes, they can only provide patches to existing nodes and hope the gods accept them. And they don't have access to all the code. To further complicate things they can't test patches in a sandbox.)

> Thank you for the Link at https://perlmonks.org/?node_id=555609

Honestly I doubt you are really interested in the gory details of the monasteries engine, since you didn't care to figured out yet how to set a proper link.*

Otherwise I could link to some documentation ...

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

*) I have a nodelet hack which automatically turns text like https://perlmonks.org/?node_id=555609 into meaningful links like Can I get the PerlMonks source code?

°) there is a long traditional reluctance against complicating the code-base with JS. And PMDevs are Perl experts, not designers excelling in CSS. The solution would be to decouple these domains.

In reply to Re^5: Welcoming New Users and Accepting Site Reviews (JS Theme) by LanX
in thread Welcoming New Users and Accepting Site Reviews by HugoNo1

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.