Download the PHP package nawasara/docs without Composer

On this page you can find all versions of the php package nawasara/docs. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package docs

Nawasara Docs

Internal Nawasara documentation, living inside the app at /nawasara-docs.

Its content is read from the running code, not from separate notes. The endpoint list comes from the route table, the scope list from the registry, the component catalog from the nawasara/ui blade files, and the guides from markdown files already in the repo. Documentation that copies its source goes stale without anyone noticing; documentation that reads from the source cannot.

Contents

Page Source
Component catalog scans packages/nawasara-ui/resources/views/components/**
API reference Route::getRoutes() plus ScopeRegistry::grouped()
Authentication and tokens written by hand, explains the flow rather than listing data
Install the secscan agent packages/nawasara-secscan/README.md from line 132
Creating a new package AGENTS.md

The API page also flags two things that raise no error anywhere: a scope a route uses but that has not been registered (the endpoint is locked for all tokens), and a registered scope that no route uses (a middleware was probably left off).

Access

Behind auth and the docs.page.view permission. It appears in the sidebar under the Pengaturan group.

Only view, there is no create/update/delete. Documentation content is built from files and the runtime catalog, not from a database, so nothing can be edited through the panel; a write permission would only gate a page that does not exist.

The seeder grants this permission to every existing role, not just developer. Documentation is how you use the system, and gating it to developers only takes the guide away from the people who need it most: OPD operators new to the system. What changed is that the permission can now be revoked per role.

Notes

Seed before deploying this version. The menu previously used permission => null, so every account holder saw it. Without the seeder, the Documentation workspace disappears from everyone's sidebar, because WorkspaceManager::accessible() filters by a permission that does not exist yet.

Gating happens in two places, and both are needed: config/menu.php hides the menu, and routes/web.php rejects the URL. Hiding the menu alone still leaves the address typeable directly.

Notes for changes

The catalog is cached for 5 minutes. While editing a component, call POST /nawasara-docs/refresh or run php artisan cache:clear so changes show up right away.

Component documentation is not uniform. Some files have a {{-- --}} block at the top with a Pemakaian: section, some have only per-prop comments, some have none. The catalog page flags the undocumented ones instead of hiding them, so the list doubles as a task list. The most complete format is in components/badge.blade.php; follow that.

Tailwind needs two @source lines. In resources/css/app.css this package is registered via packages/ and via vendor/. The first is for local dev, because vendor/nawasara/docs on Windows is a junction and Tailwind does not follow it; the second is for the build server, where packages/ is empty.

Docs pages are static views, not Livewire. The x-nawasara-ui::form.* components rely on a Livewire context and will throw Using $this when not in object context if used here. Use native elements for simple needs like a client-side search box.

Adding a page

  1. Create a blade in resources/views/pages/
  2. Register the route in routes/web.php inside the existing group. That group already carries auth plus docs.page.view, so a new page is gated too without having to remember it each time.
  3. Add it to src/Support/DocsNavigation.php. The docs sidebar and the index page both read from there, so one place is enough.
  4. If it needs to appear in the app sidebar, add it to config/menu.php as well.

Author

Pringgo J. Saputro <[email protected]>

License

MIT


All versions of docs with dependencies

PHP Build Version
Package Version
Requires php Version ^8.1
illuminate/support Version ^10.0|^12.0
nawasara/ui Version *
livewire/livewire Version ^3.0
league/commonmark Version ^2.4
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package nawasara/docs contains the following files

Loading the files please wait ...