Architecture - Revision history

2A02:C7C:C40C:2600:8C18:EA9F:289C:239D: /* Consistency */

2024-12-11T14:00:06Z

Consistency

← Older revision		Revision as of 14:00, 11 December 2024
Line 11:		Line 11:
	== Consistency ==		== Consistency ==

	A handful of universally followed patterns help a team naturally produce compatible code, even if it is in different projects. There is nothing stating that you have to use SocialStack's automated database entities in your new code, but doing so means you get a significant amount of features for free just simply because your code is fitting in with the norm.		A handful of universally followed patterns help a team naturally produce compatible code, even if it is in different projects. There is nothing stating that you have to use SocialStack's automated database entities in your new code, but doing so means you get a significant amount of features for free just simply because your code is fitting in with the norm. Better yet, the SocialStack generate command will spawn a new module which is perfectly consistent with every other module in a single line:

			<syntaxhighlight lang="bash">
			socialstack generate Api/VehicleBrands
			socialstack generate UI/Vehicle/Brand/View
			</syntaxhighlight>

	== Modularity ==		== Modularity ==

2A02:C7C:C40C:2600:8C18:EA9F:289C:239D at 13:57, 11 December 2024

2024-12-11T13:57:56Z

← Older revision		Revision as of 13:57, 11 December 2024
Line 1:		Line 1:
	SocialStack is primarily a fully open source dotnet core 6 API. By default it comes with a React frontend installed which can also be simply ignored or removed if you wish to use it headless instead.		SocialStack is primarily a fully open source dotnet core 6 API. By default it comes with a React frontend installed which can also be simply ignored or removed if you wish to use it headless instead.

	The structure of all parts of a SocialStack project is designed to be highly modular - all of the core features and functionality are in small, replaceable modules which originate from [https://github.com/socialstack-core/modules this GitHub repository].		= Founding Pillars =

	~~Creating~~ projects, which ~~primarily just installs~~ a ~~default package of modules~~, ~~as well as installing or uninstalling modules~~, is ~~handled~~ by [https://www.npmjs.com/package/socialstack SocialStack tools] - ~~an open source command line toolset written in javascript which is typically the best place to start when working with SocialStack~~.		SocialStack, like really any designed system, has foundational design pillars that it and all projects on it are built to follow.

			== Simplicity ==

			First and foremost, keep it simple. SocialStack is frequently used in fast iterating projects which often also have high performance requirements too. Dozens of layers of boilerplate are precisely what we want to eliminate at all times.

			== Consistency ==

			A handful of universally followed patterns help a team naturally produce compatible code, even if it is in different projects. There is nothing stating that you have to use SocialStack's automated database entities in your new code, but doing so means you get a significant amount of features for free just simply because your code is fitting in with the norm.

			== Modularity ==

			Grouping things by feature rather than some abstract functional type makes following and testing the code substantially easier. Working with something to do with Users? It's probably in a folder called Users.

			== Generic and reusable ==

			Configuration such as feature flags, event based design, partial classes and avoiding project specific namespacing are all essential to how code can be easily reused between projects and within a project. Public MIT licensed reusable components are installable using the [https://www.npmjs.com/package/socialstack SocialStack command line tools] and ultimately originate from [https://github.com/socialstack-core/modules this GitHub repository].

2A02:C7F:22BE:A500:498:3225:1A16:A72D at 11:23, 5 July 2022

2022-07-05T11:23:11Z

← Older revision		Revision as of 11:23, 5 July 2022
Line 1:		Line 1:
	SocialStack is primarily a dotnet core 6 API. By default it comes with a React frontend installed which can also be simply ignored or removed if you wish to use it headless instead.		SocialStack is primarily a fully open source dotnet core 6 API. By default it comes with a React frontend installed which can also be simply ignored or removed if you wish to use it headless instead.

			The structure of all parts of a SocialStack project is designed to be highly modular - all of the core features and functionality are in small, replaceable modules which originate from [https://github.com/socialstack-core/modules this GitHub repository].

			Creating projects, which primarily just installs a default package of modules, as well as installing or uninstalling modules, is handled by [https://www.npmjs.com/package/socialstack SocialStack tools] - an open source command line toolset written in javascript which is typically the best place to start when working with SocialStack.

Luke at 20:03, 21 January 2022

2022-01-21T20:03:47Z

← Older revision		Revision as of 20:03, 21 January 2022
Line 1:		Line 1:
	SocialStack is primarily a dotnet core 5 API. By default it comes with a React frontend installed which can also be simply ignored or removed if you wish to use it headless instead.		SocialStack is primarily a dotnet core 6 API. By default it comes with a React frontend installed which can also be simply ignored or removed if you wish to use it headless instead.

Luke: Created page with "SocialStack is primarily a dotnet core 5 API. By default it comes with a React frontend installed which can also be simply ignored or removed if you wish to use it headless in..."

2021-11-09T23:10:28Z

Created page with "SocialStack is primarily a dotnet core 5 API. By default it comes with a React frontend installed which can also be simply ignored or removed if you wish to use it headless in..."

New page

SocialStack is primarily a dotnet core 5 API. By default it comes with a React frontend installed which can also be simply ignored or removed if you wish to use it headless instead.