Website | Blog | Documentation | Contact/Schedule | Sponsor
No Clocks, LLC Website (https://noclocks.dev) built using React, TypeScript, and ...
Note
No Clocks, LLC is a new, cutting-edge, technology-based agency startup that seamlessly blends the expertise of seasoned Software Engineers, Web Developers, Data Engineers.
No Clocks, LLC is an avant-garde technology-based agency that brings together a dynamic team of Software Engineers, Web Developers, and Data Engineers. We thrive on innovation and our proficiency spans a multitude of programming languages and frameworks, making us a formidable force in technology consulting and development across various industries.
- Dynamic Web Presence: Our website is designed to be responsive, engaging, and informative, providing an in-depth look at our services and the unique value we bring to our clients.
- Interactive API: We use a custom-built API for dynamic content delivery and integration with backend services.
- Database Integration: Ensuring smooth data flow and security with our robust database administration.
- Infrastructure as Code (IaC): Leveraging modern DevOps practices to streamline and automate our cloud infrastructure.
This project is built using a mix of cutting-edge technologies that include:
- Modern Frontend Frameworks:
- Backend Technologies:
- Cloud Hosted Services:
- Database and Content Management:
- Third-Party API Integrations:
- Artificial Intelligence Tooling:
This repository houses the codebase for our official website hosted at https://noclocks.dev.
It serves as a digital showcase of our expertise and the services we offer, reflecting our commitment to excellence and our journey towards becoming an engineering powerhouse.
#TODO
The project structure is as follows:
.
├── .github
│ └── workflows
│ └── build.yml
├── .gitignore
├── LICENSE
To get started with the repository locally, first clone and install the repository:
git clone https://github.com/noclocks/noclocks.dev
cd noclocks.dev
bun install
if you prefer to use npm
, yarn
, or pnpm
, replace bun
with the preference package manager.
Next, setup your local environment variables:
cp .env.example .env
and populate .env
:
#TODO
...
#TODO
#TODO
#TODO
#TODO
We welcome contributions from the community, whether it's fixing bugs, improving the documentation, or proposing new features. Please read CONTRIBUTING.md for details on our code of conduct and the process for submitting pull requests to us.
- Email: dev@noclocks.dev
- Phone: +1 (678) 491-4856
Join us in redefining what's possible in technology and consulting by partnering with No Clocks, LLC – where technical prowess meets entrepreneurial vigor!
The root of the project contains the following files:
-
.gitignore
: A default.gitignore
file that can be used to ignore common files and directories. Currently it ignores typical files and directories for the following languages or frameworks:- Windows (i.e.
Thumbs.db
,desktop.ini
,.lnk
files, etc.) - macOS (i.e.
.DS_Store
files) - Python (i.e.
.venv
,.pyc
,.pyo
, etc.) - Node.js (i.e.
node_modules
,npm-debug.log
, etc.)
- Windows (i.e.
-
.gitattributes
: A default.gitattributes
file that can be used to specify attributes for the repository. Currently it applies attributes associated with the following languages or frameworks:- General Commonly Used Attributes
- Markdown
- PowerShell
- Python
- Web Development (i.e. HTML, CSS, JavaScript, etc.)
-
.editorconfig
: A default.editorconfig
file that can be used to define and maintain consistent coding styles between different editors and IDEs. -
LICENSE.md
: No Clocks Default Open Source License: Unlicense. -
README.template.md
: A template for the actual project'sREADME.md
file that can be used to provide information about the project. -
CHANGELOG.md
: A defaultCHANGELOG.md
file that can be used to provide a log of all changes made to the project.
The .github
directory contains the following files:
-
dependabot.yml
: A defaultdependabot.yml
file that can be used to configure Dependabot for the repository. -
workflows
: A directory that contains GitHub Actions workflows for the repository. Currently it contains the following workflow: