Difference between revisions of "SlashGlossary"

From SoylentNews
Jump to: navigation, search
Line 14: Line 14:
  
 
* '''skin''' - from 'sectiontopics' :
 
* '''skin''' - from 'sectiontopics' :
** So "section" has been split into two: "skin" and "nexus". *Most* of the
+
** So "section" has been split into two: "skin" and "nexus". *Most* of the information that went with a section was used to describe appearances, and that went over to skin. '''So a skin now controls color (through the skin_colors table), it controls which templates are used (the final part of a template's three-part name is now skin, not section), and it controls with which other stories a story is grouped (on which index page)'''. And the non-display aspects of sections -- mainly, the "section_extras" data which ensured that stories in Book Reviews stored a field for ISBN -- were sent over to nexuses.
    information that went with a section was used to describe appearances,
+
** Each skin has precisely one nexus; you can think of a skin as drawing its stories from its nexus. The clever part is that a nexus is just a special kind of topic (which we call a topic_nexus when we want to emphasize that it is both). So if a story has both the Developers topic_nexus, and the Book Reviews topic_nexus, then it will appear on both books.slashdot.org and developers.slashdot.org. And the additional data stored with the story will include the union of all the "extras" data -- not only ISBN and so on, but also any "extras" data that may be in the Developers nexus. There don't actually happen to be any extras for Developers on Slashdot, so maybe this isn't the best example, but if there were, a story that was categorized into both nexuses would include that data too.
    and that went over to skin. '''So a skin now controls color (through the
 
    skin_colors table), it controls which templates are used (the final part
 
    of a template's three-part name is now skin, not section), and it
 
    controls with which other stories a story is grouped (on which index
 
    page)'''. And the non-display aspects of sections -- mainly, the
 
    "section_extras" data which ensured that stories in Book Reviews stored
 
    a field for ISBN -- were sent over to nexuses.
 
** Each skin has precisely one nexus; you can think of a skin as drawing
 
    its stories from its nexus. The clever part is that a nexus is just a
 
    special kind of topic (which we call a topic_nexus when we want to
 
    emphasize that it is both). So if a story has both the Developers
 
    topic_nexus, and the Book Reviews topic_nexus, then it will appear on
 
    both books.slashdot.org and developers.slashdot.org. And the additional
 
    data stored with the story will include the union of all the "extras"
 
    data -- not only ISBN and so on, but also any "extras" data that may be
 
    in the Developers nexus. There don't actually happen to be any extras
 
    for Developers on Slashdot, so maybe this isn't the best example, but if
 
    there were, a story that was categorized into both nexuses would include
 
    that data too.
 

Revision as of 22:18, 28 February 2014

CssWork parent of this page

Glossary of terms used in slash code

These an be confusing if you are new to slash code. Try to keep these to one displayed line, this is not for full descriptions.

  • theme - "A theme is a website design."
  • template - html that is parsed by the Perl Template Toolkit. part of a theme
  • D1 - The orgiginal Slash interface
  • D2 - The new fancy interface that we have disabled on Soylent.
  • tasks - periodic tasks run by slashd like cron jobs.
  • tagboxes
  • plugins -
  • firehose - The Firehose is a collection of content from anywhere on the site that users can vote on and tag.
  • skin - from 'sectiontopics' :
    • So "section" has been split into two: "skin" and "nexus". *Most* of the information that went with a section was used to describe appearances, and that went over to skin. So a skin now controls color (through the skin_colors table), it controls which templates are used (the final part of a template's three-part name is now skin, not section), and it controls with which other stories a story is grouped (on which index page). And the non-display aspects of sections -- mainly, the "section_extras" data which ensured that stories in Book Reviews stored a field for ISBN -- were sent over to nexuses.
    • Each skin has precisely one nexus; you can think of a skin as drawing its stories from its nexus. The clever part is that a nexus is just a special kind of topic (which we call a topic_nexus when we want to emphasize that it is both). So if a story has both the Developers topic_nexus, and the Book Reviews topic_nexus, then it will appear on both books.slashdot.org and developers.slashdot.org. And the additional data stored with the story will include the union of all the "extras" data -- not only ISBN and so on, but also any "extras" data that may be in the Developers nexus. There don't actually happen to be any extras for Developers on Slashdot, so maybe this isn't the best example, but if there were, a story that was categorized into both nexuses would include that data too.