SlashGlossary - Revision history

FunPika: added Category:Development using HotCat

2014-03-15T15:38:05Z

← Older revision		Revision as of 15:38, 15 March 2014
Line 29:		Line 29:

	* '''Users''' - Users are registered to use the site, all other visitors are logged as Anonymous.		* '''Users''' - Users are registered to use the site, all other visitors are logged as Anonymous.

			[[Category:Development]]

AudioGuy at 04:16, 15 March 2014

2014-03-15T04:16:29Z

← Older revision		Revision as of 04:16, 15 March 2014
Line 15:		Line 15:
	* '''plugins''' -		* '''plugins''' -

			* '''readers''' - readers are people who request pages on the site, if they are logged in they become users, if not they become anonymous coward users if they post.
	* '''Sections & Topics''' - Seem similar. Sections are similar to the way a newspaper is laid out, i.e.: business section, sports section, local section, etc. Topics can appear anywhere, share similar concepts. The home page has stuff from all sections. (AG note - this now not entirely correct)		* '''Sections & Topics''' - Seem similar. Sections are similar to the way a newspaper is laid out, i.e.: business section, sports section, local section, etc. Topics can appear anywhere, share similar concepts. The home page has stuff from all sections. (AG note - this now not entirely correct)
	* '''Stories''' - Stories reside in the middle section of the page and have the intro-text of the stories along with the authors and what departments they are from.		* '''Stories''' - Stories reside in the middle section of the page and have the intro-text of the stories along with the authors and what departments they are from.

50.45.173.59 at 23:10, 28 February 2014

2014-02-28T23:10:57Z

← Older revision		Revision as of 23:10, 28 February 2014
Line 4:		Line 4:
	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.		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		* '''D1''' - The orgiginal Slash interface
	* '''D2''' - The new fancy interface that we have disabled on Soylent.		* '''D2''' - The new fancy interface that we have disabled on Soylent.
	* '''~~tasks~~''' - ~~periodic tasks run by slashd like cron jobs~~.		* '''Authors''' - Authors approve submissions, have the authority to change the look of the site, and can moderate.
	* '''~~tagboxes~~'''		* '''Comments''' - Users may write comments about a story.
			* '''firehose''' - The Firehose is a collection of content from anywhere on the site that users can vote on and tag.



			* '''nexus''' - a special kind of topic (which we call a topic_nexus when we want to emphasize that it is both). 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.
	* '''plugins''' -		* '''plugins''' -
	* '''firehose''' - The Firehose is a collection of content from anywhere on the site that users can vote on and tag.

			* '''Sections & Topics''' - Seem similar. Sections are similar to the way a newspaper is laid out, i.e.: business section, sports section, local section, etc. Topics can appear anywhere, share similar concepts. The home page has stuff from all sections. (AG note - this now not entirely correct)
			* '''Stories''' - Stories reside in the middle section of the page and have the intro-text of the stories along with the authors and what departments they are from.
			* '''Submissions''' - Stories are submitted by users, and then approved by authors.
	* '''skin''' - from 'sectiontopics' :		* '''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.		** 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.		** 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.
	* '''nexus''' - a special kind of topic (which we call a topic_nexus when we want to emphasize that it is both). 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.

	* '''~~Stories~~''' - ~~Stories reside in the middle section of the page and have the intro-text of the stories along with the authors and what departments they are from~~.		* '''tagboxes'''
	* '''~~Comments~~''' - ~~Users may write comments about~~ a ~~story.~~		* '''tasks''' - periodic tasks run by slashd like cron jobs.
	* '''~~Submissions~~''' - ~~Stories are submitted by users, and then approved by authors~~.		* '''template''' - html that is parsed by the Perl Template Toolkit. part of a theme
			* '''theme''' - "A theme is a website design."

	* '''Users''' - Users are registered to use the site, all other visitors are logged as Anonymous.		* '''Users''' - Users are registered to use the site, all other visitors are logged as Anonymous.
	* '''Authors''' - Authors approve submissions, have the authority to change the look of the site, and can moderate.
	* '''Sections & Topics''' - Seem similar. Sections are similar to the way a newspaper is laid out, i.e.: business section, sports section, local section, etc. Topics can appear anywhere, share similar concepts. The home page has stuff from all sections. (AG note - this now not entirely correct)

50.45.173.59 at 23:05, 28 February 2014

2014-02-28T23:05:18Z

← Older revision		Revision as of 23:05, 28 February 2014
Line 17:		Line 17:
	** 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.		** 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.
	* '''nexus''' - a special kind of topic (which we call a topic_nexus when we want to emphasize that it is both). 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.		* '''nexus''' - a special kind of topic (which we call a topic_nexus when we want to emphasize that it is both). 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.

			* '''Stories''' - Stories reside in the middle section of the page and have the intro-text of the stories along with the authors and what departments they are from.
			* '''Comments''' - Users may write comments about a story.
			* '''Submissions''' - Stories are submitted by users, and then approved by authors.
			* '''Users''' - Users are registered to use the site, all other visitors are logged as Anonymous.
			* '''Authors''' - Authors approve submissions, have the authority to change the look of the site, and can moderate.
			* '''Sections & Topics''' - Seem similar. Sections are similar to the way a newspaper is laid out, i.e.: business section, sports section, local section, etc. Topics can appear anywhere, share similar concepts. The home page has stuff from all sections. (AG note - this now not entirely correct)

50.45.173.59 at 22:26, 28 February 2014

2014-02-28T22:26:06Z

← Older revision		Revision as of 22:26, 28 February 2014
Line 16:		Line 16:
	** 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.		** 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.		** 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.
			* '''nexus''' - a special kind of topic (which we call a topic_nexus when we want to emphasize that it is both). 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.

50.45.173.59 at 22:18, 28 February 2014

2014-02-28T22:18:29Z

@@ Line 14: / Line 14: @@
 * '''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.

