Features & lists
Grids and lists of benefits, services, steps, products, checklists. One sample per component, in a row, to compare. Items are shown inside their section.
- Features
- Feature
- FeatureSection
- FeatureItem
- GradientFeatureSection
- GradientFeatureItem
- NewFeaturesSection
- NewFeatureItem
- HighlightsSection
- HighlightItem
- DifferentSection
- DifferentItem
- ServiceSection
- ServicesSection
- ServiceItem
- ProductSection
- ProductItem
- AudienceSection
- AudienceItem
- ChecklistSection
- ChecklistItem
- StepsSection
- StepItem
- SchemaSection
- SchemaItem
- Offsets
- AboutCertificationSection
- AboutCertificationItem
- CertificationSection
- CertificationItem
- ProductQualitySection
- AboutUsSection
- MissionSection
Featuressections/Features.astroused by posexpert.se
Features — a grid of <Feature> cards: services, benefits, steps, USP. variant="cards" white cards on a tinted/dark band, icon in a brand square variant="plain" no card, icon + text (dense benefit lists) columns 2|3|4; overlap pulls the grid over a cover Hero.
Services
Fast
We develop solutions with minimal hardware requirements to speed up installation and deployment. Our software systems that can handle a high volume of transactions without slowing down.
Reliable
We offer fast and reliable online and offline functionality with data backup and recovery options, so you can retrieve your critical data in case of system failures.
Secure
We develop solutions that use end-to-end encryption protocols to safeguard transaction data with a firewall and anti-malware protection that can detect and prevent cyber threats
Featuresections/Feature.astroused by posexpert.se
Feature — one item of <Features>. Icon is an astro-heroicons component imported in the article; image is a file name from images/.
<Features>Services
Fast
We develop solutions with minimal hardware requirements to speed up installation and deployment. Our software systems that can handle a high volume of transactions without slowing down.
Reliable
We offer fast and reliable online and offline functionality with data backup and recovery options, so you can retrieve your critical data in case of system failures.
Secure
We develop solutions that use end-to-end encryption protocols to safeguard transaction data with a firewall and anti-malware protection that can detect and prevent cyber threats
FeatureSectioncomponents/FeatureSection.astroused by pages.gitt.one
No props: a wrapper around FeatureItem children.
Own your website, don't rent it
Most websites are hostages of the studio that built them: leaving means rewriting. Ours are designed for leaving — content in plain typed files that migrate to any CMS, an MIT-licensed engine any developer or AI agent can pick up, and a Docker image that runs anywhere. We measure this honestly as exit time: minutes from git clone to a working local build
FeatureItemcomponents/FeatureItem.astroused by pages.gitt.one
<FeatureSection>Own your website, don't rent it
Most websites are hostages of the studio that built them: leaving means rewriting. Ours are designed for leaving — content in plain typed files that migrate to any CMS, an MIT-licensed engine any developer or AI agent can pick up, and a Docker image that runs anywhere. We measure this honestly as exit time: minutes from git clone to a working local build
GradientFeatureSectioncomponents/GradientFeatureSection.astroused by pages.gitt.one
The technology inside
Boring, proven building blocks — assembled into a production line
Jamstack
JavaScript, APIs and Markup: pages are pre-rendered at build time and served as static files — fast, always on, nothing to hack
Astro + Tailwind
An open-source content framework that ships zero JavaScript by default, and ready-made design concepts — fonts, spacing, components — instead of a graphic designer on the project
GitLab-flavored Markdown
One rendering engine everywhere: a page looks the same in the repository and on the public site — with Mermaid and PlantUML diagrams
Docker portability
A site is a repository plus a standard image. Hosting is a detail, not a cage — the same image runs on any infrastructure
GitLab UI as the CMS
The web editor and Web IDE are the admin panel: no separate CMS to install, host, update and defend from attacks
CI/CD with staging
Every change builds an exact replica of the future site to discuss before release — content managers see real feedback on drafts
AI-ready content
Semantically typed data is a substrate for agents: AI edits and generates content without a programmer and without breaking the build
Built for speed
Minimum JavaScript, maximum pre-rendering: Lighthouse 100 is the acceptance target for every produced site, not a nice-to-have
GradientFeatureItemcomponents/GradientFeatureItem.astroused by pages.gitt.one
<GradientFeatureSection>The technology inside
Boring, proven building blocks — assembled into a production line
Jamstack
JavaScript, APIs and Markup: pages are pre-rendered at build time and served as static files — fast, always on, nothing to hack
Astro + Tailwind
An open-source content framework that ships zero JavaScript by default, and ready-made design concepts — fonts, spacing, components — instead of a graphic designer on the project
GitLab-flavored Markdown
One rendering engine everywhere: a page looks the same in the repository and on the public site — with Mermaid and PlantUML diagrams
Docker portability
A site is a repository plus a standard image. Hosting is a detail, not a cage — the same image runs on any infrastructure
GitLab UI as the CMS
The web editor and Web IDE are the admin panel: no separate CMS to install, host, update and defend from attacks
CI/CD with staging
Every change builds an exact replica of the future site to discuss before release — content managers see real feedback on drafts
AI-ready content
Semantically typed data is a substrate for agents: AI edits and generates content without a programmer and without breaking the build
Built for speed
Minimum JavaScript, maximum pre-rendering: Lighthouse 100 is the acceptance target for every produced site, not a nice-to-have
NewFeaturesSectioncomponents/NewFeaturesSection.astroused by skattedosan.se
Buffering Unit
We implemented a new way to process fiscal data, the latest generation of hardware that signs, stores and replicates fiscal data to the server and can be connected to the local network and support multiple cash registers.
Buffering Unit
All to one
Buffering unit can operate multiple cash registers “out of box” - just plug it into the socket, connect it to the local WI-FI and start working
Easy to start
Just replace old Control Unit with Buffering Unit. No extra configuration is needed
Large memory
We inserted an SD-card that will store fiscal data at least 5 years
Buffering
Buffering unit can be offline fer 48 hours without harm to your business
NewFeatureItemcomponents/NewFeatureItem.astroused by skattedosan.se
<NewFeaturesSection>Buffering Unit
We implemented a new way to process fiscal data, the latest generation of hardware that signs, stores and replicates fiscal data to the server and can be connected to the local network and support multiple cash registers.
Buffering Unit
All to one
Buffering unit can operate multiple cash registers “out of box” - just plug it into the socket, connect it to the local WI-FI and start working
Easy to start
Just replace old Control Unit with Buffering Unit. No extra configuration is needed
Large memory
We inserted an SD-card that will store fiscal data at least 5 years
Buffering
Buffering unit can be offline fer 48 hours without harm to your business
HighlightsSectioncomponents/HighlightsSection.astroused by skattedosan.se
<ModelPageSection>
Model A - For a single cash register
Skattedosan Model A is designed for connection to a cash register through USB. It can operate with a serial connection for cash registers with voltages ranging from 5 to 36 volts. Additionally, it can use an external power source if the serial connection lacks a power supply.
Communication protocol
- Kommunikation protokoll
Error Codes
For a comprehensive list of error codes and their definitions, click here
Highlights
Cloud server
Connect your equipment to the Skattedosan control unit through our Cloud Server service.
Local server
Alternatively, you can use Skattedosan (Model C) with your own local server.
Bluetooth-connection
Skattedosan can also connect to a mobile cash register via Bluetooth.
Distributors
Postronic AB
License
Certificate A UNIT
HighlightItemcomponents/HighlightItem.astroused by skattedosan.se
<HighlightsSection>Highlights
Cloud server
Connect your equipment to the Skattedosan control unit through our Cloud Server service.
Local server
Alternatively, you can use Skattedosan (Model C) with your own local server.
Bluetooth-connection
Skattedosan can also connect to a mobile cash register via Bluetooth.
DifferentSectioncomponents/DifferentSection.astroused by skattedosan.se
Control Unit VS Buffering Unit
Control Unit
Fiscal data is stored ONLY on the Control Unit, and THE TAX AGENCY NEEDS TO VISIT YOUR POINT OF SALE to download fiscal data
The solution WILL BECOME OBSOLETE soon
Buffering Unit
Fiscal data is being sent to the server in REAL TIME
There is NO more NEED for the Tax Agency TO VISIT YOUR POINT OF SALE: they just collect data from the Control Server
All fiscal data is replicated and kept on BOTH SIDES: Buffering Unit and Control Server
If the internet connection is lost, the Buffering Unit CONTINUES SIGNING AND KEEPING fiscal data, and waits until the internet connection is restored, then sends data to the Control Server
DifferentItemcomponents/DifferentItem.astroused by skattedosan.se
<DifferentSection>Control Unit VS Buffering Unit
Control Unit
Fiscal data is stored ONLY on the Control Unit, and THE TAX AGENCY NEEDS TO VISIT YOUR POINT OF SALE to download fiscal data
The solution WILL BECOME OBSOLETE soon
Buffering Unit
Fiscal data is being sent to the server in REAL TIME
There is NO more NEED for the Tax Agency TO VISIT YOUR POINT OF SALE: they just collect data from the Control Server
All fiscal data is replicated and kept on BOTH SIDES: Buffering Unit and Control Server
If the internet connection is lost, the Buffering Unit CONTINUES SIGNING AND KEEPING fiscal data, and waits until the internet connection is restored, then sends data to the Control Server
ServiceSectioncomponents/ServiceSection.astrohistory only
Services
Fast
We develop solutions with minimal hardware requirements to speed up installation and deployment. Our software systems that can handle a high volume of transactions without slowing down.
Reliable
We offer fast and reliable online and offline functionality with data backup and recovery options, so you can retrieve your critical data in case of system failures.
Secure
We develop solutions that use end-to-end encryption protocols to safeguard transaction data with a firewall and anti-malware protection that can detect and prevent cyber threats
ServicesSectioncomponents/ServicesSection.astroused by codeexpert.se
Our competences
Web applications
Apps that launched via any browser/on any device and need internet to be used. High speed of development, but low performance
Mobile Applications
Cross-platform mobile apps for often usage, with notifications and high performance; possible to go offline, hardware friendly
CRM & ERP Systems
Tools to manage company’s relationships and interactions with customers, manage day-to-day activities of a business
Landing Pages
Web pages with content that provide a digital presence for a business, important for branding purposes
FinTech Applications
Applications designed to automate or digitize financial operations: web-payments, mobile payments, P2P/B2C, EMV, PSP, PCI, NFC
Soft- & Hardware Integration
Software to enable processing data from special hardware and to interact with them using USB, Bluetooth, NFC
Enterprise automation systems
Software to automate manual or repetitive business processes using BPML, SOA, EAI, ETL, OAuth
IoT (Internet of Things)
Network of devices connected to the Internet and able to interact with each other and humans in real time
ServiceItemcomponents/ServiceItem.astroused by codeexpert.se
<ServicesSection>Our competences
Web applications
Apps that launched via any browser/on any device and need internet to be used. High speed of development, but low performance
Mobile Applications
Cross-platform mobile apps for often usage, with notifications and high performance; possible to go offline, hardware friendly
CRM & ERP Systems
Tools to manage company’s relationships and interactions with customers, manage day-to-day activities of a business
Landing Pages
Web pages with content that provide a digital presence for a business, important for branding purposes
FinTech Applications
Applications designed to automate or digitize financial operations: web-payments, mobile payments, P2P/B2C, EMV, PSP, PCI, NFC
Soft- & Hardware Integration
Software to enable processing data from special hardware and to interact with them using USB, Bluetooth, NFC
Enterprise automation systems
Software to automate manual or repetitive business processes using BPML, SOA, EAI, ETL, OAuth
IoT (Internet of Things)
Network of devices connected to the Internet and able to interact with each other and humans in real time
ProductSectioncomponents/ProductSection.astroused by pages.gitt.one
Two builder images, two kinds of website
Pick the image that matches what you are publishing. Everything else — the markdown pipeline, image optimization, SEO files, caching rules — is inherited from it.
{project}/docsKnowledge bases
The markdown files your team already writes in GitLab, published as a website. Clients read the site instead of walking into your repository.
- Plain .md and .mdx files, no front matter required
- README.md becomes the site root, links between .md files are rewritten into slugs
- Optional intranet mode behind basic auth
{project}/wwwLanding pages
Marketing sites with strictly typed content: the structure is fixed, the copy changes often — and changing it never touches the layout.
- Content written as semantic typed tags in MDX
- Images, PDFs and other assets served straight from the repository
- A single pages.config.js per site: title, contacts, logo, locales, menu
ProductItemcomponents/ProductItem.astroused by pages.gitt.one
<ProductSection>Two builder images, two kinds of website
Pick the image that matches what you are publishing. Everything else — the markdown pipeline, image optimization, SEO files, caching rules — is inherited from it.
{project}/docsKnowledge bases
The markdown files your team already writes in GitLab, published as a website. Clients read the site instead of walking into your repository.
- Plain .md and .mdx files, no front matter required
- README.md becomes the site root, links between .md files are rewritten into slugs
- Optional intranet mode behind basic auth
{project}/wwwLanding pages
Marketing sites with strictly typed content: the structure is fixed, the copy changes often — and changing it never touches the layout.
- Content written as semantic typed tags in MDX
- Images, PDFs and other assets served straight from the repository
- A single pages.config.js per site: title, contacts, logo, locales, menu
AudienceSectioncomponents/AudienceSection.astroused by pages.gitt.one
WHO IT IS FOR
Three ways a small website goes wrong
Gitt One Pages started as our own production line — we are its first and most demanding user.
If you commission websites
Your site is a hostage: it is built on whatever the studio that made it understands, so leaving means rewriting. The usual escape — a CMS of your own — buys you hosting bills, break-ins and updates.
Here the content is yours in plain files, and the site runs as a standard image on any hosting — including your own.
If you build websites
Every project is a unique artifact. A year later nobody remembers how to build it, the dependencies have rotted, and the developer who knew has left.
One conveyor for every site: the same builder image, the same pipeline, the same quality bar. Knowledge lives in conventions, not in people.
If you write the docs
Knowledge in markdown looks decent only inside GitLab. Handing it to a customer means either an invite to your repository or a website nobody has time to build.
Point a builder image at the repository and the same files become a site. Publishing costs a Dockerfile.
AudienceItemcomponents/AudienceItem.astroused by pages.gitt.one
<AudienceSection>WHO IT IS FOR
Three ways a small website goes wrong
Gitt One Pages started as our own production line — we are its first and most demanding user.
If you commission websites
Your site is a hostage: it is built on whatever the studio that made it understands, so leaving means rewriting. The usual escape — a CMS of your own — buys you hosting bills, break-ins and updates.
Here the content is yours in plain files, and the site runs as a standard image on any hosting — including your own.
If you build websites
Every project is a unique artifact. A year later nobody remembers how to build it, the dependencies have rotted, and the developer who knew has left.
One conveyor for every site: the same builder image, the same pipeline, the same quality bar. Knowledge lives in conventions, not in people.
If you write the docs
Knowledge in markdown looks decent only inside GitLab. Handing it to a customer means either an invite to your repository or a website nobody has time to build.
Point a builder image at the repository and the same files become a site. Publishing costs a Dockerfile.
ChecklistSectioncomponents/ChecklistSection.astroused by pages.gitt.one
THE QUALITY BAR
What every produced site gets
Not a per-project checklist to negotiate — these come from the builder image, so the newest site is as good as the best one.
- Lighthouse 100
- Performance, accessibility, best practices and SEO — the acceptance target for every site, measured on production
- Zero JavaScript by default
- Pages are plain pre-rendered markup; interactive pieces ship as small islands, so a contact form costs about a kilobyte
- Images done properly
- Responsive variants converted to webp at build time, with priority hints on the ones that decide your loading score
- Pre-compressed delivery
- Static files are compressed during the build and served ready-made by nginx, with immutable caching for hashed assets
- SEO out of the box
- Sitemap, robots.txt, per-page meta tags, favicon set and heading anchors that behave exactly like GitLab's
- Markdown that matches GitLab
- One rendering engine everywhere: tables, task lists, footnotes, syntax highlighting, Mermaid and PlantUML diagrams
- Cookieless analytics
- Self-hosted, privacy-preserving statistics by default — no cookies, and therefore no consent banner in your visitors' way
- Contact forms with spam protection
- A native HTML form, a lightweight challenge instead of a heavy captcha, and visible feedback when the message is sent
- Content validated at build time
- Typed content schemas and linting run in CI, so a broken link or a missing field fails the pipeline, not the visitor
ChecklistItemcomponents/ChecklistItem.astroused by pages.gitt.one
<ChecklistSection>THE QUALITY BAR
What every produced site gets
Not a per-project checklist to negotiate — these come from the builder image, so the newest site is as good as the best one.
- Lighthouse 100
- Performance, accessibility, best practices and SEO — the acceptance target for every site, measured on production
- Zero JavaScript by default
- Pages are plain pre-rendered markup; interactive pieces ship as small islands, so a contact form costs about a kilobyte
- Images done properly
- Responsive variants converted to webp at build time, with priority hints on the ones that decide your loading score
- Pre-compressed delivery
- Static files are compressed during the build and served ready-made by nginx, with immutable caching for hashed assets
- SEO out of the box
- Sitemap, robots.txt, per-page meta tags, favicon set and heading anchors that behave exactly like GitLab's
- Markdown that matches GitLab
- One rendering engine everywhere: tables, task lists, footnotes, syntax highlighting, Mermaid and PlantUML diagrams
- Cookieless analytics
- Self-hosted, privacy-preserving statistics by default — no cookies, and therefore no consent banner in your visitors' way
- Contact forms with spam protection
- A native HTML form, a lightweight challenge instead of a heavy captcha, and visible feedback when the message is sent
- Content validated at build time
- Typed content schemas and linting run in CI, so a broken link or a missing field fails the pipeline, not the visitor
StepsSectioncomponents/StepsSection.astroused by pages.gitt.one
What happens on push
The same four steps for every site produced by the technology — nothing bespoke per project.
- 1
Content lands in git
You edit markdown or typed content tags — in your IDE, in the GitLab web editor, or with an AI agent working on the repository
- 2
CI pulls the builder
A standard pipeline pulls the builder image; the engine and its locked dependencies come ready-made, so builds stay reproducible for years
- 3
Static output is built
Markdown is rendered, images are converted into responsive webp, files are pre-compressed and SEO files are generated
- 4
An image ships
The result is an ordinary ~50 MB nginx image — deploy it to our Kubernetes clusters or to any Docker hosting you control
StepItemcomponents/StepItem.astroused by pages.gitt.one
<StepsSection>What happens on push
The same four steps for every site produced by the technology — nothing bespoke per project.
- 1
Content lands in git
You edit markdown or typed content tags — in your IDE, in the GitLab web editor, or with an AI agent working on the repository
- 2
CI pulls the builder
A standard pipeline pulls the builder image; the engine and its locked dependencies come ready-made, so builds stay reproducible for years
- 3
Static output is built
Markdown is rendered, images are converted into responsive webp, files are pre-compressed and SEO files are generated
- 4
An image ships
The result is an ordinary ~50 MB nginx image — deploy it to our Kubernetes clusters or to any Docker hosting you control
SchemaSectioncomponents/SchemaSection.astroused by codeexpert.se
How do we make expectation and reality be equal?
- 1DATA DOMAIN analysis using entity relationship diagrams
- 2Working with domain experts using UBIQUITOUS language
- 3BUSINESS PROCESSES analysis with flowcharts, sequence diagrams
- 4SYSTEM analysis using component diagrams and design patterns
- 5Creating PROTOTYPE on pre-sale stage and approve UX and UI with customer
- 6A/B TESTING to compare two variants of a specific feature
SchemaItemcomponents/SchemaItem.astroused by codeexpert.se
The original measured the container width in JS: below the lg breakpoint (3-column grid) the arrow was shown after every item except the last of a row of 3; at lg and up (6-column grid) after every item except the last. Reproduce with responsive visibility classes instead of client JS.
<SchemaSection>How do we make expectation and reality be equal?
- 1DATA DOMAIN analysis using entity relationship diagrams
- 2Working with domain experts using UBIQUITOUS language
- 3BUSINESS PROCESSES analysis with flowcharts, sequence diagrams
- 4SYSTEM analysis using component diagrams and design patterns
- 5Creating PROTOTYPE on pre-sale stage and approve UX and UI with customer
- 6A/B TESTING to compare two variants of a specific feature
Offsetscomponents/Offsets.astroused by skattedosan.se
Big possibilities in small size
The technical aspect is expanding significantly, featuring Control Units storing over 32 million records with memory capacities ranging from 8GB to 128GB
Multiple devices support
Skattedosan is seamlessly adaptable and compatible with various cash solutions, requiring no external power source.
High capacity
Skattedosan boasts unmatched capabilities, storing 32+ million receipts, accommodating up to 1000 new organization numbers/cash pages, and supporting 9000 users. With a robust design, it withstands temperatures as low as -20°C, making it resilient in challenging environments.
Certified
Ensuring safety, Skattedosan is double-certified, meeting the regulations of the Swedish Tax Agency and earning certification from Kassacertifiering.se, distinguishing it in the industry.
AboutCertificationSectioncomponents/AboutCertificationSection.astroused by posexpert.se
Certification Project
Posexpert proceeds certification process for our new products and products we develop for our customers
Global tasks of the certification project:
Documentation and Requirements Analysis
- We thoroughly understand the updated legislation on control systems
Design
- We prepare the design and develop solutions for the information system to meet legislative requirements
Implementation and Testing
- We implement the code, prepare and conduct system testing
Documentation
- We prepare a document package for product certification
AboutCertificationItemcomponents/AboutCertificationItem.astroused by posexpert.se
<AboutCertificationSection>Certification Project
Posexpert proceeds certification process for our new products and products we develop for our customers
Global tasks of the certification project:
Documentation and Requirements Analysis
- We thoroughly understand the updated legislation on control systems
Design
- We prepare the design and develop solutions for the information system to meet legislative requirements
Implementation and Testing
- We implement the code, prepare and conduct system testing
Documentation
- We prepare a document package for product certification
CertificationSectioncomponents/CertificationSection.astroused by posexpert.se
Certification project steps
Documentation and Requirements Analysis
During the analysis phase, all requirements were broken down into separate parts in collaboration with the development team. Key requirements and those related to product security from the perspective of potential threats were identified. The necessary technological stack and tools for project implementation were chosen.
Design
Based on the analysis, a system design was developed, describing the main components, interaction protocols, and application structures. In addition to functional requirements, the design addresses aspects related to countering potential threats.
Implementation and Testing
After designing, the development team implemented everything in code. The main focus during project implementation was on tracing requirements in the code, meaning that the code should only contain functions required to comply with legislation. This required 100% code coverage with tests. The tests were designed to check each legislative requirement, as well as security requirements and requirements from the certification agency. End-to-end tests were also developed to assess system functioning.
Documentation
During product certification, special attention was paid to creating a document system for process management in the client company. Initially, documentation was absent, and some processes were missing. The project's task included both preparing documentation and establishing missing processes. Certification was conducted according to ISO 9001 standards with all associated requirements. The entire package of necessary documents was compiled, and a process management system was developed and implemented in the company. Processes were communicated to the company's employees.
CertificationItemcomponents/CertificationItem.astroused by posexpert.se
<CertificationSection>Certification project steps
Documentation and Requirements Analysis
During the analysis phase, all requirements were broken down into separate parts in collaboration with the development team. Key requirements and those related to product security from the perspective of potential threats were identified. The necessary technological stack and tools for project implementation were chosen.
Design
Based on the analysis, a system design was developed, describing the main components, interaction protocols, and application structures. In addition to functional requirements, the design addresses aspects related to countering potential threats.
Implementation and Testing
After designing, the development team implemented everything in code. The main focus during project implementation was on tracing requirements in the code, meaning that the code should only contain functions required to comply with legislation. This required 100% code coverage with tests. The tests were designed to check each legislative requirement, as well as security requirements and requirements from the certification agency. End-to-end tests were also developed to assess system functioning.
Documentation
During product certification, special attention was paid to creating a document system for process management in the client company. Initially, documentation was absent, and some processes were missing. The project's task included both preparing documentation and establishing missing processes. Certification was conducted according to ISO 9001 standards with all associated requirements. The entire package of necessary documents was compiled, and a process management system was developed and implemented in the company. Processes were communicated to the company's employees.
ProductQualitySectioncomponents/ProductQualitySection.astroused by codeexpert.se
How do we ensure product quality?
Quality comes from proper processes
- We do WELL-DESIGNED software ARCHITECTURE that ensures the scalability, maintainability, and longevity of the product
- We hold ARCHITECTURE MEETINGS where the team finds optimal architectural solutions
- We use coding STANDARDS: a codebase is self-documented, easy to learn and navigate
- We provide WELL-DOCUMENTED software
- We use almost all types of QA TESTING, both functional and non-functional
- CONTINUOUS INTEGRATION AND DELIVERY (CI/CD) is always used without exception
We work according to our own unique software development process: the whole process is divided into two parallel streams that run simultaneously: DEVELOPMENT in the current sprint and ANALYSIS for the next sprint. This approach is based on Kanban methodology, but with some differences, and provides psychological comfort to the developers.
David HamrenCEO at Code Expert
AboutUsSectioncomponents/AboutUsSection.astrohistory only
Custom POS solutions
We develop software for POS terminals, cash registers, and other payment processing devices. We build custom integrations with payment processors, inventory systems, or e-commerce platforms
MissionSectioncomponents/MissionSection.astroused by pages.gitt.one
HOW IT WORKS
A website is a content repository plus a standard image
The engine ships as a builder image with the framework and its dependencies already installed. Your repository holds content and a few lines of Dockerfile — no toolchain, no node_modules, no build configuration to maintain. CI turns the two into a static site and bakes it into an nginx image.
Source links point to engine-astro@e857a859. Samples are cut from the sites' own content by scripts/gallery-extract.mjs; nothing is merged or removed yet.