Seedbury Square - User contributions [en]

Global user settings json

2026-04-13T15:27:36Z

Mgm-seedbury:

{
"editor.detectIndentation": false,
"editor.insertSpaces": false,
"editor.formatOnSave": true,
"js/ts.format.semicolons": "insert",
"js/ts.preferences.quoteStyle": "single",
"js/ts.preferences.importModuleSpecifierEnding": "js",
"editor.codeActionsOnSave": {
"source.organizeImports": "always",
"source.addMissingImports.ts": "always"
},
"file.trimTrailingWhitespace": true
}

2025-12-15T20:09:46Z

Mgm-seedbury: Created page with " { "version": "0.2.0", "configurations": [ /* --- Server (Node.js) --- */ { "name": "Server: Node (inspect)", "type": "pwa-node", "request": "launch", "program": "${workspaceFolder}/api/src/webServer/webserver.js", "cwd": "${workspaceFolder}/api/src/webServer", "runtimeArgs": [ "--inspect=9229" ], "env": { "NODE_ENV": "de..."

Global user settings json

2025-12-15T20:08:28Z

Mgm-seedbury: Created page with " { "editor.detectIndentation": false, "editor.insertSpaces": false, "editor.formatOnSave": true, "javascript.format.semicolons": "insert", "javascript.preferences.quoteStyle": "single", "javascript.preferences.importModuleSpecifierEnding": "js", "editor.codeActionsOnSave": { "source.organizeImports": "always", "source.addMissingImports.ts": "always" } }"

{
"editor.detectIndentation": false,
"editor.insertSpaces": false,
"editor.formatOnSave": true,
"javascript.format.semicolons": "insert",
"javascript.preferences.quoteStyle": "single",
"javascript.preferences.importModuleSpecifierEnding": "js",
"editor.codeActionsOnSave": {
"source.organizeImports": "always",
"source.addMissingImports.ts": "always"
}
}

Setup Steps

2025-12-15T20:05:46Z

Mgm-seedbury: Setup steps for Ksitropy development workstation

Ksitropy

2025-12-15T18:43:00Z

Mgm-seedbury:

The everything app.

[[Setup Steps]]

Main Page

2025-09-24T15:50:07Z

Mgm-seedbury: /* See Also */

== Welcome to the Seedbury Wiki ==

Behave or be sent to [https://wiki.seedburysquare.com/index.php/The_Dungeon the dungeon].

== Overview ==

Established in 2016, '''Seedbury Square''' has grown to become a mayor player in the development of custom web-based application space. Clients range from the public to the private sector with some of the platforms supporting complete professions.

== Development Standards ==
Seedbury Square uses these [https://wiki.seedburysquare.com/index.php/Programming_Standards programming standards]

== Active Projects ==
From all the [https://wiki.seedburysquare.com/index.php/Projects projects] developed by Seedbury Square, these are actively being developed or maintained as of 2025.
=== [https://wiki.seedburysquare.com/index.php/Ksitropy Ksitropy] ===
The everything app.
=== [https://wiki.seedburysquare.com/index.php/SUMAC Sistema Unificado de Manejo y Administración de Casos (SUMAC)] ===
Contains the following projects:
* Court of First Instance (CFI)
** Judges
** Admin
* Court of Appeals (COA)
** Judges
** Admin
* Supreme Court (SC)
** Judges
** Admin
* Attorney
* Clerk

== Technologies Used ==
=== Frontend ===
* Frameworks: (project-dependent)
** [https://mozilla.github.io/pdf.js/ PDF.JS]
** [https://pdf-lib.js.org/ pdf-lib]
** [https://www.tiny.cloud/tinymce/ TinyMCE]
** [https://wiki.seedburysquare.com/index.php/SeedburySquareFrameworkBrrrrr Proprietary Framework]
* Styling
** Vanilla CSS
* Code style
** Default [https://code.visualstudio.com/ VSCode] Settings conventions
* Folder structure
** Modular
** Reusable components
* Testing: Try and break it testing
* Version control: Git with feature-branch workflow

=== Backend ===
* Languages
** Node.js
** PHP (based on project needs)
* Frameworks
** [https://www.setasign.com/products/setapdf-core/details/ SetaPDF-Core]
** [https://www.setasign.com/products/setapdf-stamper/details/ SetaPDF-Stamper]
** [https://www.setasign.com/products/fpdi/about/ FPDI] (based on project needs)
* Architecture: RESTful APIs (where applicable)
* Database
** MSSQL
** MariaDB
** Neo4J
* Authentication: IDK
* Logging: Still Don't konw
* Testing: Try and break it testing
* CI/CD: I don't know what this means.

== New Employee Setup Procedure ==

=== Hardware/Access Setup ===

# Provide oldest computer available.
::- New Computers are only for older employees.
# Create company email and communication accounts (Slack, Google Workspace, etc.)
# Provide access to repositories (GitHub/GitLab), project boards (Jira/Trello), and documentation

=== Software Installation ===
# Install development tools: VS Code, Docker, Postman, etc.
# Clone required repositories
# Follow README or internal docs to set up dev environment
# Join onboarding session with team lead or HR

=== Onboarding Checklist ===
* [ ] NDA signed and uploaded
* [ ] Accounts created
* [ ] Introductory meeting scheduled
* [ ] Onboarding tasks assigned in project management tool
* [ ] Dev environment verified and working

== See Also ==
* [[Project Alpha Documentation]]
* [[Employee Onboarding Checklist]]
* [[Tech Stack Overview]]
* [[Pull Requests Workflow]]
* [[Change Control Guide]]

== Helpful Tools ==
* [[VSCode Snippets]]
* [[Bash Tools]]

== External Links ==
* [https://www.seedburysquare.com/ Official Website]
* [https://github.com/SeedburySquare GitHub Organization]

Pull Requests Workflow

2025-08-13T15:14:31Z

Mgm-seedbury:

* Recommended: Github Pull Requests extension for VSCode.
* To open .zprofile mentioned in the following steps run ''edit'' in terminal.
----
== Developer Steps ==

=== Starting a task ===
* Add the following function to .zprofile:
<nowiki> function newBranch(){
git checkout Development
git pull
git checkout -b $1
git push --set-upstream origin $1
}</nowiki>
* Run ''newBranch (Bug|Feature)-###-short_description''.

=== Working a task ===
==== Daily and before any commit====
# Run ''mergeFrom''.
# Resolve conflicts (communicating with the relevant developers).

* Make sure the mergeFrom function in .zprofile is:
<nowiki> function mergeFrom() {
currentBranch=$(git rev-parse --abbrev-ref HEAD)
git checkout "${1:-Development}"
git pull
git checkout "${2:-$currentBranch}"
git merge "${1:-Development}"
}</nowiki>
==== Pushing code ====
* ''commitAndPush'' whenever there is a distinct and stable (tested) change (not the entire task; just a specific, concise, and related chunk of changes).
* If first commit of task create a Draft Pull Request:
# Create Pull Request.
# Set redmine title as title of pull request (if unavailable, set a short description).
# Use the description to explain more in depth the changes done. Remember to keep it updated with any changes as you go, and include reproduction steps if applicable.
# The button with the word create has a dropdown arrow, click it and choose draft pull request.
# Set yourself as asignee of the pull request.
* If a pull request is already open, push normally and the changes will be automatically added to the open pull request.
* Be on the lookout for changes requested.

==== Finishing a task ====
# Set draft pull request to ready for review.
# Stay on the lookout for any changes requested.
# If the request is deemed acceptable, it will be approved and the reviewer will take the next steps.

==== Multiple developers working in one task ====
* Both developers will work in the same branch.
* If you need changes made by the other developers and before any commits run ''git merge'', then resolve conflicts.
* Only one pull request per branch, communicate accordingly.

== Reviewer Steps ==
# Choose an open pull request.
# Review changes.
# Recommend changes or approve pull request.
* Be on the lookout for the owner of the request implementing the changes (repeat steps 2 and 3 after changes are committed).
* When code is acceptable, merge the task_branch into Development and delete the task_branch.

* You can see the commits in a draft pull request and recommend changes midway, only when marked for review by the developer will you be able to actually approve and merge the request.

== Keep in mind ==
* If using VSCode extension, you might need to manually refresh at some points throughout the process.
----

Pull Requests Workflow

2025-08-13T15:12:07Z

Mgm-seedbury: Added Pull Requests Workflow Page

= Pull Requests Workflow =
* Recommended: Github Pull Requests extension for VSCode.
* To open .zprofile mentioned in the following steps run ''edit'' in terminal.
----
== Developer Steps ==

=== Starting a task ===
* Add the following function to .zprofile:
<nowiki> function newBranch(){
git checkout Development
git pull
git checkout -b $1
git push --set-upstream origin $1
}</nowiki>
* Run ''newBranch (Bug|Feature)-###-short_description''.

=== Working a task ===
==== Daily and before any commit====
# Run ''mergeFrom''.
# Resolve conflicts (communicating with the relevant developers).

* Make sure the mergeFrom function in .zprofile is:
<nowiki> function mergeFrom() {
currentBranch=$(git rev-parse --abbrev-ref HEAD)
git checkout "${1:-Development}"
git pull
git checkout "${2:-$currentBranch}"
git merge "${1:-Development}"
}</nowiki>
==== Pushing code ====
* ''commitAndPush'' whenever there is a distinct and stable (tested) change (not the entire task; just a specific, concise, and related chunk of changes).
* If first commit of task create a Draft Pull Request:
# Create Pull Request.
# Set redmine title as title of pull request (if unavailable, set a short description).
# Use the description to explain more in depth the changes done. Remember to keep it updated with any changes as you go, and include reproduction steps if applicable.
# The button with the word create has a dropdown arrow, click it and choose draft pull request.
# Set yourself as asignee of the pull request.
* If a pull request is already open, push normally and the changes will be automatically added to the open pull request.
* Be on the lookout for changes requested.

==== Finishing a task ====
# Set draft pull request to ready for review.
# Stay on the lookout for any changes requested.
# If the request is deemed acceptable, it will be approved and the reviewer will take the next steps.

==== Multiple developers working in one task ====
* Both developers will work in the same branch.
* If you need changes made by the other developers and before any commits run ''git merge'', then resolve conflicts.
* Only one pull request per branch, communicate accordingly.

== Reviewer Steps ==
# Choose an open pull request.
# Review changes.
# Recommend changes or approve pull request.
* Be on the lookout for the owner of the request implementing the changes (repeat steps 2 and 3 after changes are committed).
* When code is acceptable, merge the task_branch into Development and delete the task_branch.

* You can see the commits in a draft pull request and recommend changes midway, only when marked for review by the developer will you be able to actually approve and merge the request.

== Keep in mind ==
* If using VSCode extension, you might need to manually refresh at some points throughout the process.
----

Main Page

2025-08-13T13:21:10Z

Mgm-seedbury:

== Welcome to the Seedbury Wiki ==

Behave or be sent to [https://wiki.seedburysquare.com/index.php/The_Dungeon the dungeon].

== Overview ==

Established in 2016, '''Seedbury Square''' has grown to become a mayor player in the development of custom web-based application space. Clients range from the public to the private sector with some of the platforms supporting complete professions.

== Development Standards ==
Seedbury Square uses these [https://wiki.seedburysquare.com/index.php/Programming_Standards programming standards]

== Active Projects ==
From all the [https://wiki.seedburysquare.com/index.php/Projects projects] developed by Seedbury Square, these are actively being developed or maintained as of 2025.
=== [https://wiki.seedburysquare.com/index.php/Ksitropy Ksitropy] ===
The everything app.
=== [https://wiki.seedburysquare.com/index.php/SUMAC Sistema Unificado de Manejo y Administración de Casos (SUMAC)] ===
Contains the following projects:
* Court of First Instance (CFI)
** Judges
** Admin
* Court of Appeals (COA)
** Judges
** Admin
* Supreme Court (SC)
** Judges
** Admin
* Attorney
* Clerk

== Technologies Used ==
=== Frontend ===
* Frameworks: (project-dependent)
** [https://mozilla.github.io/pdf.js/ PDF.JS]
** [https://pdf-lib.js.org/ pdf-lib]
** [https://www.tiny.cloud/tinymce/ TinyMCE]
** [https://wiki.seedburysquare.com/index.php/SeedburySquareFrameworkBrrrrr Proprietary Framework]
* Styling
** Vanilla CSS
* Code style
** Default [https://code.visualstudio.com/ VSCode] Settings conventions
* Folder structure
** Modular
** Reusable components
* Testing: Try and break it testing
* Version control: Git with feature-branch workflow

=== Backend ===
* Languages
** Node.js
** PHP (based on project needs)
* Frameworks
** [https://www.setasign.com/products/setapdf-core/details/ SetaPDF-Core]
** [https://www.setasign.com/products/setapdf-stamper/details/ SetaPDF-Stamper]
** [https://www.setasign.com/products/fpdi/about/ FPDI] (based on project needs)
* Architecture: RESTful APIs (where applicable)
* Database
** MSSQL
** MariaDB
** Neo4J
* Authentication: IDK
* Logging: Still Don't konw
* Testing: Try and break it testing
* CI/CD: I don't know what this means.

== New Employee Setup Procedure ==

=== Hardware/Access Setup ===

# Provide oldest computer available.
::- New Computers are only for older employees.
# Create company email and communication accounts (Slack, Google Workspace, etc.)
# Provide access to repositories (GitHub/GitLab), project boards (Jira/Trello), and documentation

=== Software Installation ===
# Install development tools: VS Code, Docker, Postman, etc.
# Clone required repositories
# Follow README or internal docs to set up dev environment
# Join onboarding session with team lead or HR

=== Onboarding Checklist ===
* [ ] NDA signed and uploaded
* [ ] Accounts created
* [ ] Introductory meeting scheduled
* [ ] Onboarding tasks assigned in project management tool
* [ ] Dev environment verified and working

== See Also ==
* [[Project Alpha Documentation]]
* [[Employee Onboarding Checklist]]
* [[Tech Stack Overview]]
* [[Pull Requests Workflow]]
== Helpful Tools ==
* [[VSCode Snippets]]
* [[Bash Tools]]

== External Links ==
* [https://www.seedburysquare.com/ Official Website]
* [https://github.com/SeedburySquare GitHub Organization]