50.45.173.59 at 22:16, 28 February 2014

2014-02-28T22:16:19Z

@@ Line 5: / Line 5: @@
 * '''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
@@ Line 13: / Line 12: @@
 * '''plugins''' -
 * '''firehose''' - The Firehose is a collection of content from anywhere on the site that users can vote on and tag.

50.45.173.59 at 18:25, 27 February 2014

2014-02-27T18:25:52Z

← Older revision		Revision as of 18:25, 27 February 2014
Line 5:		Line 5:

	* '''theme''' - "A theme is a website design."		* '''theme''' - "A theme is a website design."
	* '''skin''' - seems to ~~be used interchangeably with theme~~, ~~especially in the code~~		* '''skin''' - seems to refer to a css file, no clear definition yet.
	* '''template''' - html that is parsed by the Perl Template Toolkit. part of a theme		* '''template''' - html that is parsed by the Perl Template Toolkit. part of a theme
	* '''D1''' - The orgiginal Slash interface		* '''D1''' - The orgiginal Slash interface

50.45.172.110 at 11:01, 22 February 2014

2014-02-22T11:01:37Z

← Older revision		Revision as of 11:01, 22 February 2014
Line 6:		Line 6:
	* '''theme''' - "A theme is a website design."		* '''theme''' - "A theme is a website design."
	* '''skin''' - seems to be used interchangeably with theme, especially in the code		* '''skin''' - seems to be used interchangeably with theme, especially in the code
	* '''template''' - ~~"a bit of text~~ that is parsed by Perl~~, using the~~ Template Toolkit". part of a theme		* '''template''' - html that is parsed by the Perl Template Toolkit. part of a theme
	* '''D1''' - The orgiginal Slash interface		* '''D1''' - The orgiginal Slash interface
	* '''D2''' - The new fancy interface that we have disabled on Soylent.		* '''D2''' - The new fancy interface that we have disabled on Soylent.

50.45.172.110 at 10:58, 22 February 2014

2014-02-22T10:58:44Z

← Older revision		Revision as of 10:58, 22 February 2014
Line 9:		Line 9:
	* '''D1''' - The orgiginal Slash interface		* '''D1''' - The orgiginal Slash interface
	* '''D2''' - The new fancy interface that we have disabled on Soylent.		* '''D2''' - The new fancy interface that we have disabled on Soylent.
	* '''tasks'''		* '''tasks''' - periodic tasks run by slashd like cron jobs.
	* '''tagboxes'''		* '''tagboxes'''
	* '''plugins'''		* '''plugins''' -
	* '''firehose''' - The Firehose is a collection of content from anywhere on the site that users can vote on and tag.		* '''firehose''' - The Firehose is a collection of content from anywhere on the site that users can vote on and tag.