betaharp/turkce-git-rehberi

Purpose

This repository is a Turkish-language Git usage guide based on official Git documentation. It is a static documentation site, published through GitHub Pages at https://betaharp.github.io/Turkce-git-rehberi/#/.

Entry Points and Delivery

• Repository-level introduction and publication URL: README.md

• Rendered static-site entry document: docs/index.html

• Documentation-site-specific notes: docs/README.md

GitHub Pages is the material hosting infrastructure; no application server, backend runtime, database, or API integration is represented in the repository tree.

Documentation Site Root

The docs/ directory is the deployable site boundary. Its contents are intended to be served directly as static assets:

• docs/index.html

• docs/.nojekyll

• docs/images

docs/.nojekyll indicates Pages should serve the directory without Jekyll processing, preserving the site’s static asset layout and any client-side routing/resource conventions.

Content and Presentation Assets

The main HTML document establishes the reader-facing guide experience:

• docs/index.html

• docs/images

Images are isolated beneath docs/images, separating presentation media from the page shell. The supplied tree does not expose separate source-content directories, build scripts, or a package-managed frontend; documentation content is therefore likely embedded or referenced directly by the static site files.

Primary Flow

1. A maintainer edits repository documentation or static site files.

2. GitHub Pages publishes the docs/ site root.

3. A browser requests docs/index.html and associated assets under docs/images.

4. The guide is rendered entirely client-side/static, with no indicated server-side processing.

The primary architectural boundary is between repository metadata/contributor guidance and the publishable Pages directory.

Project Governance and Constraints

• Contribution expectations: CONTRIBUTING.md

• Licensing: LICENSE

• Git ignore rules: .gitignore

These govern repository changes but are outside the runtime delivery path. The project’s operational dependency is GitHub Pages; its content dependency is the official Git documentation described in README.md.