Technology stack: Difference between revisions

Revision as of 02:58, 27 December 2015 editSn1per (talk \| contribs)Extended confirmed users, Rollbackers2,062 edits Added {{merge}} tag to article (TW)← Previous edit		Latest revision as of 18:06, 15 June 2017 edit undoTom.Reding (talk \| contribs)Autopatrolled, Extended confirmed users, Page movers, Template editors3,879,760 editsm +{{Redirect category shell}} for multiple-{{R}} #Rs using AWB
(3 intermediate revisions by 2 users not shown)
Line 1:		Line 1:
			#REDIRECT ]
	{{merge\|Solution stack\|discuss=Talk:Technology stack#Proposed merge with Solution stack\|date=December 2015}}
	]
	A '''technology stack''' comprises the layers of components or services that are used to provide a software solution or application. Traditional examples include the ], the ], and the .

			{{Redirect category shell\|1=
	Technology stacks are often articulated as a list of technologies, such as "J2EE with Java Server Faces running against a SQL Server database" or as a diagram.
			{{R to article without mention}}

			{{R with history}}
	== See also ==
			}}
	*]
	*]

	== References ==



	{{compu-network-stub}}
	]
	]

Latest revision as of 18:06, 15 June 2017

Redirect to:

This page is a redirect. The following categories are used to track and monitor this redirect:

To an article without mention: This is a redirect to an article without any mention of the redirected word or phrase.
- For titles that are obvious omissions from target articles, check the rcat index for more specific templates to use instead of this rcat – examples: {{R from misspelling}} for misspellings of article titles or {{R from incorrect name}} for wrong names.

With history: This is a redirect from a page containing substantive page history. This page is kept as a redirect to preserve its former content and attributions. Please do not remove the tag that generates this text (unless the need to recreate content on this page has been demonstrated), nor delete this page.
- This template should not be used for redirects having some edit history but no meaningful content in their previous versions, nor for redirects created as a result of a page merge (use {{R from merge}} instead), nor for redirects from a title that forms a historic part of Misplaced Pages (use {{R with old history}} instead).

When appropriate, protection levels are automatically sensed, described and categorized.