PHPackages                             jahudka/nittro-project - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. jahudka/nittro-project

ActiveProject

jahudka/nittro-project
======================

v1.1.0(7y ago)028[12 PRs](https://github.com/jahudka/nittro-project/pulls)MITPHPPHP ^7.1

Since Oct 21Pushed 3y ago1 watchersCompare

[ Source](https://github.com/jahudka/nittro-project)[ Packagist](https://packagist.org/packages/jahudka/nittro-project)[ RSS](/packages/jahudka-nittro-project/feed)WikiDiscussions master Synced 3d ago

READMEChangelogDependencies (15)Versions (18)Used By (0)

Nittro project skeleton
=======================

[](#nittro-project-skeleton)

This is a simple skeleton for a Nette project with Nittro via Gulp, Doctrine via Kdyby and a basic admin template based on Bootstrap v4. PHP 7.1 is required.

### Installation

[](#installation)

```
composer create-project jahudka/nittro-project myproject
cd myproject
.ci/build
cp etc/config.local.dist etc/config.local.neon
$EDITOR etc/config.local.neon
bin/console orm:schema-tool:create
```

### Application layout

[](#application-layout)

- Configuration is stored in `./etc`.
- Executable console tool is at `./bin/console`.
- All application sources are under `./src`, which is a PSR-4 namespace root for the `App` namespace; autoloading in this namespace is provided by Composer.
- All caches and logs, as well as sessions, are under `./var`.

### Doctrine

[](#doctrine)

- Entities reside in `./src/Entity`.
- A default entity exists for user identity, users can be managed using the console tool's `user:*` family of commands.

### Components

[](#components)

- There is an abstract base class `App\UI\BaseControl` which adds the `setView(string $view)`, `getView()` and `render()` methods; components extending this class will be rendered using a latte template located at `/templates/.latte`.
- As a convenience, all interfaces with a single method called `create`defined in either the common `./src/Components` or the per-module `Components` directories are automatically registered in the DI container (unless a service implementing the interface already exists).

### Assets

[](#assets)

- All assets are managed and compiled using Gulp.
- As a convention, assets specific to each module are in the module's `assets` subdirectory while (potentially) common assets are in the `./src/assets` directory.
- There are many available Gulp tasks to build all the individual assets, as well as a couple of watch tasks to make life easier during development. They are named according to the following convention: ```
    task := [ watch ] [:] [ public|admin ] [:] [ js|css|fonts ]

    ```

    You can think of the task names as a list of tags separated by a colon. The `watch` tag doesn't work with the `fonts` tag, but otherwise all combinations are allowed. Omitting any tag except the `watch` tag is the same as if you specified all the permutations of the tag, e.g. `watch:js` is the same as `watch:public:js watch:admin:js`and `public` is the same as `public:js public:css public:fonts`.
- The default task builds everything.
- Nittro components are enabled at the beginning of the gulpfile using configuration flags of the builder instances; additional libraries from other vendors as well as your custom code can be specified there as well. Reading the source of the gulpfile should make everything clear.
- All non-minified javascripts are minified, all LESS styles are compiled and all non-minified styles are minified.
- Bootstrap for Nittro is generated automatically.

### Console

[](#console)

- There are a number of useful Doctrine-related commands defined by the `kdyby/doctrine` package - those are available as usual.
- There are also a couple of commands for user management as mentioned previously.
- As a convenience, all classes in the common `./src/Commands` or the per-module `Commands` directories that extend Symfony's `Command`class are automatically registered in the DI container and tagged with the `kdyby.console.command` tag (unless a service of the same type already exists).

###  Health Score

28

—

LowBetter than 54% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity7

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity67

Established project with proven stability

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~85 days

Total

5

Last Release

2787d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/330635?v=4)[jahudka](/maintainers/jahudka)[@jahudka](https://github.com/jahudka)

---

Top Contributors

[![jahudka](https://avatars.githubusercontent.com/u/330635?v=4)](https://github.com/jahudka "jahudka (12 commits)")

### Embed Badge

![Health badge](/badges/jahudka-nittro-project/health.svg)

```
[![Health](https://phpackages.com/badges/jahudka-nittro-project/health.svg)](https://phpackages.com/packages/jahudka-nittro-project)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)