Main Page: Difference between revisions
Mgm-seedbury (talk | contribs) |
|||
| (42 intermediate revisions by 3 users not shown) | |||
| Line 2: | Line 2: | ||
Behave or be sent to [https://wiki.seedburysquare.com/index.php/The_Dungeon the dungeon]. | Behave or be sent to [https://wiki.seedburysquare.com/index.php/The_Dungeon the dungeon]. | ||
== Overview == | == Overview == | ||
| Line 29: | Line 8: | ||
== Development Standards == | == 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 | |||
=== Frontend | == Technologies Used == | ||
* Frameworks: | === Frontend === | ||
* | * Frameworks: (project-dependent) | ||
* Code style: | ** [https://mozilla.github.io/pdf.js/ PDF.JS] | ||
* Folder structure | ** [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 | * Testing: Try and break it testing | ||
* Version control: Git with feature-branch workflow | * Version control: Git with feature-branch workflow | ||
=== Backend | === Backend === | ||
* Languages | * Languages | ||
* Frameworks: | ** 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) | * Architecture: RESTful APIs (where applicable) | ||
* Database | * Database | ||
** MSSQL | |||
** MariaDB | |||
** Neo4J | |||
* Authentication: IDK | * Authentication: IDK | ||
* Logging: Still Don't konw | * Logging: Still Don't konw | ||
* Testing: Try and break it testing | * Testing: Try and break it testing | ||
* CI/CD: I don't know what this means. | * CI/CD: I don't know what this means. | ||
== New Employee Setup Procedure == | == New Employee Setup Procedure == | ||
| Line 73: | Line 67: | ||
=== Hardware/Access Setup === | === 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 === | === 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 === | === Onboarding Checklist === | ||
| Line 92: | Line 86: | ||
== See Also == | == See Also == | ||
* [[Project Alpha Documentation]] | * [[Project Alpha Documentation]] | ||
* [[Employee Onboarding Checklist]] | * [[Employee Onboarding Checklist]] | ||
* [[Tech Stack Overview]] | * [[Tech Stack Overview]] | ||
* [[Pull Requests Workflow]] | |||
* [[Change Control Guide]] | |||
== Helpful Tools == | |||
* [[VSCode Snippets]] | |||
* [[Bash Tools]] | |||
== External Links == | == External Links == | ||
* [https://www. | * [https://www.seedburysquare.com/ Official Website] | ||
* [https://github.com/ | * [https://github.com/SeedburySquare GitHub Organization] | ||
Latest revision as of 15:50, 24 September 2025
Welcome to the Seedbury Wiki
Behave or be sent to 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 programming standards
Active Projects
From all the projects developed by Seedbury Square, these are actively being developed or maintained as of 2025.
Ksitropy
The everything app.
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)
- Styling
- Vanilla CSS
- Code style
- Default 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
- SetaPDF-Core
- SetaPDF-Stamper
- 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