Merge branch 'develop'
Deploy to Development and Production / deploy (push) Successful in 3m0s
Details
Deploy to Development and Production / deploy (push) Successful in 3m0s
Details
# Conflicts: # cene-in-reference/index.html # code_export.txt
This commit is contained in:
Mark Poljanšek
commit
11081b665f
|
|
@ -0,0 +1,188 @@
|
|||
description = "Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation."
|
||||
|
||||
prompt = """
|
||||
---
|
||||
description: Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
|
||||
---
|
||||
|
||||
## User Input
|
||||
|
||||
```text
|
||||
$ARGUMENTS
|
||||
```
|
||||
|
||||
You **MUST** consider the user input before proceeding (if not empty).
|
||||
|
||||
## Goal
|
||||
|
||||
Identify inconsistencies, duplications, ambiguities, and underspecified items across the three core artifacts (`spec.md`, `plan.md`, `tasks.md`) before implementation. This command MUST run only after `/speckit.tasks` has successfully produced a complete `tasks.md`.
|
||||
|
||||
## Operating Constraints
|
||||
|
||||
**STRICTLY READ-ONLY**: Do **not** modify any files. Output a structured analysis report. Offer an optional remediation plan (user must explicitly approve before any follow-up editing commands would be invoked manually).
|
||||
|
||||
**Constitution Authority**: The project constitution (`.specify/memory/constitution.md`) is **non-negotiable** within this analysis scope. Constitution conflicts are automatically CRITICAL and require adjustment of the spec, plan, or tasks—not dilution, reinterpretation, or silent ignoring of the principle. If a principle itself needs to change, that must occur in a separate, explicit constitution update outside `/speckit.analyze`.
|
||||
|
||||
## Execution Steps
|
||||
|
||||
### 1. Initialize Analysis Context
|
||||
|
||||
Run `.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks` once from repo root and parse JSON for FEATURE_DIR and AVAILABLE_DOCS. Derive absolute paths:
|
||||
|
||||
- SPEC = FEATURE_DIR/spec.md
|
||||
- PLAN = FEATURE_DIR/plan.md
|
||||
- TASKS = FEATURE_DIR/tasks.md
|
||||
|
||||
Abort with an error message if any required file is missing (instruct the user to run missing prerequisite command).
|
||||
For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: "I'm Groot").
|
||||
|
||||
### 2. Load Artifacts (Progressive Disclosure)
|
||||
|
||||
Load only the minimal necessary context from each artifact:
|
||||
|
||||
**From spec.md:**
|
||||
|
||||
- Overview/Context
|
||||
- Functional Requirements
|
||||
- Non-Functional Requirements
|
||||
- User Stories
|
||||
- Edge Cases (if present)
|
||||
|
||||
**From plan.md:**
|
||||
|
||||
- Architecture/stack choices
|
||||
- Data Model references
|
||||
- Phases
|
||||
- Technical constraints
|
||||
|
||||
**From tasks.md:**
|
||||
|
||||
- Task IDs
|
||||
- Descriptions
|
||||
- Phase grouping
|
||||
- Parallel markers [P]
|
||||
- Referenced file paths
|
||||
|
||||
**From constitution:**
|
||||
|
||||
- Load `.specify/memory/constitution.md` for principle validation
|
||||
|
||||
### 3. Build Semantic Models
|
||||
|
||||
Create internal representations (do not include raw artifacts in output):
|
||||
|
||||
- **Requirements inventory**: Each functional + non-functional requirement with a stable key (derive slug based on imperative phrase; e.g., "User can upload file" → `user-can-upload-file`)
|
||||
- **User story/action inventory**: Discrete user actions with acceptance criteria
|
||||
- **Task coverage mapping**: Map each task to one or more requirements or stories (inference by keyword / explicit reference patterns like IDs or key phrases)
|
||||
- **Constitution rule set**: Extract principle names and MUST/SHOULD normative statements
|
||||
|
||||
### 4. Detection Passes (Token-Efficient Analysis)
|
||||
|
||||
Focus on high-signal findings. Limit to 50 findings total; aggregate remainder in overflow summary.
|
||||
|
||||
#### A. Duplication Detection
|
||||
|
||||
- Identify near-duplicate requirements
|
||||
- Mark lower-quality phrasing for consolidation
|
||||
|
||||
#### B. Ambiguity Detection
|
||||
|
||||
- Flag vague adjectives (fast, scalable, secure, intuitive, robust) lacking measurable criteria
|
||||
- Flag unresolved placeholders (TODO, TKTK, ???, `<placeholder>`, etc.)
|
||||
|
||||
#### C. Underspecification
|
||||
|
||||
- Requirements with verbs but missing object or measurable outcome
|
||||
- User stories missing acceptance criteria alignment
|
||||
- Tasks referencing files or components not defined in spec/plan
|
||||
|
||||
#### D. Constitution Alignment
|
||||
|
||||
- Any requirement or plan element conflicting with a MUST principle
|
||||
- Missing mandated sections or quality gates from constitution
|
||||
|
||||
#### E. Coverage Gaps
|
||||
|
||||
- Requirements with zero associated tasks
|
||||
- Tasks with no mapped requirement/story
|
||||
- Non-functional requirements not reflected in tasks (e.g., performance, security)
|
||||
|
||||
#### F. Inconsistency
|
||||
|
||||
- Terminology drift (same concept named differently across files)
|
||||
- Data entities referenced in plan but absent in spec (or vice versa)
|
||||
- Task ordering contradictions (e.g., integration tasks before foundational setup tasks without dependency note)
|
||||
- Conflicting requirements (e.g., one requires Next.js while other specifies Vue)
|
||||
|
||||
### 5. Severity Assignment
|
||||
|
||||
Use this heuristic to prioritize findings:
|
||||
|
||||
- **CRITICAL**: Violates constitution MUST, missing core spec artifact, or requirement with zero coverage that blocks baseline functionality
|
||||
- **HIGH**: Duplicate or conflicting requirement, ambiguous security/performance attribute, untestable acceptance criterion
|
||||
- **MEDIUM**: Terminology drift, missing non-functional task coverage, underspecified edge case
|
||||
- **LOW**: Style/wording improvements, minor redundancy not affecting execution order
|
||||
|
||||
### 6. Produce Compact Analysis Report
|
||||
|
||||
Output a Markdown report (no file writes) with the following structure:
|
||||
|
||||
## Specification Analysis Report
|
||||
|
||||
| ID | Category | Severity | Location(s) | Summary | Recommendation |
|
||||
|----|----------|----------|-------------|---------|----------------|
|
||||
| A1 | Duplication | HIGH | spec.md:L120-134 | Two similar requirements ... | Merge phrasing; keep clearer version |
|
||||
|
||||
(Add one row per finding; generate stable IDs prefixed by category initial.)
|
||||
|
||||
**Coverage Summary Table:**
|
||||
|
||||
| Requirement Key | Has Task? | Task IDs | Notes |
|
||||
|-----------------|-----------|----------|-------|
|
||||
|
||||
**Constitution Alignment Issues:** (if any)
|
||||
|
||||
**Unmapped Tasks:** (if any)
|
||||
|
||||
**Metrics:**
|
||||
|
||||
- Total Requirements
|
||||
- Total Tasks
|
||||
- Coverage % (requirements with >=1 task)
|
||||
- Ambiguity Count
|
||||
- Duplication Count
|
||||
- Critical Issues Count
|
||||
|
||||
### 7. Provide Next Actions
|
||||
|
||||
At end of report, output a concise Next Actions block:
|
||||
|
||||
- If CRITICAL issues exist: Recommend resolving before `/speckit.implement`
|
||||
- If only LOW/MEDIUM: User may proceed, but provide improvement suggestions
|
||||
- Provide explicit command suggestions: e.g., "Run /speckit.specify with refinement", "Run /speckit.plan to adjust architecture", "Manually edit tasks.md to add coverage for 'performance-metrics'"
|
||||
|
||||
### 8. Offer Remediation
|
||||
|
||||
Ask the user: "Would you like me to suggest concrete remediation edits for the top N issues?" (Do NOT apply them automatically.)
|
||||
|
||||
## Operating Principles
|
||||
|
||||
### Context Efficiency
|
||||
|
||||
- **Minimal high-signal tokens**: Focus on actionable findings, not exhaustive documentation
|
||||
- **Progressive disclosure**: Load artifacts incrementally; don't dump all content into analysis
|
||||
- **Token-efficient output**: Limit findings table to 50 rows; summarize overflow
|
||||
- **Deterministic results**: Rerunning without changes should produce consistent IDs and counts
|
||||
|
||||
### Analysis Guidelines
|
||||
|
||||
- **NEVER modify files** (this is read-only analysis)
|
||||
- **NEVER hallucinate missing sections** (if absent, report them accurately)
|
||||
- **Prioritize constitution violations** (these are always CRITICAL)
|
||||
- **Use examples over exhaustive rules** (cite specific instances, not generic patterns)
|
||||
- **Report zero issues gracefully** (emit success report with coverage statistics)
|
||||
|
||||
## Context
|
||||
|
||||
{{args}}
|
||||
"""
|
||||
|
|
@ -0,0 +1,298 @@
|
|||
description = "Generate a custom checklist for the current feature based on user requirements."
|
||||
|
||||
prompt = """
|
||||
---
|
||||
description: Generate a custom checklist for the current feature based on user requirements.
|
||||
---
|
||||
|
||||
## Checklist Purpose: "Unit Tests for English"
|
||||
|
||||
**CRITICAL CONCEPT**: Checklists are **UNIT TESTS FOR REQUIREMENTS WRITING** - they validate the quality, clarity, and completeness of requirements in a given domain.
|
||||
|
||||
**NOT for verification/testing**:
|
||||
|
||||
- ❌ NOT "Verify the button clicks correctly"
|
||||
- ❌ NOT "Test error handling works"
|
||||
- ❌ NOT "Confirm the API returns 200"
|
||||
- ❌ NOT checking if code/implementation matches the spec
|
||||
|
||||
**FOR requirements quality validation**:
|
||||
|
||||
- ✅ "Are visual hierarchy requirements defined for all card types?" (completeness)
|
||||
- ✅ "Is 'prominent display' quantified with specific sizing/positioning?" (clarity)
|
||||
- ✅ "Are hover state requirements consistent across all interactive elements?" (consistency)
|
||||
- ✅ "Are accessibility requirements defined for keyboard navigation?" (coverage)
|
||||
- ✅ "Does the spec define what happens when logo image fails to load?" (edge cases)
|
||||
|
||||
**Metaphor**: If your spec is code written in English, the checklist is its unit test suite. You're testing whether the requirements are well-written, complete, unambiguous, and ready for implementation - NOT whether the implementation works.
|
||||
|
||||
## User Input
|
||||
|
||||
```text
|
||||
$ARGUMENTS
|
||||
```
|
||||
|
||||
You **MUST** consider the user input before proceeding (if not empty).
|
||||
|
||||
## Execution Steps
|
||||
|
||||
1. **Setup**: Run `.specify/scripts/bash/check-prerequisites.sh --json` from repo root and parse JSON for FEATURE_DIR and AVAILABLE_DOCS list.
|
||||
- All file paths must be absolute.
|
||||
- For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: "I'm Groot").
|
||||
|
||||
2. **Clarify intent (dynamic)**: Derive up to THREE initial contextual clarifying questions (no pre-baked catalog). They MUST:
|
||||
- Be generated from the user's phrasing + extracted signals from spec/plan/tasks
|
||||
- Only ask about information that materially changes checklist content
|
||||
- Be skipped individually if already unambiguous in `$ARGUMENTS`
|
||||
- Prefer precision over breadth
|
||||
|
||||
Generation algorithm:
|
||||
1. Extract signals: feature domain keywords (e.g., auth, latency, UX, API), risk indicators ("critical", "must", "compliance"), stakeholder hints ("QA", "review", "security team"), and explicit deliverables ("a11y", "rollback", "contracts").
|
||||
2. Cluster signals into candidate focus areas (max 4) ranked by relevance.
|
||||
3. Identify probable audience & timing (author, reviewer, QA, release) if not explicit.
|
||||
4. Detect missing dimensions: scope breadth, depth/rigor, risk emphasis, exclusion boundaries, measurable acceptance criteria.
|
||||
5. Formulate questions chosen from these archetypes:
|
||||
- Scope refinement (e.g., "Should this include integration touchpoints with X and Y or stay limited to local module correctness?")
|
||||
- Risk prioritization (e.g., "Which of these potential risk areas should receive mandatory gating checks?")
|
||||
- Depth calibration (e.g., "Is this a lightweight pre-commit sanity list or a formal release gate?")
|
||||
- Audience framing (e.g., "Will this be used by the author only or peers during PR review?")
|
||||
- Boundary exclusion (e.g., "Should we explicitly exclude performance tuning items this round?")
|
||||
- Scenario class gap (e.g., "No recovery flows detected—are rollback / partial failure paths in scope?")
|
||||
|
||||
Question formatting rules:
|
||||
- If presenting options, generate a compact table with columns: Option | Candidate | Why It Matters
|
||||
- Limit to A–E options maximum; omit table if a free-form answer is clearer
|
||||
- Never ask the user to restate what they already said
|
||||
- Avoid speculative categories (no hallucination). If uncertain, ask explicitly: "Confirm whether X belongs in scope."
|
||||
|
||||
Defaults when interaction impossible:
|
||||
- Depth: Standard
|
||||
- Audience: Reviewer (PR) if code-related; Author otherwise
|
||||
- Focus: Top 2 relevance clusters
|
||||
|
||||
Output the questions (label Q1/Q2/Q3). After answers: if ≥2 scenario classes (Alternate / Exception / Recovery / Non-Functional domain) remain unclear, you MAY ask up to TWO more targeted follow‑ups (Q4/Q5) with a one-line justification each (e.g., "Unresolved recovery path risk"). Do not exceed five total questions. Skip escalation if user explicitly declines more.
|
||||
|
||||
3. **Understand user request**: Combine `$ARGUMENTS` + clarifying answers:
|
||||
- Derive checklist theme (e.g., security, review, deploy, ux)
|
||||
- Consolidate explicit must-have items mentioned by user
|
||||
- Map focus selections to category scaffolding
|
||||
- Infer any missing context from spec/plan/tasks (do NOT hallucinate)
|
||||
|
||||
4. **Load feature context**: Read from FEATURE_DIR:
|
||||
- spec.md: Feature requirements and scope
|
||||
- plan.md (if exists): Technical details, dependencies
|
||||
- tasks.md (if exists): Implementation tasks
|
||||
|
||||
**Context Loading Strategy**:
|
||||
- Load only necessary portions relevant to active focus areas (avoid full-file dumping)
|
||||
- Prefer summarizing long sections into concise scenario/requirement bullets
|
||||
- Use progressive disclosure: add follow-on retrieval only if gaps detected
|
||||
- If source docs are large, generate interim summary items instead of embedding raw text
|
||||
|
||||
5. **Generate checklist** - Create "Unit Tests for Requirements":
|
||||
- Create `FEATURE_DIR/checklists/` directory if it doesn't exist
|
||||
- Generate unique checklist filename:
|
||||
- Use short, descriptive name based on domain (e.g., `ux.md`, `api.md`, `security.md`)
|
||||
- Format: `[domain].md`
|
||||
- If file exists, append to existing file
|
||||
- Number items sequentially starting from CHK001
|
||||
- Each `/speckit.checklist` run creates a NEW file (never overwrites existing checklists)
|
||||
|
||||
**CORE PRINCIPLE - Test the Requirements, Not the Implementation**:
|
||||
Every checklist item MUST evaluate the REQUIREMENTS THEMSELVES for:
|
||||
- **Completeness**: Are all necessary requirements present?
|
||||
- **Clarity**: Are requirements unambiguous and specific?
|
||||
- **Consistency**: Do requirements align with each other?
|
||||
- **Measurability**: Can requirements be objectively verified?
|
||||
- **Coverage**: Are all scenarios/edge cases addressed?
|
||||
|
||||
**Category Structure** - Group items by requirement quality dimensions:
|
||||
- **Requirement Completeness** (Are all necessary requirements documented?)
|
||||
- **Requirement Clarity** (Are requirements specific and unambiguous?)
|
||||
- **Requirement Consistency** (Do requirements align without conflicts?)
|
||||
- **Acceptance Criteria Quality** (Are success criteria measurable?)
|
||||
- **Scenario Coverage** (Are all flows/cases addressed?)
|
||||
- **Edge Case Coverage** (Are boundary conditions defined?)
|
||||
- **Non-Functional Requirements** (Performance, Security, Accessibility, etc. - are they specified?)
|
||||
- **Dependencies & Assumptions** (Are they documented and validated?)
|
||||
- **Ambiguities & Conflicts** (What needs clarification?)
|
||||
|
||||
**HOW TO WRITE CHECKLIST ITEMS - "Unit Tests for English"**:
|
||||
|
||||
❌ **WRONG** (Testing implementation):
|
||||
- "Verify landing page displays 3 episode cards"
|
||||
- "Test hover states work on desktop"
|
||||
- "Confirm logo click navigates home"
|
||||
|
||||
✅ **CORRECT** (Testing requirements quality):
|
||||
- "Are the exact number and layout of featured episodes specified?" [Completeness]
|
||||
- "Is 'prominent display' quantified with specific sizing/positioning?" [Clarity]
|
||||
- "Are hover state requirements consistent across all interactive elements?" [Consistency]
|
||||
- "Are keyboard navigation requirements defined for all interactive UI?" [Coverage]
|
||||
- "Is the fallback behavior specified when logo image fails to load?" [Edge Cases]
|
||||
- "Are loading states defined for asynchronous episode data?" [Completeness]
|
||||
- "Does the spec define visual hierarchy for competing UI elements?" [Clarity]
|
||||
|
||||
**ITEM STRUCTURE**:
|
||||
Each item should follow this pattern:
|
||||
- Question format asking about requirement quality
|
||||
- Focus on what's WRITTEN (or not written) in the spec/plan
|
||||
- Include quality dimension in brackets [Completeness/Clarity/Consistency/etc.]
|
||||
- Reference spec section `[Spec §X.Y]` when checking existing requirements
|
||||
- Use `[Gap]` marker when checking for missing requirements
|
||||
|
||||
**EXAMPLES BY QUALITY DIMENSION**:
|
||||
|
||||
Completeness:
|
||||
- "Are error handling requirements defined for all API failure modes? [Gap]"
|
||||
- "Are accessibility requirements specified for all interactive elements? [Completeness]"
|
||||
- "Are mobile breakpoint requirements defined for responsive layouts? [Gap]"
|
||||
|
||||
Clarity:
|
||||
- "Is 'fast loading' quantified with specific timing thresholds? [Clarity, Spec §NFR-2]"
|
||||
- "Are 'related episodes' selection criteria explicitly defined? [Clarity, Spec §FR-5]"
|
||||
- "Is 'prominent' defined with measurable visual properties? [Ambiguity, Spec §FR-4]"
|
||||
|
||||
Consistency:
|
||||
- "Do navigation requirements align across all pages? [Consistency, Spec §FR-10]"
|
||||
- "Are card component requirements consistent between landing and detail pages? [Consistency]"
|
||||
|
||||
Coverage:
|
||||
- "Are requirements defined for zero-state scenarios (no episodes)? [Coverage, Edge Case]"
|
||||
- "Are concurrent user interaction scenarios addressed? [Coverage, Gap]"
|
||||
- "Are requirements specified for partial data loading failures? [Coverage, Exception Flow]"
|
||||
|
||||
Measurability:
|
||||
- "Are visual hierarchy requirements measurable/testable? [Acceptance Criteria, Spec §FR-1]"
|
||||
- "Can 'balanced visual weight' be objectively verified? [Measurability, Spec §FR-2]"
|
||||
|
||||
**Scenario Classification & Coverage** (Requirements Quality Focus):
|
||||
- Check if requirements exist for: Primary, Alternate, Exception/Error, Recovery, Non-Functional scenarios
|
||||
- For each scenario class, ask: "Are [scenario type] requirements complete, clear, and consistent?"
|
||||
- If scenario class missing: "Are [scenario type] requirements intentionally excluded or missing? [Gap]"
|
||||
- Include resilience/rollback when state mutation occurs: "Are rollback requirements defined for migration failures? [Gap]"
|
||||
|
||||
**Traceability Requirements**:
|
||||
- MINIMUM: ≥80% of items MUST include at least one traceability reference
|
||||
- Each item should reference: spec section `[Spec §X.Y]`, or use markers: `[Gap]`, `[Ambiguity]`, `[Conflict]`, `[Assumption]`
|
||||
- If no ID system exists: "Is a requirement & acceptance criteria ID scheme established? [Traceability]"
|
||||
|
||||
**Surface & Resolve Issues** (Requirements Quality Problems):
|
||||
Ask questions about the requirements themselves:
|
||||
- Ambiguities: "Is the term 'fast' quantified with specific metrics? [Ambiguity, Spec §NFR-1]"
|
||||
- Conflicts: "Do navigation requirements conflict between §FR-10 and §FR-10a? [Conflict]"
|
||||
- Assumptions: "Is the assumption of 'always available podcast API' validated? [Assumption]"
|
||||
- Dependencies: "Are external podcast API requirements documented? [Dependency, Gap]"
|
||||
- Missing definitions: "Is 'visual hierarchy' defined with measurable criteria? [Gap]"
|
||||
|
||||
**Content Consolidation**:
|
||||
- Soft cap: If raw candidate items > 40, prioritize by risk/impact
|
||||
- Merge near-duplicates checking the same requirement aspect
|
||||
- If >5 low-impact edge cases, create one item: "Are edge cases X, Y, Z addressed in requirements? [Coverage]"
|
||||
|
||||
**🚫 ABSOLUTELY PROHIBITED** - These make it an implementation test, not a requirements test:
|
||||
- ❌ Any item starting with "Verify", "Test", "Confirm", "Check" + implementation behavior
|
||||
- ❌ References to code execution, user actions, system behavior
|
||||
- ❌ "Displays correctly", "works properly", "functions as expected"
|
||||
- ❌ "Click", "navigate", "render", "load", "execute"
|
||||
- ❌ Test cases, test plans, QA procedures
|
||||
- ❌ Implementation details (frameworks, APIs, algorithms)
|
||||
|
||||
**✅ REQUIRED PATTERNS** - These test requirements quality:
|
||||
- ✅ "Are [requirement type] defined/specified/documented for [scenario]?"
|
||||
- ✅ "Is [vague term] quantified/clarified with specific criteria?"
|
||||
- ✅ "Are requirements consistent between [section A] and [section B]?"
|
||||
- ✅ "Can [requirement] be objectively measured/verified?"
|
||||
- ✅ "Are [edge cases/scenarios] addressed in requirements?"
|
||||
- ✅ "Does the spec define [missing aspect]?"
|
||||
|
||||
6. **Structure Reference**: Generate the checklist following the canonical template in `.specify/templates/checklist-template.md` for title, meta section, category headings, and ID formatting. If template is unavailable, use: H1 title, purpose/created meta lines, `##` category sections containing `- [ ] CHK### <requirement item>` lines with globally incrementing IDs starting at CHK001.
|
||||
|
||||
7. **Report**: Output full path to created checklist, item count, and remind user that each run creates a new file. Summarize:
|
||||
- Focus areas selected
|
||||
- Depth level
|
||||
- Actor/timing
|
||||
- Any explicit user-specified must-have items incorporated
|
||||
|
||||
**Important**: Each `/speckit.checklist` command invocation creates a checklist file using short, descriptive names unless file already exists. This allows:
|
||||
|
||||
- Multiple checklists of different types (e.g., `ux.md`, `test.md`, `security.md`)
|
||||
- Simple, memorable filenames that indicate checklist purpose
|
||||
- Easy identification and navigation in the `checklists/` folder
|
||||
|
||||
To avoid clutter, use descriptive types and clean up obsolete checklists when done.
|
||||
|
||||
## Example Checklist Types & Sample Items
|
||||
|
||||
**UX Requirements Quality:** `ux.md`
|
||||
|
||||
Sample items (testing the requirements, NOT the implementation):
|
||||
|
||||
- "Are visual hierarchy requirements defined with measurable criteria? [Clarity, Spec §FR-1]"
|
||||
- "Is the number and positioning of UI elements explicitly specified? [Completeness, Spec §FR-1]"
|
||||
- "Are interaction state requirements (hover, focus, active) consistently defined? [Consistency]"
|
||||
- "Are accessibility requirements specified for all interactive elements? [Coverage, Gap]"
|
||||
- "Is fallback behavior defined when images fail to load? [Edge Case, Gap]"
|
||||
- "Can 'prominent display' be objectively measured? [Measurability, Spec §FR-4]"
|
||||
|
||||
**API Requirements Quality:** `api.md`
|
||||
|
||||
Sample items:
|
||||
|
||||
- "Are error response formats specified for all failure scenarios? [Completeness]"
|
||||
- "Are rate limiting requirements quantified with specific thresholds? [Clarity]"
|
||||
- "Are authentication requirements consistent across all endpoints? [Consistency]"
|
||||
- "Are retry/timeout requirements defined for external dependencies? [Coverage, Gap]"
|
||||
- "Is versioning strategy documented in requirements? [Gap]"
|
||||
|
||||
**Performance Requirements Quality:** `performance.md`
|
||||
|
||||
Sample items:
|
||||
|
||||
- "Are performance requirements quantified with specific metrics? [Clarity]"
|
||||
- "Are performance targets defined for all critical user journeys? [Coverage]"
|
||||
- "Are performance requirements under different load conditions specified? [Completeness]"
|
||||
- "Can performance requirements be objectively measured? [Measurability]"
|
||||
- "Are degradation requirements defined for high-load scenarios? [Edge Case, Gap]"
|
||||
|
||||
**Security Requirements Quality:** `security.md`
|
||||
|
||||
Sample items:
|
||||
|
||||
- "Are authentication requirements specified for all protected resources? [Coverage]"
|
||||
- "Are data protection requirements defined for sensitive information? [Completeness]"
|
||||
- "Is the threat model documented and requirements aligned to it? [Traceability]"
|
||||
- "Are security requirements consistent with compliance obligations? [Consistency]"
|
||||
- "Are security failure/breach response requirements defined? [Gap, Exception Flow]"
|
||||
|
||||
## Anti-Examples: What NOT To Do
|
||||
|
||||
**❌ WRONG - These test implementation, not requirements:**
|
||||
|
||||
```markdown
|
||||
- [ ] CHK001 - Verify landing page displays 3 episode cards [Spec §FR-001]
|
||||
- [ ] CHK002 - Test hover states work correctly on desktop [Spec §FR-003]
|
||||
- [ ] CHK003 - Confirm logo click navigates to home page [Spec §FR-010]
|
||||
- [ ] CHK004 - Check that related episodes section shows 3-5 items [Spec §FR-005]
|
||||
```
|
||||
|
||||
**✅ CORRECT - These test requirements quality:**
|
||||
|
||||
```markdown
|
||||
- [ ] CHK001 - Are the number and layout of featured episodes explicitly specified? [Completeness, Spec §FR-001]
|
||||
- [ ] CHK002 - Are hover state requirements consistently defined for all interactive elements? [Consistency, Spec §FR-003]
|
||||
- [ ] CHK003 - Are navigation requirements clear for all clickable brand elements? [Clarity, Spec §FR-010]
|
||||
- [ ] CHK004 - Is the selection criteria for related episodes documented? [Gap, Spec §FR-005]
|
||||
- [ ] CHK005 - Are loading state requirements defined for asynchronous episode data? [Gap]
|
||||
- [ ] CHK006 - Can "visual hierarchy" requirements be objectively measured? [Measurability, Spec §FR-001]
|
||||
```
|
||||
|
||||
**Key Differences:**
|
||||
|
||||
- Wrong: Tests if the system works correctly
|
||||
- Correct: Tests if the requirements are written correctly
|
||||
- Wrong: Verification of behavior
|
||||
- Correct: Validation of requirement quality
|
||||
- Wrong: "Does it do X?"
|
||||
- Correct: "Is X clearly specified?"
|
||||
"""
|
||||
|
|
@ -0,0 +1,185 @@
|
|||
description = "Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec."
|
||||
|
||||
prompt = """
|
||||
---
|
||||
description: Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
|
||||
handoffs:
|
||||
- label: Build Technical Plan
|
||||
agent: speckit.plan
|
||||
prompt: Create a plan for the spec. I am building with...
|
||||
---
|
||||
|
||||
## User Input
|
||||
|
||||
```text
|
||||
$ARGUMENTS
|
||||
```
|
||||
|
||||
You **MUST** consider the user input before proceeding (if not empty).
|
||||
|
||||
## Outline
|
||||
|
||||
Goal: Detect and reduce ambiguity or missing decision points in the active feature specification and record the clarifications directly in the spec file.
|
||||
|
||||
Note: This clarification workflow is expected to run (and be completed) BEFORE invoking `/speckit.plan`. If the user explicitly states they are skipping clarification (e.g., exploratory spike), you may proceed, but must warn that downstream rework risk increases.
|
||||
|
||||
Execution steps:
|
||||
|
||||
1. Run `.specify/scripts/bash/check-prerequisites.sh --json --paths-only` from repo root **once** (combined `--json --paths-only` mode / `-Json -PathsOnly`). Parse minimal JSON payload fields:
|
||||
- `FEATURE_DIR`
|
||||
- `FEATURE_SPEC`
|
||||
- (Optionally capture `IMPL_PLAN`, `TASKS` for future chained flows.)
|
||||
- If JSON parsing fails, abort and instruct user to re-run `/speckit.specify` or verify feature branch environment.
|
||||
- For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: "I'm Groot").
|
||||
|
||||
2. Load the current spec file. Perform a structured ambiguity & coverage scan using this taxonomy. For each category, mark status: Clear / Partial / Missing. Produce an internal coverage map used for prioritization (do not output raw map unless no questions will be asked).
|
||||
|
||||
Functional Scope & Behavior:
|
||||
- Core user goals & success criteria
|
||||
- Explicit out-of-scope declarations
|
||||
- User roles / personas differentiation
|
||||
|
||||
Domain & Data Model:
|
||||
- Entities, attributes, relationships
|
||||
- Identity & uniqueness rules
|
||||
- Lifecycle/state transitions
|
||||
- Data volume / scale assumptions
|
||||
|
||||
Interaction & UX Flow:
|
||||
- Critical user journeys / sequences
|
||||
- Error/empty/loading states
|
||||
- Accessibility or localization notes
|
||||
|
||||
Non-Functional Quality Attributes:
|
||||
- Performance (latency, throughput targets)
|
||||
- Scalability (horizontal/vertical, limits)
|
||||
- Reliability & availability (uptime, recovery expectations)
|
||||
- Observability (logging, metrics, tracing signals)
|
||||
- Security & privacy (authN/Z, data protection, threat assumptions)
|
||||
- Compliance / regulatory constraints (if any)
|
||||
|
||||
Integration & External Dependencies:
|
||||
- External services/APIs and failure modes
|
||||
- Data import/export formats
|
||||
- Protocol/versioning assumptions
|
||||
|
||||
Edge Cases & Failure Handling:
|
||||
- Negative scenarios
|
||||
- Rate limiting / throttling
|
||||
- Conflict resolution (e.g., concurrent edits)
|
||||
|
||||
Constraints & Tradeoffs:
|
||||
- Technical constraints (language, storage, hosting)
|
||||
- Explicit tradeoffs or rejected alternatives
|
||||
|
||||
Terminology & Consistency:
|
||||
- Canonical glossary terms
|
||||
- Avoided synonyms / deprecated terms
|
||||
|
||||
Completion Signals:
|
||||
- Acceptance criteria testability
|
||||
- Measurable Definition of Done style indicators
|
||||
|
||||
Misc / Placeholders:
|
||||
- TODO markers / unresolved decisions
|
||||
- Ambiguous adjectives ("robust", "intuitive") lacking quantification
|
||||
|
||||
For each category with Partial or Missing status, add a candidate question opportunity unless:
|
||||
- Clarification would not materially change implementation or validation strategy
|
||||
- Information is better deferred to planning phase (note internally)
|
||||
|
||||
3. Generate (internally) a prioritized queue of candidate clarification questions (maximum 5). Do NOT output them all at once. Apply these constraints:
|
||||
- Maximum of 10 total questions across the whole session.
|
||||
- Each question must be answerable with EITHER:
|
||||
- A short multiple‑choice selection (2–5 distinct, mutually exclusive options), OR
|
||||
- A one-word / short‑phrase answer (explicitly constrain: "Answer in <=5 words").
|
||||
- Only include questions whose answers materially impact architecture, data modeling, task decomposition, test design, UX behavior, operational readiness, or compliance validation.
|
||||
- Ensure category coverage balance: attempt to cover the highest impact unresolved categories first; avoid asking two low-impact questions when a single high-impact area (e.g., security posture) is unresolved.
|
||||
- Exclude questions already answered, trivial stylistic preferences, or plan-level execution details (unless blocking correctness).
|
||||
- Favor clarifications that reduce downstream rework risk or prevent misaligned acceptance tests.
|
||||
- If more than 5 categories remain unresolved, select the top 5 by (Impact * Uncertainty) heuristic.
|
||||
|
||||
4. Sequential questioning loop (interactive):
|
||||
- Present EXACTLY ONE question at a time.
|
||||
- For multiple‑choice questions:
|
||||
- **Analyze all options** and determine the **most suitable option** based on:
|
||||
- Best practices for the project type
|
||||
- Common patterns in similar implementations
|
||||
- Risk reduction (security, performance, maintainability)
|
||||
- Alignment with any explicit project goals or constraints visible in the spec
|
||||
- Present your **recommended option prominently** at the top with clear reasoning (1-2 sentences explaining why this is the best choice).
|
||||
- Format as: `**Recommended:** Option [X] - <reasoning>`
|
||||
- Then render all options as a Markdown table:
|
||||
|
||||
| Option | Description |
|
||||
|--------|-------------|
|
||||
| A | <Option A description> |
|
||||
| B | <Option B description> |
|
||||
| C | <Option C description> (add D/E as needed up to 5) |
|
||||
| Short | Provide a different short answer (<=5 words) (Include only if free-form alternative is appropriate) |
|
||||
|
||||
- After the table, add: `You can reply with the option letter (e.g., "A"), accept the recommendation by saying "yes" or "recommended", or provide your own short answer.`
|
||||
- For short‑answer style (no meaningful discrete options):
|
||||
- Provide your **suggested answer** based on best practices and context.
|
||||
- Format as: `**Suggested:** <your proposed answer> - <brief reasoning>`
|
||||
- Then output: `Format: Short answer (<=5 words). You can accept the suggestion by saying "yes" or "suggested", or provide your own answer.`
|
||||
- After the user answers:
|
||||
- If the user replies with "yes", "recommended", or "suggested", use your previously stated recommendation/suggestion as the answer.
|
||||
- Otherwise, validate the answer maps to one option or fits the <=5 word constraint.
|
||||
- If ambiguous, ask for a quick disambiguation (count still belongs to same question; do not advance).
|
||||
- Once satisfactory, record it in working memory (do not yet write to disk) and move to the next queued question.
|
||||
- Stop asking further questions when:
|
||||
- All critical ambiguities resolved early (remaining queued items become unnecessary), OR
|
||||
- User signals completion ("done", "good", "no more"), OR
|
||||
- You reach 5 asked questions.
|
||||
- Never reveal future queued questions in advance.
|
||||
- If no valid questions exist at start, immediately report no critical ambiguities.
|
||||
|
||||
5. Integration after EACH accepted answer (incremental update approach):
|
||||
- Maintain in-memory representation of the spec (loaded once at start) plus the raw file contents.
|
||||
- For the first integrated answer in this session:
|
||||
- Ensure a `## Clarifications` section exists (create it just after the highest-level contextual/overview section per the spec template if missing).
|
||||
- Under it, create (if not present) a `### Session YYYY-MM-DD` subheading for today.
|
||||
- Append a bullet line immediately after acceptance: `- Q: <question> → A: <final answer>`.
|
||||
- Then immediately apply the clarification to the most appropriate section(s):
|
||||
- Functional ambiguity → Update or add a bullet in Functional Requirements.
|
||||
- User interaction / actor distinction → Update User Stories or Actors subsection (if present) with clarified role, constraint, or scenario.
|
||||
- Data shape / entities → Update Data Model (add fields, types, relationships) preserving ordering; note added constraints succinctly.
|
||||
- Non-functional constraint → Add/modify measurable criteria in Non-Functional / Quality Attributes section (convert vague adjective to metric or explicit target).
|
||||
- Edge case / negative flow → Add a new bullet under Edge Cases / Error Handling (or create such subsection if template provides placeholder for it).
|
||||
- Terminology conflict → Normalize term across spec; retain original only if necessary by adding `(formerly referred to as "X")` once.
|
||||
- If the clarification invalidates an earlier ambiguous statement, replace that statement instead of duplicating; leave no obsolete contradictory text.
|
||||
- Save the spec file AFTER each integration to minimize risk of context loss (atomic overwrite).
|
||||
- Preserve formatting: do not reorder unrelated sections; keep heading hierarchy intact.
|
||||
- Keep each inserted clarification minimal and testable (avoid narrative drift).
|
||||
|
||||
6. Validation (performed after EACH write plus final pass):
|
||||
- Clarifications session contains exactly one bullet per accepted answer (no duplicates).
|
||||
- Total asked (accepted) questions ≤ 5.
|
||||
- Updated sections contain no lingering vague placeholders the new answer was meant to resolve.
|
||||
- No contradictory earlier statement remains (scan for now-invalid alternative choices removed).
|
||||
- Markdown structure valid; only allowed new headings: `## Clarifications`, `### Session YYYY-MM-DD`.
|
||||
- Terminology consistency: same canonical term used across all updated sections.
|
||||
|
||||
7. Write the updated spec back to `FEATURE_SPEC`.
|
||||
|
||||
8. Report completion (after questioning loop ends or early termination):
|
||||
- Number of questions asked & answered.
|
||||
- Path to updated spec.
|
||||
- Sections touched (list names).
|
||||
- Coverage summary table listing each taxonomy category with Status: Resolved (was Partial/Missing and addressed), Deferred (exceeds question quota or better suited for planning), Clear (already sufficient), Outstanding (still Partial/Missing but low impact).
|
||||
- If any Outstanding or Deferred remain, recommend whether to proceed to `/speckit.plan` or run `/speckit.clarify` again later post-plan.
|
||||
- Suggested next command.
|
||||
|
||||
Behavior rules:
|
||||
|
||||
- If no meaningful ambiguities found (or all potential questions would be low-impact), respond: "No critical ambiguities detected worth formal clarification." and suggest proceeding.
|
||||
- If spec file missing, instruct user to run `/speckit.specify` first (do not create a new spec here).
|
||||
- Never exceed 5 total asked questions (clarification retries for a single question do not count as new questions).
|
||||
- Avoid speculative tech stack questions unless the absence blocks functional clarity.
|
||||
- Respect user early termination signals ("stop", "done", "proceed").
|
||||
- If no questions asked due to full coverage, output a compact coverage summary (all categories Clear) then suggest advancing.
|
||||
- If quota reached with unresolved high-impact categories remaining, explicitly flag them under Deferred with rationale.
|
||||
|
||||
Context for prioritization: {{args}}
|
||||
"""
|
||||
|
|
@ -0,0 +1,86 @@
|
|||
description = "Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync."
|
||||
|
||||
prompt = """
|
||||
---
|
||||
description: Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.
|
||||
handoffs:
|
||||
- label: Build Specification
|
||||
agent: speckit.specify
|
||||
prompt: Implement the feature specification based on the updated constitution. I want to build...
|
||||
---
|
||||
|
||||
## User Input
|
||||
|
||||
```text
|
||||
$ARGUMENTS
|
||||
```
|
||||
|
||||
You **MUST** consider the user input before proceeding (if not empty).
|
||||
|
||||
## Outline
|
||||
|
||||
You are updating the project constitution at `.specify/memory/constitution.md`. This file is a TEMPLATE containing placeholder tokens in square brackets (e.g. `[PROJECT_NAME]`, `[PRINCIPLE_1_NAME]`). Your job is to (a) collect/derive concrete values, (b) fill the template precisely, and (c) propagate any amendments across dependent artifacts.
|
||||
|
||||
Follow this execution flow:
|
||||
|
||||
1. Load the existing constitution template at `.specify/memory/constitution.md`.
|
||||
- Identify every placeholder token of the form `[ALL_CAPS_IDENTIFIER]`.
|
||||
**IMPORTANT**: The user might require less or more principles than the ones used in the template. If a number is specified, respect that - follow the general template. You will update the doc accordingly.
|
||||
|
||||
2. Collect/derive values for placeholders:
|
||||
- If user input (conversation) supplies a value, use it.
|
||||
- Otherwise infer from existing repo context (README, docs, prior constitution versions if embedded).
|
||||
- For governance dates: `RATIFICATION_DATE` is the original adoption date (if unknown ask or mark TODO), `LAST_AMENDED_DATE` is today if changes are made, otherwise keep previous.
|
||||
- `CONSTITUTION_VERSION` must increment according to semantic versioning rules:
|
||||
- MAJOR: Backward incompatible governance/principle removals or redefinitions.
|
||||
- MINOR: New principle/section added or materially expanded guidance.
|
||||
- PATCH: Clarifications, wording, typo fixes, non-semantic refinements.
|
||||
- If version bump type ambiguous, propose reasoning before finalizing.
|
||||
|
||||
3. Draft the updated constitution content:
|
||||
- Replace every placeholder with concrete text (no bracketed tokens left except intentionally retained template slots that the project has chosen not to define yet—explicitly justify any left).
|
||||
- Preserve heading hierarchy and comments can be removed once replaced unless they still add clarifying guidance.
|
||||
- Ensure each Principle section: succinct name line, paragraph (or bullet list) capturing non‑negotiable rules, explicit rationale if not obvious.
|
||||
- Ensure Governance section lists amendment procedure, versioning policy, and compliance review expectations.
|
||||
|
||||
4. Consistency propagation checklist (convert prior checklist into active validations):
|
||||
- Read `.specify/templates/plan-template.md` and ensure any "Constitution Check" or rules align with updated principles.
|
||||
- Read `.specify/templates/spec-template.md` for scope/requirements alignment—update if constitution adds/removes mandatory sections or constraints.
|
||||
- Read `.specify/templates/tasks-template.md` and ensure task categorization reflects new or removed principle-driven task types (e.g., observability, versioning, testing discipline).
|
||||
- Read each command file in `.specify/templates/commands/*.md` (including this one) to verify no outdated references (agent-specific names like CLAUDE only) remain when generic guidance is required.
|
||||
- Read any runtime guidance docs (e.g., `README.md`, `docs/quickstart.md`, or agent-specific guidance files if present). Update references to principles changed.
|
||||
|
||||
5. Produce a Sync Impact Report (prepend as an HTML comment at top of the constitution file after update):
|
||||
- Version change: old → new
|
||||
- List of modified principles (old title → new title if renamed)
|
||||
- Added sections
|
||||
- Removed sections
|
||||
- Templates requiring updates (✅ updated / ⚠ pending) with file paths
|
||||
- Follow-up TODOs if any placeholders intentionally deferred.
|
||||
|
||||
6. Validation before final output:
|
||||
- No remaining unexplained bracket tokens.
|
||||
- Version line matches report.
|
||||
- Dates ISO format YYYY-MM-DD.
|
||||
- Principles are declarative, testable, and free of vague language ("should" → replace with MUST/SHOULD rationale where appropriate).
|
||||
|
||||
7. Write the completed constitution back to `.specify/memory/constitution.md` (overwrite).
|
||||
|
||||
8. Output a final summary to the user with:
|
||||
- New version and bump rationale.
|
||||
- Any files flagged for manual follow-up.
|
||||
- Suggested commit message (e.g., `docs: amend constitution to vX.Y.Z (principle additions + governance update)`).
|
||||
|
||||
Formatting & Style Requirements:
|
||||
|
||||
- Use Markdown headings exactly as in the template (do not demote/promote levels).
|
||||
- Wrap long rationale lines to keep readability (<100 chars ideally) but do not hard enforce with awkward breaks.
|
||||
- Keep a single blank line between sections.
|
||||
- Avoid trailing whitespace.
|
||||
|
||||
If the user supplies partial updates (e.g., only one principle revision), still perform validation and version decision steps.
|
||||
|
||||
If critical info missing (e.g., ratification date truly unknown), insert `TODO(<FIELD_NAME>): explanation` and include in the Sync Impact Report under deferred items.
|
||||
|
||||
Do not create a new template; always operate on the existing `.specify/memory/constitution.md` file.
|
||||
"""
|
||||
|
|
@ -0,0 +1,139 @@
|
|||
description = "Execute the implementation plan by processing and executing all tasks defined in tasks.md"
|
||||
|
||||
prompt = """
|
||||
---
|
||||
description: Execute the implementation plan by processing and executing all tasks defined in tasks.md
|
||||
---
|
||||
|
||||
## User Input
|
||||
|
||||
```text
|
||||
$ARGUMENTS
|
||||
```
|
||||
|
||||
You **MUST** consider the user input before proceeding (if not empty).
|
||||
|
||||
## Outline
|
||||
|
||||
1. Run `.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: "I'm Groot").
|
||||
|
||||
2. **Check checklists status** (if FEATURE_DIR/checklists/ exists):
|
||||
- Scan all checklist files in the checklists/ directory
|
||||
- For each checklist, count:
|
||||
- Total items: All lines matching `- [ ]` or `- [X]` or `- [x]`
|
||||
- Completed items: Lines matching `- [X]` or `- [x]`
|
||||
- Incomplete items: Lines matching `- [ ]`
|
||||
- Create a status table:
|
||||
|
||||
```text
|
||||
| Checklist | Total | Completed | Incomplete | Status |
|
||||
|-----------|-------|-----------|------------|--------|
|
||||
| ux.md | 12 | 12 | 0 | ✓ PASS |
|
||||
| test.md | 8 | 5 | 3 | ✗ FAIL |
|
||||
| security.md | 6 | 6 | 0 | ✓ PASS |
|
||||
```
|
||||
|
||||
- Calculate overall status:
|
||||
- **PASS**: All checklists have 0 incomplete items
|
||||
- **FAIL**: One or more checklists have incomplete items
|
||||
|
||||
- **If any checklist is incomplete**:
|
||||
- Display the table with incomplete item counts
|
||||
- **STOP** and ask: "Some checklists are incomplete. Do you want to proceed with implementation anyway? (yes/no)"
|
||||
- Wait for user response before continuing
|
||||
- If user says "no" or "wait" or "stop", halt execution
|
||||
- If user says "yes" or "proceed" or "continue", proceed to step 3
|
||||
|
||||
- **If all checklists are complete**:
|
||||
- Display the table showing all checklists passed
|
||||
- Automatically proceed to step 3
|
||||
|
||||
3. Load and analyze the implementation context:
|
||||
- **REQUIRED**: Read tasks.md for the complete task list and execution plan
|
||||
- **REQUIRED**: Read plan.md for tech stack, architecture, and file structure
|
||||
- **IF EXISTS**: Read data-model.md for entities and relationships
|
||||
- **IF EXISTS**: Read contracts/ for API specifications and test requirements
|
||||
- **IF EXISTS**: Read research.md for technical decisions and constraints
|
||||
- **IF EXISTS**: Read quickstart.md for integration scenarios
|
||||
|
||||
4. **Project Setup Verification**:
|
||||
- **REQUIRED**: Create/verify ignore files based on actual project setup:
|
||||
|
||||
**Detection & Creation Logic**:
|
||||
- Check if the following command succeeds to determine if the repository is a git repo (create/verify .gitignore if so):
|
||||
|
||||
```sh
|
||||
git rev-parse --git-dir 2>/dev/null
|
||||
```
|
||||
|
||||
- Check if Dockerfile* exists or Docker in plan.md → create/verify .dockerignore
|
||||
- Check if .eslintrc* exists → create/verify .eslintignore
|
||||
- Check if eslint.config.* exists → ensure the config's `ignores` entries cover required patterns
|
||||
- Check if .prettierrc* exists → create/verify .prettierignore
|
||||
- Check if .npmrc or package.json exists → create/verify .npmignore (if publishing)
|
||||
- Check if terraform files (*.tf) exist → create/verify .terraformignore
|
||||
- Check if .helmignore needed (helm charts present) → create/verify .helmignore
|
||||
|
||||
**If ignore file already exists**: Verify it contains essential patterns, append missing critical patterns only
|
||||
**If ignore file missing**: Create with full pattern set for detected technology
|
||||
|
||||
**Common Patterns by Technology** (from plan.md tech stack):
|
||||
- **Node.js/JavaScript/TypeScript**: `node_modules/`, `dist/`, `build/`, `*.log`, `.env*`
|
||||
- **Python**: `__pycache__/`, `*.pyc`, `.venv/`, `venv/`, `dist/`, `*.egg-info/`
|
||||
- **Java**: `target/`, `*.class`, `*.jar`, `.gradle/`, `build/`
|
||||
- **C#/.NET**: `bin/`, `obj/`, `*.user`, `*.suo`, `packages/`
|
||||
- **Go**: `*.exe`, `*.test`, `vendor/`, `*.out`
|
||||
- **Ruby**: `.bundle/`, `log/`, `tmp/`, `*.gem`, `vendor/bundle/`
|
||||
- **PHP**: `vendor/`, `*.log`, `*.cache`, `*.env`
|
||||
- **Rust**: `target/`, `debug/`, `release/`, `*.rs.bk`, `*.rlib`, `*.prof*`, `.idea/`, `*.log`, `.env*`
|
||||
- **Kotlin**: `build/`, `out/`, `.gradle/`, `.idea/`, `*.class`, `*.jar`, `*.iml`, `*.log`, `.env*`
|
||||
- **C++**: `build/`, `bin/`, `obj/`, `out/`, `*.o`, `*.so`, `*.a`, `*.exe`, `*.dll`, `.idea/`, `*.log`, `.env*`
|
||||
- **C**: `build/`, `bin/`, `obj/`, `out/`, `*.o`, `*.a`, `*.so`, `*.exe`, `Makefile`, `config.log`, `.idea/`, `*.log`, `.env*`
|
||||
- **Swift**: `.build/`, `DerivedData/`, `*.swiftpm/`, `Packages/`
|
||||
- **R**: `.Rproj.user/`, `.Rhistory`, `.RData`, `.Ruserdata`, `*.Rproj`, `packrat/`, `renv/`
|
||||
- **Universal**: `.DS_Store`, `Thumbs.db`, `*.tmp`, `*.swp`, `.vscode/`, `.idea/`
|
||||
|
||||
**Tool-Specific Patterns**:
|
||||
- **Docker**: `node_modules/`, `.git/`, `Dockerfile*`, `.dockerignore`, `*.log*`, `.env*`, `coverage/`
|
||||
- **ESLint**: `node_modules/`, `dist/`, `build/`, `coverage/`, `*.min.js`
|
||||
- **Prettier**: `node_modules/`, `dist/`, `build/`, `coverage/`, `package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`
|
||||
- **Terraform**: `.terraform/`, `*.tfstate*`, `*.tfvars`, `.terraform.lock.hcl`
|
||||
- **Kubernetes/k8s**: `*.secret.yaml`, `secrets/`, `.kube/`, `kubeconfig*`, `*.key`, `*.crt`
|
||||
|
||||
5. Parse tasks.md structure and extract:
|
||||
- **Task phases**: Setup, Tests, Core, Integration, Polish
|
||||
- **Task dependencies**: Sequential vs parallel execution rules
|
||||
- **Task details**: ID, description, file paths, parallel markers [P]
|
||||
- **Execution flow**: Order and dependency requirements
|
||||
|
||||
6. Execute implementation following the task plan:
|
||||
- **Phase-by-phase execution**: Complete each phase before moving to the next
|
||||
- **Respect dependencies**: Run sequential tasks in order, parallel tasks [P] can run together
|
||||
- **Follow TDD approach**: Execute test tasks before their corresponding implementation tasks
|
||||
- **File-based coordination**: Tasks affecting the same files must run sequentially
|
||||
- **Validation checkpoints**: Verify each phase completion before proceeding
|
||||
|
||||
7. Implementation execution rules:
|
||||
- **Setup first**: Initialize project structure, dependencies, configuration
|
||||
- **Tests before code**: If you need to write tests for contracts, entities, and integration scenarios
|
||||
- **Core development**: Implement models, services, CLI commands, endpoints
|
||||
- **Integration work**: Database connections, middleware, logging, external services
|
||||
- **Polish and validation**: Unit tests, performance optimization, documentation
|
||||
|
||||
8. Progress tracking and error handling:
|
||||
- Report progress after each completed task
|
||||
- Halt execution if any non-parallel task fails
|
||||
- For parallel tasks [P], continue with successful tasks, report failed ones
|
||||
- Provide clear error messages with context for debugging
|
||||
- Suggest next steps if implementation cannot proceed
|
||||
- **IMPORTANT** For completed tasks, make sure to mark the task off as [X] in the tasks file.
|
||||
|
||||
9. Completion validation:
|
||||
- Verify all required tasks are completed
|
||||
- Check that implemented features match the original specification
|
||||
- Validate that tests pass and coverage meets requirements
|
||||
- Confirm the implementation follows the technical plan
|
||||
- Report final status with summary of completed work
|
||||
|
||||
Note: This command assumes a complete task breakdown exists in tasks.md. If tasks are incomplete or missing, suggest running `/speckit.tasks` first to regenerate the task list.
|
||||
"""
|
||||
|
|
@ -0,0 +1,93 @@
|
|||
description = "Execute the implementation planning workflow using the plan template to generate design artifacts."
|
||||
|
||||
prompt = """
|
||||
---
|
||||
description: Execute the implementation planning workflow using the plan template to generate design artifacts.
|
||||
handoffs:
|
||||
- label: Create Tasks
|
||||
agent: speckit.tasks
|
||||
prompt: Break the plan into tasks
|
||||
send: true
|
||||
- label: Create Checklist
|
||||
agent: speckit.checklist
|
||||
prompt: Create a checklist for the following domain...
|
||||
---
|
||||
|
||||
## User Input
|
||||
|
||||
```text
|
||||
$ARGUMENTS
|
||||
```
|
||||
|
||||
You **MUST** consider the user input before proceeding (if not empty).
|
||||
|
||||
## Outline
|
||||
|
||||
1. **Setup**: Run `.specify/scripts/bash/setup-plan.sh --json` from repo root and parse JSON for FEATURE_SPEC, IMPL_PLAN, SPECS_DIR, BRANCH. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: "I'm Groot").
|
||||
|
||||
2. **Load context**: Read FEATURE_SPEC and `.specify/memory/constitution.md`. Load IMPL_PLAN template (already copied).
|
||||
|
||||
3. **Execute plan workflow**: Follow the structure in IMPL_PLAN template to:
|
||||
- Fill Technical Context (mark unknowns as "NEEDS CLARIFICATION")
|
||||
- Fill Constitution Check section from constitution
|
||||
- Evaluate gates (ERROR if violations unjustified)
|
||||
- Phase 0: Generate research.md (resolve all NEEDS CLARIFICATION)
|
||||
- Phase 1: Generate data-model.md, contracts/, quickstart.md
|
||||
- Phase 1: Update agent context by running the agent script
|
||||
- Re-evaluate Constitution Check post-design
|
||||
|
||||
4. **Stop and report**: Command ends after Phase 2 planning. Report branch, IMPL_PLAN path, and generated artifacts.
|
||||
|
||||
## Phases
|
||||
|
||||
### Phase 0: Outline & Research
|
||||
|
||||
1. **Extract unknowns from Technical Context** above:
|
||||
- For each NEEDS CLARIFICATION → research task
|
||||
- For each dependency → best practices task
|
||||
- For each integration → patterns task
|
||||
|
||||
2. **Generate and dispatch research agents**:
|
||||
|
||||
```text
|
||||
For each unknown in Technical Context:
|
||||
Task: "Research {unknown} for {feature context}"
|
||||
For each technology choice:
|
||||
Task: "Find best practices for {tech} in {domain}"
|
||||
```
|
||||
|
||||
3. **Consolidate findings** in `research.md` using format:
|
||||
- Decision: [what was chosen]
|
||||
- Rationale: [why chosen]
|
||||
- Alternatives considered: [what else evaluated]
|
||||
|
||||
**Output**: research.md with all NEEDS CLARIFICATION resolved
|
||||
|
||||
### Phase 1: Design & Contracts
|
||||
|
||||
**Prerequisites:** `research.md` complete
|
||||
|
||||
1. **Extract entities from feature spec** → `data-model.md`:
|
||||
- Entity name, fields, relationships
|
||||
- Validation rules from requirements
|
||||
- State transitions if applicable
|
||||
|
||||
2. **Generate API contracts** from functional requirements:
|
||||
- For each user action → endpoint
|
||||
- Use standard REST/GraphQL patterns
|
||||
- Output OpenAPI/GraphQL schema to `/contracts/`
|
||||
|
||||
3. **Agent context update**:
|
||||
- Run `.specify/scripts/bash/update-agent-context.sh gemini`
|
||||
- These scripts detect which AI agent is in use
|
||||
- Update the appropriate agent-specific context file
|
||||
- Add only new technology from current plan
|
||||
- Preserve manual additions between markers
|
||||
|
||||
**Output**: data-model.md, /contracts/*, quickstart.md, agent-specific file
|
||||
|
||||
## Key rules
|
||||
|
||||
- Use absolute paths
|
||||
- ERROR on gate failures or unresolved clarifications
|
||||
"""
|
||||
|
|
@ -0,0 +1,261 @@
|
|||
description = "Create or update the feature specification from a natural language feature description."
|
||||
|
||||
prompt = """
|
||||
---
|
||||
description: Create or update the feature specification from a natural language feature description.
|
||||
handoffs:
|
||||
- label: Build Technical Plan
|
||||
agent: speckit.plan
|
||||
prompt: Create a plan for the spec. I am building with...
|
||||
- label: Clarify Spec Requirements
|
||||
agent: speckit.clarify
|
||||
prompt: Clarify specification requirements
|
||||
send: true
|
||||
---
|
||||
|
||||
## User Input
|
||||
|
||||
```text
|
||||
$ARGUMENTS
|
||||
```
|
||||
|
||||
You **MUST** consider the user input before proceeding (if not empty).
|
||||
|
||||
## Outline
|
||||
|
||||
The text the user typed after `/speckit.specify` in the triggering message **is** the feature description. Assume you always have it available in this conversation even if `{{args}}` appears literally below. Do not ask the user to repeat it unless they provided an empty command.
|
||||
|
||||
Given that feature description, do this:
|
||||
|
||||
1. **Generate a concise short name** (2-4 words) for the branch:
|
||||
- Analyze the feature description and extract the most meaningful keywords
|
||||
- Create a 2-4 word short name that captures the essence of the feature
|
||||
- Use action-noun format when possible (e.g., "add-user-auth", "fix-payment-bug")
|
||||
- Preserve technical terms and acronyms (OAuth2, API, JWT, etc.)
|
||||
- Keep it concise but descriptive enough to understand the feature at a glance
|
||||
- Examples:
|
||||
- "I want to add user authentication" → "user-auth"
|
||||
- "Implement OAuth2 integration for the API" → "oauth2-api-integration"
|
||||
- "Create a dashboard for analytics" → "analytics-dashboard"
|
||||
- "Fix payment processing timeout bug" → "fix-payment-timeout"
|
||||
|
||||
2. **Check for existing branches before creating new one**:
|
||||
|
||||
a. First, fetch all remote branches to ensure we have the latest information:
|
||||
```bash
|
||||
git fetch --all --prune
|
||||
```
|
||||
|
||||
b. Find the highest feature number across all sources for the short-name:
|
||||
- Remote branches: `git ls-remote --heads origin | grep -E 'refs/heads/[0-9]+-<short-name>$'`
|
||||
- Local branches: `git branch | grep -E '^[* ]*[0-9]+-<short-name>$'`
|
||||
- Specs directories: Check for directories matching `specs/[0-9]+-<short-name>`
|
||||
|
||||
c. Determine the next available number:
|
||||
- Extract all numbers from all three sources
|
||||
- Find the highest number N
|
||||
- Use N+1 for the new branch number
|
||||
|
||||
d. Run the script `.specify/scripts/bash/create-new-feature.sh --json "{{args}}"` with the calculated number and short-name:
|
||||
- Pass `--number N+1` and `--short-name "your-short-name"` along with the feature description
|
||||
- Bash example: `.specify/scripts/bash/create-new-feature.sh --json "{{args}}" --json --number 5 --short-name "user-auth" "Add user authentication"`
|
||||
- PowerShell example: `.specify/scripts/bash/create-new-feature.sh --json "{{args}}" -Json -Number 5 -ShortName "user-auth" "Add user authentication"`
|
||||
|
||||
**IMPORTANT**:
|
||||
- Check all three sources (remote branches, local branches, specs directories) to find the highest number
|
||||
- Only match branches/directories with the exact short-name pattern
|
||||
- If no existing branches/directories found with this short-name, start with number 1
|
||||
- You must only ever run this script once per feature
|
||||
- The JSON is provided in the terminal as output - always refer to it to get the actual content you're looking for
|
||||
- The JSON output will contain BRANCH_NAME and SPEC_FILE paths
|
||||
- For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: "I'm Groot")
|
||||
|
||||
3. Load `.specify/templates/spec-template.md` to understand required sections.
|
||||
|
||||
4. Follow this execution flow:
|
||||
|
||||
1. Parse user description from Input
|
||||
If empty: ERROR "No feature description provided"
|
||||
2. Extract key concepts from description
|
||||
Identify: actors, actions, data, constraints
|
||||
3. For unclear aspects:
|
||||
- Make informed guesses based on context and industry standards
|
||||
- Only mark with [NEEDS CLARIFICATION: specific question] if:
|
||||
- The choice significantly impacts feature scope or user experience
|
||||
- Multiple reasonable interpretations exist with different implications
|
||||
- No reasonable default exists
|
||||
- **LIMIT: Maximum 3 [NEEDS CLARIFICATION] markers total**
|
||||
- Prioritize clarifications by impact: scope > security/privacy > user experience > technical details
|
||||
4. Fill User Scenarios & Testing section
|
||||
If no clear user flow: ERROR "Cannot determine user scenarios"
|
||||
5. Generate Functional Requirements
|
||||
Each requirement must be testable
|
||||
Use reasonable defaults for unspecified details (document assumptions in Assumptions section)
|
||||
6. Define Success Criteria
|
||||
Create measurable, technology-agnostic outcomes
|
||||
Include both quantitative metrics (time, performance, volume) and qualitative measures (user satisfaction, task completion)
|
||||
Each criterion must be verifiable without implementation details
|
||||
7. Identify Key Entities (if data involved)
|
||||
8. Return: SUCCESS (spec ready for planning)
|
||||
|
||||
5. Write the specification to SPEC_FILE using the template structure, replacing placeholders with concrete details derived from the feature description (arguments) while preserving section order and headings.
|
||||
|
||||
6. **Specification Quality Validation**: After writing the initial spec, validate it against quality criteria:
|
||||
|
||||
a. **Create Spec Quality Checklist**: Generate a checklist file at `FEATURE_DIR/checklists/requirements.md` using the checklist template structure with these validation items:
|
||||
|
||||
```markdown
|
||||
# Specification Quality Checklist: [FEATURE NAME]
|
||||
|
||||
**Purpose**: Validate specification completeness and quality before proceeding to planning
|
||||
**Created**: [DATE]
|
||||
**Feature**: [Link to spec.md]
|
||||
|
||||
## Content Quality
|
||||
|
||||
- [ ] No implementation details (languages, frameworks, APIs)
|
||||
- [ ] Focused on user value and business needs
|
||||
- [ ] Written for non-technical stakeholders
|
||||
- [ ] All mandatory sections completed
|
||||
|
||||
## Requirement Completeness
|
||||
|
||||
- [ ] No [NEEDS CLARIFICATION] markers remain
|
||||
- [ ] Requirements are testable and unambiguous
|
||||
- [ ] Success criteria are measurable
|
||||
- [ ] Success criteria are technology-agnostic (no implementation details)
|
||||
- [ ] All acceptance scenarios are defined
|
||||
- [ ] Edge cases are identified
|
||||
- [ ] Scope is clearly bounded
|
||||
- [ ] Dependencies and assumptions identified
|
||||
|
||||
## Feature Readiness
|
||||
|
||||
- [ ] All functional requirements have clear acceptance criteria
|
||||
- [ ] User scenarios cover primary flows
|
||||
- [ ] Feature meets measurable outcomes defined in Success Criteria
|
||||
- [ ] No implementation details leak into specification
|
||||
|
||||
## Notes
|
||||
|
||||
- Items marked incomplete require spec updates before `/speckit.clarify` or `/speckit.plan`
|
||||
```
|
||||
|
||||
b. **Run Validation Check**: Review the spec against each checklist item:
|
||||
- For each item, determine if it passes or fails
|
||||
- Document specific issues found (quote relevant spec sections)
|
||||
|
||||
c. **Handle Validation Results**:
|
||||
|
||||
- **If all items pass**: Mark checklist complete and proceed to step 6
|
||||
|
||||
- **If items fail (excluding [NEEDS CLARIFICATION])**:
|
||||
1. List the failing items and specific issues
|
||||
2. Update the spec to address each issue
|
||||
3. Re-run validation until all items pass (max 3 iterations)
|
||||
4. If still failing after 3 iterations, document remaining issues in checklist notes and warn user
|
||||
|
||||
- **If [NEEDS CLARIFICATION] markers remain**:
|
||||
1. Extract all [NEEDS CLARIFICATION: ...] markers from the spec
|
||||
2. **LIMIT CHECK**: If more than 3 markers exist, keep only the 3 most critical (by scope/security/UX impact) and make informed guesses for the rest
|
||||
3. For each clarification needed (max 3), present options to user in this format:
|
||||
|
||||
```markdown
|
||||
## Question [N]: [Topic]
|
||||
|
||||
**Context**: [Quote relevant spec section]
|
||||
|
||||
**What we need to know**: [Specific question from NEEDS CLARIFICATION marker]
|
||||
|
||||
**Suggested Answers**:
|
||||
|
||||
| Option | Answer | Implications |
|
||||
|--------|--------|--------------|
|
||||
| A | [First suggested answer] | [What this means for the feature] |
|
||||
| B | [Second suggested answer] | [What this means for the feature] |
|
||||
| C | [Third suggested answer] | [What this means for the feature] |
|
||||
| Custom | Provide your own answer | [Explain how to provide custom input] |
|
||||
|
||||
**Your choice**: _[Wait for user response]_
|
||||
```
|
||||
|
||||
4. **CRITICAL - Table Formatting**: Ensure markdown tables are properly formatted:
|
||||
- Use consistent spacing with pipes aligned
|
||||
- Each cell should have spaces around content: `| Content |` not `|Content|`
|
||||
- Header separator must have at least 3 dashes: `|--------|`
|
||||
- Test that the table renders correctly in markdown preview
|
||||
5. Number questions sequentially (Q1, Q2, Q3 - max 3 total)
|
||||
6. Present all questions together before waiting for responses
|
||||
7. Wait for user to respond with their choices for all questions (e.g., "Q1: A, Q2: Custom - [details], Q3: B")
|
||||
8. Update the spec by replacing each [NEEDS CLARIFICATION] marker with the user's selected or provided answer
|
||||
9. Re-run validation after all clarifications are resolved
|
||||
|
||||
d. **Update Checklist**: After each validation iteration, update the checklist file with current pass/fail status
|
||||
|
||||
7. Report completion with branch name, spec file path, checklist results, and readiness for the next phase (`/speckit.clarify` or `/speckit.plan`).
|
||||
|
||||
**NOTE:** The script creates and checks out the new branch and initializes the spec file before writing.
|
||||
|
||||
## General Guidelines
|
||||
|
||||
## Quick Guidelines
|
||||
|
||||
- Focus on **WHAT** users need and **WHY**.
|
||||
- Avoid HOW to implement (no tech stack, APIs, code structure).
|
||||
- Written for business stakeholders, not developers.
|
||||
- DO NOT create any checklists that are embedded in the spec. That will be a separate command.
|
||||
|
||||
### Section Requirements
|
||||
|
||||
- **Mandatory sections**: Must be completed for every feature
|
||||
- **Optional sections**: Include only when relevant to the feature
|
||||
- When a section doesn't apply, remove it entirely (don't leave as "N/A")
|
||||
|
||||
### For AI Generation
|
||||
|
||||
When creating this spec from a user prompt:
|
||||
|
||||
1. **Make informed guesses**: Use context, industry standards, and common patterns to fill gaps
|
||||
2. **Document assumptions**: Record reasonable defaults in the Assumptions section
|
||||
3. **Limit clarifications**: Maximum 3 [NEEDS CLARIFICATION] markers - use only for critical decisions that:
|
||||
- Significantly impact feature scope or user experience
|
||||
- Have multiple reasonable interpretations with different implications
|
||||
- Lack any reasonable default
|
||||
4. **Prioritize clarifications**: scope > security/privacy > user experience > technical details
|
||||
5. **Think like a tester**: Every vague requirement should fail the "testable and unambiguous" checklist item
|
||||
6. **Common areas needing clarification** (only if no reasonable default exists):
|
||||
- Feature scope and boundaries (include/exclude specific use cases)
|
||||
- User types and permissions (if multiple conflicting interpretations possible)
|
||||
- Security/compliance requirements (when legally/financially significant)
|
||||
|
||||
**Examples of reasonable defaults** (don't ask about these):
|
||||
|
||||
- Data retention: Industry-standard practices for the domain
|
||||
- Performance targets: Standard web/mobile app expectations unless specified
|
||||
- Error handling: User-friendly messages with appropriate fallbacks
|
||||
- Authentication method: Standard session-based or OAuth2 for web apps
|
||||
- Integration patterns: RESTful APIs unless specified otherwise
|
||||
|
||||
### Success Criteria Guidelines
|
||||
|
||||
Success criteria must be:
|
||||
|
||||
1. **Measurable**: Include specific metrics (time, percentage, count, rate)
|
||||
2. **Technology-agnostic**: No mention of frameworks, languages, databases, or tools
|
||||
3. **User-focused**: Describe outcomes from user/business perspective, not system internals
|
||||
4. **Verifiable**: Can be tested/validated without knowing implementation details
|
||||
|
||||
**Good examples**:
|
||||
|
||||
- "Users can complete checkout in under 3 minutes"
|
||||
- "System supports 10,000 concurrent users"
|
||||
- "95% of searches return results in under 1 second"
|
||||
- "Task completion rate improves by 40%"
|
||||
|
||||
**Bad examples** (implementation-focused):
|
||||
|
||||
- "API response time is under 200ms" (too technical, use "Users see results instantly")
|
||||
- "Database can handle 1000 TPS" (implementation detail, use user-facing metric)
|
||||
- "React components render efficiently" (framework-specific)
|
||||
- "Redis cache hit rate above 80%" (technology-specific)
|
||||
"""
|
||||
|
|
@ -0,0 +1,141 @@
|
|||
description = "Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts."
|
||||
|
||||
prompt = """
|
||||
---
|
||||
description: Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
|
||||
handoffs:
|
||||
- label: Analyze For Consistency
|
||||
agent: speckit.analyze
|
||||
prompt: Run a project analysis for consistency
|
||||
send: true
|
||||
- label: Implement Project
|
||||
agent: speckit.implement
|
||||
prompt: Start the implementation in phases
|
||||
send: true
|
||||
---
|
||||
|
||||
## User Input
|
||||
|
||||
```text
|
||||
$ARGUMENTS
|
||||
```
|
||||
|
||||
You **MUST** consider the user input before proceeding (if not empty).
|
||||
|
||||
## Outline
|
||||
|
||||
1. **Setup**: Run `.specify/scripts/bash/check-prerequisites.sh --json` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: "I'm Groot").
|
||||
|
||||
2. **Load design documents**: Read from FEATURE_DIR:
|
||||
- **Required**: plan.md (tech stack, libraries, structure), spec.md (user stories with priorities)
|
||||
- **Optional**: data-model.md (entities), contracts/ (API endpoints), research.md (decisions), quickstart.md (test scenarios)
|
||||
- Note: Not all projects have all documents. Generate tasks based on what's available.
|
||||
|
||||
3. **Execute task generation workflow**:
|
||||
- Load plan.md and extract tech stack, libraries, project structure
|
||||
- Load spec.md and extract user stories with their priorities (P1, P2, P3, etc.)
|
||||
- If data-model.md exists: Extract entities and map to user stories
|
||||
- If contracts/ exists: Map endpoints to user stories
|
||||
- If research.md exists: Extract decisions for setup tasks
|
||||
- Generate tasks organized by user story (see Task Generation Rules below)
|
||||
- Generate dependency graph showing user story completion order
|
||||
- Create parallel execution examples per user story
|
||||
- Validate task completeness (each user story has all needed tasks, independently testable)
|
||||
|
||||
4. **Generate tasks.md**: Use `.specify.specify/templates/tasks-template.md` as structure, fill with:
|
||||
- Correct feature name from plan.md
|
||||
- Phase 1: Setup tasks (project initialization)
|
||||
- Phase 2: Foundational tasks (blocking prerequisites for all user stories)
|
||||
- Phase 3+: One phase per user story (in priority order from spec.md)
|
||||
- Each phase includes: story goal, independent test criteria, tests (if requested), implementation tasks
|
||||
- Final Phase: Polish & cross-cutting concerns
|
||||
- All tasks must follow the strict checklist format (see Task Generation Rules below)
|
||||
- Clear file paths for each task
|
||||
- Dependencies section showing story completion order
|
||||
- Parallel execution examples per story
|
||||
- Implementation strategy section (MVP first, incremental delivery)
|
||||
|
||||
5. **Report**: Output path to generated tasks.md and summary:
|
||||
- Total task count
|
||||
- Task count per user story
|
||||
- Parallel opportunities identified
|
||||
- Independent test criteria for each story
|
||||
- Suggested MVP scope (typically just User Story 1)
|
||||
- Format validation: Confirm ALL tasks follow the checklist format (checkbox, ID, labels, file paths)
|
||||
|
||||
Context for task generation: {{args}}
|
||||
|
||||
The tasks.md should be immediately executable - each task must be specific enough that an LLM can complete it without additional context.
|
||||
|
||||
## Task Generation Rules
|
||||
|
||||
**CRITICAL**: Tasks MUST be organized by user story to enable independent implementation and testing.
|
||||
|
||||
**Tests are OPTIONAL**: Only generate test tasks if explicitly requested in the feature specification or if user requests TDD approach.
|
||||
|
||||
### Checklist Format (REQUIRED)
|
||||
|
||||
Every task MUST strictly follow this format:
|
||||
|
||||
```text
|
||||
- [ ] [TaskID] [P?] [Story?] Description with file path
|
||||
```
|
||||
|
||||
**Format Components**:
|
||||
|
||||
1. **Checkbox**: ALWAYS start with `- [ ]` (markdown checkbox)
|
||||
2. **Task ID**: Sequential number (T001, T002, T003...) in execution order
|
||||
3. **[P] marker**: Include ONLY if task is parallelizable (different files, no dependencies on incomplete tasks)
|
||||
4. **[Story] label**: REQUIRED for user story phase tasks only
|
||||
- Format: [US1], [US2], [US3], etc. (maps to user stories from spec.md)
|
||||
- Setup phase: NO story label
|
||||
- Foundational phase: NO story label
|
||||
- User Story phases: MUST have story label
|
||||
- Polish phase: NO story label
|
||||
5. **Description**: Clear action with exact file path
|
||||
|
||||
**Examples**:
|
||||
|
||||
- ✅ CORRECT: `- [ ] T001 Create project structure per implementation plan`
|
||||
- ✅ CORRECT: `- [ ] T005 [P] Implement authentication middleware in src/middleware/auth.py`
|
||||
- ✅ CORRECT: `- [ ] T012 [P] [US1] Create User model in src/models/user.py`
|
||||
- ✅ CORRECT: `- [ ] T014 [US1] Implement UserService in src/services/user_service.py`
|
||||
- ❌ WRONG: `- [ ] Create User model` (missing ID and Story label)
|
||||
- ❌ WRONG: `T001 [US1] Create model` (missing checkbox)
|
||||
- ❌ WRONG: `- [ ] [US1] Create User model` (missing Task ID)
|
||||
- ❌ WRONG: `- [ ] T001 [US1] Create model` (missing file path)
|
||||
|
||||
### Task Organization
|
||||
|
||||
1. **From User Stories (spec.md)** - PRIMARY ORGANIZATION:
|
||||
- Each user story (P1, P2, P3...) gets its own phase
|
||||
- Map all related components to their story:
|
||||
- Models needed for that story
|
||||
- Services needed for that story
|
||||
- Endpoints/UI needed for that story
|
||||
- If tests requested: Tests specific to that story
|
||||
- Mark story dependencies (most stories should be independent)
|
||||
|
||||
2. **From Contracts**:
|
||||
- Map each contract/endpoint → to the user story it serves
|
||||
- If tests requested: Each contract → contract test task [P] before implementation in that story's phase
|
||||
|
||||
3. **From Data Model**:
|
||||
- Map each entity to the user story(ies) that need it
|
||||
- If entity serves multiple stories: Put in earliest story or Setup phase
|
||||
- Relationships → service layer tasks in appropriate story phase
|
||||
|
||||
4. **From Setup/Infrastructure**:
|
||||
- Shared infrastructure → Setup phase (Phase 1)
|
||||
- Foundational/blocking tasks → Foundational phase (Phase 2)
|
||||
- Story-specific setup → within that story's phase
|
||||
|
||||
### Phase Structure
|
||||
|
||||
- **Phase 1**: Setup (project initialization)
|
||||
- **Phase 2**: Foundational (blocking prerequisites - MUST complete before user stories)
|
||||
- **Phase 3+**: User Stories in priority order (P1, P2, P3...)
|
||||
- Within each story: Tests (if requested) → Models → Services → Endpoints → Integration
|
||||
- Each phase should be a complete, independently testable increment
|
||||
- **Final Phase**: Polish & Cross-Cutting Concerns
|
||||
"""
|
||||
|
|
@ -0,0 +1,32 @@
|
|||
description = "Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts."
|
||||
|
||||
prompt = """
|
||||
---
|
||||
description: Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
|
||||
tools: ['github/github-mcp-server/issue_write']
|
||||
---
|
||||
|
||||
## User Input
|
||||
|
||||
```text
|
||||
$ARGUMENTS
|
||||
```
|
||||
|
||||
You **MUST** consider the user input before proceeding (if not empty).
|
||||
|
||||
## Outline
|
||||
|
||||
1. Run `.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasks` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'\\''m Groot' (or double-quote if possible: "I'm Groot").
|
||||
1. From the executed script, extract the path to **tasks**.
|
||||
1. Get the Git remote by running:
|
||||
|
||||
```bash
|
||||
git config --get remote.origin.url
|
||||
```
|
||||
|
||||
**ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL**
|
||||
|
||||
1. For each task in the list, use the GitHub MCP server to create a new issue in the repository that is representative of the Git remote.
|
||||
|
||||
**UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE URL**
|
||||
"""
|
||||
|
|
@ -0,0 +1,50 @@
|
|||
# [PROJECT_NAME] Constitution
|
||||
<!-- Example: Spec Constitution, TaskFlow Constitution, etc. -->
|
||||
|
||||
## Core Principles
|
||||
|
||||
### [PRINCIPLE_1_NAME]
|
||||
<!-- Example: I. Library-First -->
|
||||
[PRINCIPLE_1_DESCRIPTION]
|
||||
<!-- Example: Every feature starts as a standalone library; Libraries must be self-contained, independently testable, documented; Clear purpose required - no organizational-only libraries -->
|
||||
|
||||
### [PRINCIPLE_2_NAME]
|
||||
<!-- Example: II. CLI Interface -->
|
||||
[PRINCIPLE_2_DESCRIPTION]
|
||||
<!-- Example: Every library exposes functionality via CLI; Text in/out protocol: stdin/args → stdout, errors → stderr; Support JSON + human-readable formats -->
|
||||
|
||||
### [PRINCIPLE_3_NAME]
|
||||
<!-- Example: III. Test-First (NON-NEGOTIABLE) -->
|
||||
[PRINCIPLE_3_DESCRIPTION]
|
||||
<!-- Example: TDD mandatory: Tests written → User approved → Tests fail → Then implement; Red-Green-Refactor cycle strictly enforced -->
|
||||
|
||||
### [PRINCIPLE_4_NAME]
|
||||
<!-- Example: IV. Integration Testing -->
|
||||
[PRINCIPLE_4_DESCRIPTION]
|
||||
<!-- Example: Focus areas requiring integration tests: New library contract tests, Contract changes, Inter-service communication, Shared schemas -->
|
||||
|
||||
### [PRINCIPLE_5_NAME]
|
||||
<!-- Example: V. Observability, VI. Versioning & Breaking Changes, VII. Simplicity -->
|
||||
[PRINCIPLE_5_DESCRIPTION]
|
||||
<!-- Example: Text I/O ensures debuggability; Structured logging required; Or: MAJOR.MINOR.BUILD format; Or: Start simple, YAGNI principles -->
|
||||
|
||||
## [SECTION_2_NAME]
|
||||
<!-- Example: Additional Constraints, Security Requirements, Performance Standards, etc. -->
|
||||
|
||||
[SECTION_2_CONTENT]
|
||||
<!-- Example: Technology stack requirements, compliance standards, deployment policies, etc. -->
|
||||
|
||||
## [SECTION_3_NAME]
|
||||
<!-- Example: Development Workflow, Review Process, Quality Gates, etc. -->
|
||||
|
||||
[SECTION_3_CONTENT]
|
||||
<!-- Example: Code review requirements, testing gates, deployment approval process, etc. -->
|
||||
|
||||
## Governance
|
||||
<!-- Example: Constitution supersedes all other practices; Amendments require documentation, approval, migration plan -->
|
||||
|
||||
[GOVERNANCE_RULES]
|
||||
<!-- Example: All PRs/reviews must verify compliance; Complexity must be justified; Use [GUIDANCE_FILE] for runtime development guidance -->
|
||||
|
||||
**Version**: [CONSTITUTION_VERSION] | **Ratified**: [RATIFICATION_DATE] | **Last Amended**: [LAST_AMENDED_DATE]
|
||||
<!-- Example: Version: 2.1.1 | Ratified: 2025-06-13 | Last Amended: 2025-07-16 -->
|
||||
|
|
@ -0,0 +1,166 @@
|
|||
#!/usr/bin/env bash
|
||||
|
||||
# Consolidated prerequisite checking script
|
||||
#
|
||||
# This script provides unified prerequisite checking for Spec-Driven Development workflow.
|
||||
# It replaces the functionality previously spread across multiple scripts.
|
||||
#
|
||||
# Usage: ./check-prerequisites.sh [OPTIONS]
|
||||
#
|
||||
# OPTIONS:
|
||||
# --json Output in JSON format
|
||||
# --require-tasks Require tasks.md to exist (for implementation phase)
|
||||
# --include-tasks Include tasks.md in AVAILABLE_DOCS list
|
||||
# --paths-only Only output path variables (no validation)
|
||||
# --help, -h Show help message
|
||||
#
|
||||
# OUTPUTS:
|
||||
# JSON mode: {"FEATURE_DIR":"...", "AVAILABLE_DOCS":["..."]}
|
||||
# Text mode: FEATURE_DIR:... \n AVAILABLE_DOCS: \n ✓/✗ file.md
|
||||
# Paths only: REPO_ROOT: ... \n BRANCH: ... \n FEATURE_DIR: ... etc.
|
||||
|
||||
set -e
|
||||
|
||||
# Parse command line arguments
|
||||
JSON_MODE=false
|
||||
REQUIRE_TASKS=false
|
||||
INCLUDE_TASKS=false
|
||||
PATHS_ONLY=false
|
||||
|
||||
for arg in "$@"; do
|
||||
case "$arg" in
|
||||
--json)
|
||||
JSON_MODE=true
|
||||
;;
|
||||
--require-tasks)
|
||||
REQUIRE_TASKS=true
|
||||
;;
|
||||
--include-tasks)
|
||||
INCLUDE_TASKS=true
|
||||
;;
|
||||
--paths-only)
|
||||
PATHS_ONLY=true
|
||||
;;
|
||||
--help|-h)
|
||||
cat << 'EOF'
|
||||
Usage: check-prerequisites.sh [OPTIONS]
|
||||
|
||||
Consolidated prerequisite checking for Spec-Driven Development workflow.
|
||||
|
||||
OPTIONS:
|
||||
--json Output in JSON format
|
||||
--require-tasks Require tasks.md to exist (for implementation phase)
|
||||
--include-tasks Include tasks.md in AVAILABLE_DOCS list
|
||||
--paths-only Only output path variables (no prerequisite validation)
|
||||
--help, -h Show this help message
|
||||
|
||||
EXAMPLES:
|
||||
# Check task prerequisites (plan.md required)
|
||||
./check-prerequisites.sh --json
|
||||
|
||||
# Check implementation prerequisites (plan.md + tasks.md required)
|
||||
./check-prerequisites.sh --json --require-tasks --include-tasks
|
||||
|
||||
# Get feature paths only (no validation)
|
||||
./check-prerequisites.sh --paths-only
|
||||
|
||||
EOF
|
||||
exit 0
|
||||
;;
|
||||
*)
|
||||
echo "ERROR: Unknown option '$arg'. Use --help for usage information." >&2
|
||||
exit 1
|
||||
;;
|
||||
esac
|
||||
done
|
||||
|
||||
# Source common functions
|
||||
SCRIPT_DIR="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
|
||||
source "$SCRIPT_DIR/common.sh"
|
||||
|
||||
# Get feature paths and validate branch
|
||||
eval $(get_feature_paths)
|
||||
check_feature_branch "$CURRENT_BRANCH" "$HAS_GIT" || exit 1
|
||||
|
||||
# If paths-only mode, output paths and exit (support JSON + paths-only combined)
|
||||
if $PATHS_ONLY; then
|
||||
if $JSON_MODE; then
|
||||
# Minimal JSON paths payload (no validation performed)
|
||||
printf '{"REPO_ROOT":"%s","BRANCH":"%s","FEATURE_DIR":"%s","FEATURE_SPEC":"%s","IMPL_PLAN":"%s","TASKS":"%s"}\n' \
|
||||
"$REPO_ROOT" "$CURRENT_BRANCH" "$FEATURE_DIR" "$FEATURE_SPEC" "$IMPL_PLAN" "$TASKS"
|
||||
else
|
||||
echo "REPO_ROOT: $REPO_ROOT"
|
||||
echo "BRANCH: $CURRENT_BRANCH"
|
||||
echo "FEATURE_DIR: $FEATURE_DIR"
|
||||
echo "FEATURE_SPEC: $FEATURE_SPEC"
|
||||
echo "IMPL_PLAN: $IMPL_PLAN"
|
||||
echo "TASKS: $TASKS"
|
||||
fi
|
||||
exit 0
|
||||
fi
|
||||
|
||||
# Validate required directories and files
|
||||
if [[ ! -d "$FEATURE_DIR" ]]; then
|
||||
echo "ERROR: Feature directory not found: $FEATURE_DIR" >&2
|
||||
echo "Run /speckit.specify first to create the feature structure." >&2
|
||||
exit 1
|
||||
fi
|
||||
|
||||
if [[ ! -f "$IMPL_PLAN" ]]; then
|
||||
echo "ERROR: plan.md not found in $FEATURE_DIR" >&2
|
||||
echo "Run /speckit.plan first to create the implementation plan." >&2
|
||||
exit 1
|
||||
fi
|
||||
|
||||
# Check for tasks.md if required
|
||||
if $REQUIRE_TASKS && [[ ! -f "$TASKS" ]]; then
|
||||
echo "ERROR: tasks.md not found in $FEATURE_DIR" >&2
|
||||
echo "Run /speckit.tasks first to create the task list." >&2
|
||||
exit 1
|
||||
fi
|
||||
|
||||
# Build list of available documents
|
||||
docs=()
|
||||
|
||||
# Always check these optional docs
|
||||
[[ -f "$RESEARCH" ]] && docs+=("research.md")
|
||||
[[ -f "$DATA_MODEL" ]] && docs+=("data-model.md")
|
||||
|
||||
# Check contracts directory (only if it exists and has files)
|
||||
if [[ -d "$CONTRACTS_DIR" ]] && [[ -n "$(ls -A "$CONTRACTS_DIR" 2>/dev/null)" ]]; then
|
||||
docs+=("contracts/")
|
||||
fi
|
||||
|
||||
[[ -f "$QUICKSTART" ]] && docs+=("quickstart.md")
|
||||
|
||||
# Include tasks.md if requested and it exists
|
||||
if $INCLUDE_TASKS && [[ -f "$TASKS" ]]; then
|
||||
docs+=("tasks.md")
|
||||
fi
|
||||
|
||||
# Output results
|
||||
if $JSON_MODE; then
|
||||
# Build JSON array of documents
|
||||
if [[ ${#docs[@]} -eq 0 ]]; then
|
||||
json_docs="[]"
|
||||
else
|
||||
json_docs=$(printf '"%s",' "${docs[@]}")
|
||||
json_docs="[${json_docs%,}]"
|
||||
fi
|
||||
|
||||
printf '{"FEATURE_DIR":"%s","AVAILABLE_DOCS":%s}\n' "$FEATURE_DIR" "$json_docs"
|
||||
else
|
||||
# Text output
|
||||
echo "FEATURE_DIR:$FEATURE_DIR"
|
||||
echo "AVAILABLE_DOCS:"
|
||||
|
||||
# Show status of each potential document
|
||||
check_file "$RESEARCH" "research.md"
|
||||
check_file "$DATA_MODEL" "data-model.md"
|
||||
check_dir "$CONTRACTS_DIR" "contracts/"
|
||||
check_file "$QUICKSTART" "quickstart.md"
|
||||
|
||||
if $INCLUDE_TASKS; then
|
||||
check_file "$TASKS" "tasks.md"
|
||||
fi
|
||||
fi
|
||||
|
|
@ -0,0 +1,156 @@
|
|||
#!/usr/bin/env bash
|
||||
# Common functions and variables for all scripts
|
||||
|
||||
# Get repository root, with fallback for non-git repositories
|
||||
get_repo_root() {
|
||||
if git rev-parse --show-toplevel >/dev/null 2>&1; then
|
||||
git rev-parse --show-toplevel
|
||||
else
|
||||
# Fall back to script location for non-git repos
|
||||
local script_dir="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
|
||||
(cd "$script_dir/../../.." && pwd)
|
||||
fi
|
||||
}
|
||||
|
||||
# Get current branch, with fallback for non-git repositories
|
||||
get_current_branch() {
|
||||
# First check if SPECIFY_FEATURE environment variable is set
|
||||
if [[ -n "${SPECIFY_FEATURE:-}" ]]; then
|
||||
echo "$SPECIFY_FEATURE"
|
||||
return
|
||||
fi
|
||||
|
||||
# Then check git if available
|
||||
if git rev-parse --abbrev-ref HEAD >/dev/null 2>&1; then
|
||||
git rev-parse --abbrev-ref HEAD
|
||||
return
|
||||
fi
|
||||
|
||||
# For non-git repos, try to find the latest feature directory
|
||||
local repo_root=$(get_repo_root)
|
||||
local specs_dir="$repo_root/specs"
|
||||
|
||||
if [[ -d "$specs_dir" ]]; then
|
||||
local latest_feature=""
|
||||
local highest=0
|
||||
|
||||
for dir in "$specs_dir"/*; do
|
||||
if [[ -d "$dir" ]]; then
|
||||
local dirname=$(basename "$dir")
|
||||
if [[ "$dirname" =~ ^([0-9]{3})- ]]; then
|
||||
local number=${BASH_REMATCH[1]}
|
||||
number=$((10#$number))
|
||||
if [[ "$number" -gt "$highest" ]]; then
|
||||
highest=$number
|
||||
latest_feature=$dirname
|
||||
fi
|
||||
fi
|
||||
fi
|
||||
done
|
||||
|
||||
if [[ -n "$latest_feature" ]]; then
|
||||
echo "$latest_feature"
|
||||
return
|
||||
fi
|
||||
fi
|
||||
|
||||
echo "main" # Final fallback
|
||||
}
|
||||
|
||||
# Check if we have git available
|
||||
has_git() {
|
||||
git rev-parse --show-toplevel >/dev/null 2>&1
|
||||
}
|
||||
|
||||
check_feature_branch() {
|
||||
local branch="$1"
|
||||
local has_git_repo="$2"
|
||||
|
||||
# For non-git repos, we can't enforce branch naming but still provide output
|
||||
if [[ "$has_git_repo" != "true" ]]; then
|
||||
echo "[specify] Warning: Git repository not detected; skipped branch validation" >&2
|
||||
return 0
|
||||
fi
|
||||
|
||||
if [[ ! "$branch" =~ ^[0-9]{3}- ]]; then
|
||||
echo "ERROR: Not on a feature branch. Current branch: $branch" >&2
|
||||
echo "Feature branches should be named like: 001-feature-name" >&2
|
||||
return 1
|
||||
fi
|
||||
|
||||
return 0
|
||||
}
|
||||
|
||||
get_feature_dir() { echo "$1/specs/$2"; }
|
||||
|
||||
# Find feature directory by numeric prefix instead of exact branch match
|
||||
# This allows multiple branches to work on the same spec (e.g., 004-fix-bug, 004-add-feature)
|
||||
find_feature_dir_by_prefix() {
|
||||
local repo_root="$1"
|
||||
local branch_name="$2"
|
||||
local specs_dir="$repo_root/specs"
|
||||
|
||||
# Extract numeric prefix from branch (e.g., "004" from "004-whatever")
|
||||
if [[ ! "$branch_name" =~ ^([0-9]{3})- ]]; then
|
||||
# If branch doesn't have numeric prefix, fall back to exact match
|
||||
echo "$specs_dir/$branch_name"
|
||||
return
|
||||
fi
|
||||
|
||||
local prefix="${BASH_REMATCH[1]}"
|
||||
|
||||
# Search for directories in specs/ that start with this prefix
|
||||
local matches=()
|
||||
if [[ -d "$specs_dir" ]]; then
|
||||
for dir in "$specs_dir"/"$prefix"-*; do
|
||||
if [[ -d "$dir" ]]; then
|
||||
matches+=("$(basename "$dir")")
|
||||
fi
|
||||
done
|
||||
fi
|
||||
|
||||
# Handle results
|
||||
if [[ ${#matches[@]} -eq 0 ]]; then
|
||||
# No match found - return the branch name path (will fail later with clear error)
|
||||
echo "$specs_dir/$branch_name"
|
||||
elif [[ ${#matches[@]} -eq 1 ]]; then
|
||||
# Exactly one match - perfect!
|
||||
echo "$specs_dir/${matches[0]}"
|
||||
else
|
||||
# Multiple matches - this shouldn't happen with proper naming convention
|
||||
echo "ERROR: Multiple spec directories found with prefix '$prefix': ${matches[*]}" >&2
|
||||
echo "Please ensure only one spec directory exists per numeric prefix." >&2
|
||||
echo "$specs_dir/$branch_name" # Return something to avoid breaking the script
|
||||
fi
|
||||
}
|
||||
|
||||
get_feature_paths() {
|
||||
local repo_root=$(get_repo_root)
|
||||
local current_branch=$(get_current_branch)
|
||||
local has_git_repo="false"
|
||||
|
||||
if has_git; then
|
||||
has_git_repo="true"
|
||||
fi
|
||||
|
||||
# Use prefix-based lookup to support multiple branches per spec
|
||||
local feature_dir=$(find_feature_dir_by_prefix "$repo_root" "$current_branch")
|
||||
|
||||
cat <<EOF
|
||||
REPO_ROOT='$repo_root'
|
||||
CURRENT_BRANCH='$current_branch'
|
||||
HAS_GIT='$has_git_repo'
|
||||
FEATURE_DIR='$feature_dir'
|
||||
FEATURE_SPEC='$feature_dir/spec.md'
|
||||
IMPL_PLAN='$feature_dir/plan.md'
|
||||
TASKS='$feature_dir/tasks.md'
|
||||
RESEARCH='$feature_dir/research.md'
|
||||
DATA_MODEL='$feature_dir/data-model.md'
|
||||
QUICKSTART='$feature_dir/quickstart.md'
|
||||
CONTRACTS_DIR='$feature_dir/contracts'
|
||||
EOF
|
||||
}
|
||||
|
||||
check_file() { [[ -f "$1" ]] && echo " ✓ $2" || echo " ✗ $2"; }
|
||||
check_dir() { [[ -d "$1" && -n $(ls -A "$1" 2>/dev/null) ]] && echo " ✓ $2" || echo " ✗ $2"; }
|
||||
|
||||
|
|
@ -0,0 +1,330 @@
|
|||
#!/usr/bin/env bash
|
||||
|
||||
set -e
|
||||
|
||||
JSON_MODE=false
|
||||
SHORT_NAME=""
|
||||
BRANCH_NUMBER=""
|
||||
ARGS=()
|
||||
i=1
|
||||
while [ $i -le $# ]; do
|
||||
arg="${!i}"
|
||||
case "$arg" in
|
||||
--json)
|
||||
JSON_MODE=true
|
||||
;;
|
||||
--short-name)
|
||||
if [ $((i + 1)) -gt $# ]; then
|
||||
echo 'Error: --short-name requires a value' >&2
|
||||
exit 1
|
||||
fi
|
||||
i=$((i + 1))
|
||||
next_arg="${!i}"
|
||||
# Check if the next argument is another option (starts with --)
|
||||
if [[ "$next_arg" == --* ]]; then
|
||||
echo 'Error: --short-name requires a value' >&2
|
||||
exit 1
|
||||
fi
|
||||
SHORT_NAME="$next_arg"
|
||||
;;
|
||||
--number)
|
||||
if [ $((i + 1)) -gt $# ]; then
|
||||
echo 'Error: --number requires a value' >&2
|
||||
exit 1
|
||||
fi
|
||||
i=$((i + 1))
|
||||
next_arg="${!i}"
|
||||
if [[ "$next_arg" == --* ]]; then
|
||||
echo 'Error: --number requires a value' >&2
|
||||
exit 1
|
||||
fi
|
||||
BRANCH_NUMBER="$next_arg"
|
||||
;;
|
||||
--file)
|
||||
if [ $((i + 1)) -gt $# ]; then
|
||||
echo 'Error: --file requires a value' >&2
|
||||
exit 1
|
||||
fi
|
||||
i=$((i + 1))
|
||||
next_arg="${!i}"
|
||||
if [[ "$next_arg" == --* ]]; then
|
||||
echo 'Error: --file requires a value' >&2
|
||||
exit 1
|
||||
fi
|
||||
FEATURE_FILE="$next_arg"
|
||||
;;
|
||||
--help|-h)
|
||||
echo "Usage: $0 [--json] [--short-name <name>] [--number N] [--file <path>] <feature_description>"
|
||||
echo ""
|
||||
echo "Options:"
|
||||
echo " --json Output in JSON format"
|
||||
echo " --short-name <name> Provide a custom short name (2-4 words) for the branch"
|
||||
echo " --number N Specify branch number manually (overrides auto-detection)"
|
||||
echo " --file <path> Read feature description from a file"
|
||||
echo " --help, -h Show this help message"
|
||||
echo ""
|
||||
echo "Examples:"
|
||||
echo " $0 'Add user authentication system' --short-name 'user-auth'"
|
||||
echo " $0 'Implement OAuth2 integration for API' --number 5"
|
||||
echo " $0 --file my_feature.md --short-name 'new-feature'"
|
||||
exit 0
|
||||
;;
|
||||
*)
|
||||
ARGS+=("$arg")
|
||||
;;
|
||||
esac
|
||||
i=$((i + 1))
|
||||
done
|
||||
|
||||
FEATURE_DESCRIPTION=""
|
||||
if [ -n "$FEATURE_FILE" ]; then
|
||||
if [ ! -f "$FEATURE_FILE" ]; then
|
||||
echo "Error: Feature file not found: $FEATURE_FILE" >&2
|
||||
exit 1
|
||||
fi
|
||||
FEATURE_DESCRIPTION=$(cat "$FEATURE_FILE")
|
||||
elif [ ${#ARGS[@]} -gt 0 ]; then
|
||||
FEATURE_DESCRIPTION="${ARGS[*]}"
|
||||
fi
|
||||
|
||||
if [ -z "$FEATURE_DESCRIPTION" ]; then
|
||||
echo "Usage: $0 [--json] [--short-name <name>] [--number N] [--file <path>] <feature_description>" >&2
|
||||
exit 1
|
||||
fi
|
||||
|
||||
# Function to find the repository root by searching for existing project markers
|
||||
find_repo_root() {
|
||||
local dir="$1"
|
||||
while [ "$dir" != "/" ]; do
|
||||
if [ -d "$dir/.git" ] || [ -d "$dir/.specify" ]; then
|
||||
echo "$dir"
|
||||
return 0
|
||||
fi
|
||||
dir="$(dirname "$dir")"
|
||||
done
|
||||
return 1
|
||||
}
|
||||
|
||||
# Function to get highest number from specs directory
|
||||
get_highest_from_specs() {
|
||||
local specs_dir="$1"
|
||||
local highest=0
|
||||
|
||||
if [ -d "$specs_dir" ]; then
|
||||
for dir in "$specs_dir"/*; do
|
||||
[ -d "$dir" ] || continue
|
||||
dirname=$(basename "$dir")
|
||||
number=$(echo "$dirname" | grep -o '^[0-9]\+' || echo "0")
|
||||
number=$((10#$number))
|
||||
if [ "$number" -gt "$highest" ]; then
|
||||
highest=$number
|
||||
fi
|
||||
done
|
||||
fi
|
||||
|
||||
echo "$highest"
|
||||
}
|
||||
|
||||
# Function to get highest number from git branches
|
||||
get_highest_from_branches() {
|
||||
local highest=0
|
||||
|
||||
# Get all branches (local and remote)
|
||||
branches=$(git branch -a 2>/dev/null || echo "")
|
||||
|
||||
if [ -n "$branches" ]; then
|
||||
while IFS= read -r branch; do
|
||||
# Clean branch name: remove leading markers and remote prefixes
|
||||
clean_branch=$(echo "$branch" | sed 's/^[* ]*//; s|^remotes/[^/]*/||')
|
||||
|
||||
# Extract feature number if branch matches pattern ###-*
|
||||
if echo "$clean_branch" | grep -q '^[0-9]\{3\}-'; then
|
||||
number=$(echo "$clean_branch" | grep -o '^[0-9]\{3\}' || echo "0")
|
||||
number=$((10#$number))
|
||||
if [ "$number" -gt "$highest" ]; then
|
||||
highest=$number
|
||||
fi
|
||||
fi
|
||||
done <<< "$branches"
|
||||
fi
|
||||
|
||||
echo "$highest"
|
||||
}
|
||||
|
||||
# Function to check existing branches (local and remote) and return next available number
|
||||
check_existing_branches() {
|
||||
local short_name="$1"
|
||||
local specs_dir="$2"
|
||||
|
||||
# Fetch all remotes to get latest branch info (suppress errors if no remotes)
|
||||
git fetch --all --prune 2>/dev/null || true
|
||||
|
||||
# Find all branches matching the pattern using git ls-remote (more reliable)
|
||||
local remote_branches=$(git ls-remote --heads origin 2>/dev/null | grep -E "refs/heads/[0-9]+-${short_name}$" | sed 's/.*\/\([0-9]*\)-.*/\1/' | sort -n)
|
||||
|
||||
# Also check local branches
|
||||
local local_branches=$(git branch 2>/dev/null | grep -E "^[* ]*[0-9]+-${short_name}$" | sed 's/^[* ]*//' | sed 's/-.*//' | sort -n)
|
||||
|
||||
# Check specs directory as well
|
||||
local spec_dirs=""
|
||||
if [ -d "$specs_dir" ]; then
|
||||
spec_dirs=$(find "$specs_dir" -maxdepth 1 -type d -name "[0-9]*-${short_name}" 2>/dev/null | xargs -n1 basename 2>/dev/null | sed 's/-.*//' | sort -n)
|
||||
fi
|
||||
|
||||
# Combine all sources and get the highest number
|
||||
local max_num=0
|
||||
for num in $remote_branches $local_branches $spec_dirs; do
|
||||
if [ "$num" -gt "$max_num" ]; then
|
||||
max_num=$num
|
||||
fi
|
||||
done
|
||||
|
||||
# Return next number
|
||||
echo $((max_num + 1))
|
||||
}
|
||||
|
||||
# Function to clean and format a branch name
|
||||
clean_branch_name() {
|
||||
local name="$1"
|
||||
echo "$name" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/-\+/-/g' | sed 's/^-//' | sed 's/-$//'
|
||||
}
|
||||
|
||||
# Resolve repository root. Prefer git information when available, but fall back
|
||||
# to searching for repository markers so the workflow still functions in repositories that
|
||||
# were initialised with --no-git.
|
||||
SCRIPT_DIR="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
|
||||
|
||||
if git rev-parse --show-toplevel >/dev/null 2>&1; then
|
||||
REPO_ROOT=$(git rev-parse --show-toplevel)
|
||||
HAS_GIT=true
|
||||
else
|
||||
REPO_ROOT="$(find_repo_root "$SCRIPT_DIR")"
|
||||
if [ -z "$REPO_ROOT" ]; then
|
||||
echo "Error: Could not determine repository root. Please run this script from within the repository." >&2
|
||||
exit 1
|
||||
fi
|
||||
HAS_GIT=false
|
||||
fi
|
||||
|
||||
cd "$REPO_ROOT"
|
||||
|
||||
SPECS_DIR="$REPO_ROOT/specs"
|
||||
mkdir -p "$SPECS_DIR"
|
||||
|
||||
# Function to generate branch name with stop word filtering and length filtering
|
||||
generate_branch_name() {
|
||||
local description="$1"
|
||||
|
||||
# Common stop words to filter out
|
||||
local stop_words="^(i|a|an|the|to|for|of|in|on|at|by|with|from|is|are|was|were|be|been|being|have|has|had|do|does|did|will|would|should|could|can|may|might|must|shall|this|that|these|those|my|your|our|their|want|need|add|get|set)$"
|
||||
|
||||
# Convert to lowercase and split into words
|
||||
local clean_name=$(echo "$description" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/ /g')
|
||||
|
||||
# Filter words: remove stop words and words shorter than 3 chars (unless they're uppercase acronyms in original)
|
||||
local meaningful_words=()
|
||||
for word in $clean_name; do
|
||||
# Skip empty words
|
||||
[ -z "$word" ] && continue
|
||||
|
||||
# Keep words that are NOT stop words AND (length >= 3 OR are potential acronyms)
|
||||
if ! echo "$word" | grep -qiE "$stop_words"; then
|
||||
if [ ${#word} -ge 3 ]; then
|
||||
meaningful_words+=("$word")
|
||||
elif echo "$description" | grep -q "\b${word^^}\b"; then
|
||||
# Keep short words if they appear as uppercase in original (likely acronyms)
|
||||
meaningful_words+=("$word")
|
||||
fi
|
||||
fi
|
||||
done
|
||||
|
||||
# If we have meaningful words, use first 3-4 of them
|
||||
if [ ${#meaningful_words[@]} -gt 0 ]; then
|
||||
local max_words=3
|
||||
if [ ${#meaningful_words[@]} -eq 4 ]; then max_words=4; fi
|
||||
|
||||
local result=""
|
||||
local count=0
|
||||
for word in "${meaningful_words[@]}"; do
|
||||
if [ $count -ge $max_words ]; then break; fi
|
||||
if [ -n "$result" ]; then result="$result-"; fi
|
||||
result="$result$word"
|
||||
count=$((count + 1))
|
||||
done
|
||||
echo "$result"
|
||||
else
|
||||
# Fallback to original logic if no meaningful words found
|
||||
local cleaned=$(clean_branch_name "$description")
|
||||
echo "$cleaned" | tr '-' '\n' | grep -v '^$' | head -3 | tr '\n' '-' | sed 's/-$//'
|
||||
fi
|
||||
}
|
||||
|
||||
# Generate branch name
|
||||
if [ -n "$SHORT_NAME" ]; then
|
||||
# Use provided short name, just clean it up
|
||||
BRANCH_SUFFIX=$(clean_branch_name "$SHORT_NAME")
|
||||
else
|
||||
# Generate from description with smart filtering
|
||||
BRANCH_SUFFIX=$(generate_branch_name "$FEATURE_DESCRIPTION")
|
||||
fi
|
||||
|
||||
# Determine branch number
|
||||
if [ -z "$BRANCH_NUMBER" ]; then
|
||||
if [ "$HAS_GIT" = true ]; then
|
||||
# Check existing branches on remotes
|
||||
BRANCH_NUMBER=$(check_existing_branches "$BRANCH_SUFFIX" "$SPECS_DIR")
|
||||
else
|
||||
# Fall back to local directory check
|
||||
HIGHEST=$(get_highest_from_specs "$SPECS_DIR")
|
||||
BRANCH_NUMBER=$((HIGHEST + 1))
|
||||
fi
|
||||
fi
|
||||
|
||||
FEATURE_NUM=$(printf "%03d" "$BRANCH_NUMBER")
|
||||
BRANCH_NAME="${FEATURE_NUM}-${BRANCH_SUFFIX}"
|
||||
|
||||
# GitHub enforces a 244-byte limit on branch names
|
||||
# Validate and truncate if necessary
|
||||
MAX_BRANCH_LENGTH=244
|
||||
if [ ${#BRANCH_NAME} -gt $MAX_BRANCH_LENGTH ]; then
|
||||
# Calculate how much we need to trim from suffix
|
||||
# Account for: feature number (3) + hyphen (1) = 4 chars
|
||||
MAX_SUFFIX_LENGTH=$((MAX_BRANCH_LENGTH - 4))
|
||||
|
||||
# Truncate suffix at word boundary if possible
|
||||
TRUNCATED_SUFFIX=$(echo "$BRANCH_SUFFIX" | cut -c1-$MAX_SUFFIX_LENGTH)
|
||||
# Remove trailing hyphen if truncation created one
|
||||
TRUNCATED_SUFFIX=$(echo "$TRUNCATED_SUFFIX" | sed 's/-$//')
|
||||
|
||||
ORIGINAL_BRANCH_NAME="$BRANCH_NAME"
|
||||
BRANCH_NAME="${FEATURE_NUM}-${TRUNCATED_SUFFIX}"
|
||||
|
||||
>&2 echo "[specify] Warning: Branch name exceeded GitHub's 244-byte limit"
|
||||
>&2 echo "[specify] Original: $ORIGINAL_BRANCH_NAME (${#ORIGINAL_BRANCH_NAME} bytes)"
|
||||
>&2 echo "[specify] Truncated to: $BRANCH_NAME (${#BRANCH_NAME} bytes)"
|
||||
fi
|
||||
|
||||
if [ "$HAS_GIT" = true ]; then
|
||||
git checkout -b "$BRANCH_NAME"
|
||||
else
|
||||
>&2 echo "[specify] Warning: Git repository not detected; skipped branch creation for $BRANCH_NAME"
|
||||
fi
|
||||
|
||||
FEATURE_DIR="$SPECS_DIR/$BRANCH_NAME"
|
||||
mkdir -p "$FEATURE_DIR"
|
||||
|
||||
TEMPLATE="$REPO_ROOT/.specify/templates/spec-template.md"
|
||||
SPEC_FILE="$FEATURE_DIR/spec.md"
|
||||
if [ -f "$TEMPLATE" ]; then cp "$TEMPLATE" "$SPEC_FILE"; else touch "$SPEC_FILE"; fi
|
||||
|
||||
# Set the SPECIFY_FEATURE environment variable for the current session
|
||||
export SPECIFY_FEATURE="$BRANCH_NAME"
|
||||
|
||||
if $JSON_MODE; then
|
||||
printf '{"BRANCH_NAME":"%s","SPEC_FILE":"%s","FEATURE_NUM":"%s"}\n' "$BRANCH_NAME" "$SPEC_FILE" "$FEATURE_NUM"
|
||||
else
|
||||
echo "BRANCH_NAME: $BRANCH_NAME"
|
||||
echo "SPEC_FILE: $SPEC_FILE"
|
||||
echo "FEATURE_NUM: $FEATURE_NUM"
|
||||
echo "SPECIFY_FEATURE environment variable set to: $BRANCH_NAME"
|
||||
fi
|
||||
|
|
@ -0,0 +1,61 @@
|
|||
#!/usr/bin/env bash
|
||||
|
||||
set -e
|
||||
|
||||
# Parse command line arguments
|
||||
JSON_MODE=false
|
||||
ARGS=()
|
||||
|
||||
for arg in "$@"; do
|
||||
case "$arg" in
|
||||
--json)
|
||||
JSON_MODE=true
|
||||
;;
|
||||
--help|-h)
|
||||
echo "Usage: $0 [--json]"
|
||||
echo " --json Output results in JSON format"
|
||||
echo " --help Show this help message"
|
||||
exit 0
|
||||
;;
|
||||
*)
|
||||
ARGS+=("$arg")
|
||||
;;
|
||||
esac
|
||||
done
|
||||
|
||||
# Get script directory and load common functions
|
||||
SCRIPT_DIR="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
|
||||
source "$SCRIPT_DIR/common.sh"
|
||||
|
||||
# Get all paths and variables from common functions
|
||||
eval $(get_feature_paths)
|
||||
|
||||
# Check if we're on a proper feature branch (only for git repos)
|
||||
check_feature_branch "$CURRENT_BRANCH" "$HAS_GIT" || exit 1
|
||||
|
||||
# Ensure the feature directory exists
|
||||
mkdir -p "$FEATURE_DIR"
|
||||
|
||||
# Copy plan template if it exists
|
||||
TEMPLATE="$REPO_ROOT/.specify/templates/plan-template.md"
|
||||
if [[ -f "$TEMPLATE" ]]; then
|
||||
cp "$TEMPLATE" "$IMPL_PLAN"
|
||||
echo "Copied plan template to $IMPL_PLAN"
|
||||
else
|
||||
echo "Warning: Plan template not found at $TEMPLATE"
|
||||
# Create a basic plan file if template doesn't exist
|
||||
touch "$IMPL_PLAN"
|
||||
fi
|
||||
|
||||
# Output results
|
||||
if $JSON_MODE; then
|
||||
printf '{"FEATURE_SPEC":"%s","IMPL_PLAN":"%s","SPECS_DIR":"%s","BRANCH":"%s","HAS_GIT":"%s"}\n' \
|
||||
"$FEATURE_SPEC" "$IMPL_PLAN" "$FEATURE_DIR" "$CURRENT_BRANCH" "$HAS_GIT"
|
||||
else
|
||||
echo "FEATURE_SPEC: $FEATURE_SPEC"
|
||||
echo "IMPL_PLAN: $IMPL_PLAN"
|
||||
echo "SPECS_DIR: $FEATURE_DIR"
|
||||
echo "BRANCH: $CURRENT_BRANCH"
|
||||
echo "HAS_GIT: $HAS_GIT"
|
||||
fi
|
||||
|
||||
|
|
@ -0,0 +1,781 @@
|
|||
#!/usr/bin/env bash
|
||||
|
||||
# Update agent context files with information from plan.md
|
||||
#
|
||||
# This script maintains AI agent context files by parsing feature specifications
|
||||
# and updating agent-specific configuration files with project information.
|
||||
#
|
||||
# MAIN FUNCTIONS:
|
||||
# 1. Environment Validation
|
||||
# - Verifies git repository structure and branch information
|
||||
# - Checks for required plan.md files and templates
|
||||
# - Validates file permissions and accessibility
|
||||
#
|
||||
# 2. Plan Data Extraction
|
||||
# - Parses plan.md files to extract project metadata
|
||||
# - Identifies language/version, frameworks, databases, and project types
|
||||
# - Handles missing or incomplete specification data gracefully
|
||||
#
|
||||
# 3. Agent File Management
|
||||
# - Creates new agent context files from templates when needed
|
||||
# - Updates existing agent files with new project information
|
||||
# - Preserves manual additions and custom configurations
|
||||
# - Supports multiple AI agent formats and directory structures
|
||||
#
|
||||
# 4. Content Generation
|
||||
# - Generates language-specific build/test commands
|
||||
# - Creates appropriate project directory structures
|
||||
# - Updates technology stacks and recent changes sections
|
||||
# - Maintains consistent formatting and timestamps
|
||||
#
|
||||
# 5. Multi-Agent Support
|
||||
# - Handles agent-specific file paths and naming conventions
|
||||
# - Supports: Claude, Gemini, Copilot, Cursor, Qwen, opencode, Codex, Windsurf, Kilo Code, Auggie CLI, Roo Code, CodeBuddy CLI, Amp, SHAI, or Amazon Q Developer CLI
|
||||
# - Can update single agents or all existing agent files
|
||||
# - Creates default Claude file if no agent files exist
|
||||
#
|
||||
# Usage: ./update-agent-context.sh [agent_type]
|
||||
# Agent types: claude|gemini|copilot|cursor-agent|qwen|opencode|codex|windsurf|kilocode|auggie|shai|q
|
||||
# Leave empty to update all existing agent files
|
||||
|
||||
set -e
|
||||
|
||||
# Enable strict error handling
|
||||
set -u
|
||||
set -o pipefail
|
||||
|
||||
#==============================================================================
|
||||
# Configuration and Global Variables
|
||||
#==============================================================================
|
||||
|
||||
# Get script directory and load common functions
|
||||
SCRIPT_DIR="$(CDPATH="" cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
|
||||
source "$SCRIPT_DIR/common.sh"
|
||||
|
||||
# Get all paths and variables from common functions
|
||||
eval $(get_feature_paths)
|
||||
|
||||
NEW_PLAN="$IMPL_PLAN" # Alias for compatibility with existing code
|
||||
AGENT_TYPE="${1:-}"
|
||||
|
||||
# Agent-specific file paths
|
||||
CLAUDE_FILE="$REPO_ROOT/CLAUDE.md"
|
||||
GEMINI_FILE="$REPO_ROOT/GEMINI.md"
|
||||
COPILOT_FILE="$REPO_ROOT/.github/agents/copilot-instructions.md"
|
||||
CURSOR_FILE="$REPO_ROOT/.cursor/rules/specify-rules.mdc"
|
||||
QWEN_FILE="$REPO_ROOT/QWEN.md"
|
||||
AGENTS_FILE="$REPO_ROOT/AGENTS.md"
|
||||
WINDSURF_FILE="$REPO_ROOT/.windsurf/rules/specify-rules.md"
|
||||
KILOCODE_FILE="$REPO_ROOT/.kilocode/rules/specify-rules.md"
|
||||
AUGGIE_FILE="$REPO_ROOT/.augment/rules/specify-rules.md"
|
||||
ROO_FILE="$REPO_ROOT/.roo/rules/specify-rules.md"
|
||||
CODEBUDDY_FILE="$REPO_ROOT/CODEBUDDY.md"
|
||||
AMP_FILE="$REPO_ROOT/AGENTS.md"
|
||||
SHAI_FILE="$REPO_ROOT/SHAI.md"
|
||||
Q_FILE="$REPO_ROOT/AGENTS.md"
|
||||
|
||||
# Template file
|
||||
TEMPLATE_FILE="$REPO_ROOT/.specify/templates/agent-file-template.md"
|
||||
|
||||
# Global variables for parsed plan data
|
||||
NEW_LANG=""
|
||||
NEW_FRAMEWORK=""
|
||||
NEW_DB=""
|
||||
NEW_PROJECT_TYPE=""
|
||||
|
||||
#==============================================================================
|
||||
# Utility Functions
|
||||
#==============================================================================
|
||||
|
||||
log_info() {
|
||||
echo "INFO: $1"
|
||||
}
|
||||
|
||||
log_success() {
|
||||
echo "✓ $1"
|
||||
}
|
||||
|
||||
log_error() {
|
||||
echo "ERROR: $1" >&2
|
||||
}
|
||||
|
||||
log_warning() {
|
||||
echo "WARNING: $1" >&2
|
||||
}
|
||||
|
||||
# Cleanup function for temporary files
|
||||
cleanup() {
|
||||
local exit_code=$?
|
||||
rm -f /tmp/agent_update_*_$$
|
||||
rm -f /tmp/manual_additions_$$
|
||||
exit $exit_code
|
||||
}
|
||||
|
||||
# Set up cleanup trap
|
||||
trap cleanup EXIT INT TERM
|
||||
|
||||
#==============================================================================
|
||||
# Validation Functions
|
||||
#==============================================================================
|
||||
|
||||
validate_environment() {
|
||||
# Check if we have a current branch/feature (git or non-git)
|
||||
if [[ -z "$CURRENT_BRANCH" ]]; then
|
||||
log_error "Unable to determine current feature"
|
||||
if [[ "$HAS_GIT" == "true" ]]; then
|
||||
log_info "Make sure you're on a feature branch"
|
||||
else
|
||||
log_info "Set SPECIFY_FEATURE environment variable or create a feature first"
|
||||
fi
|
||||
exit 1
|
||||
fi
|
||||
|
||||
# Check if plan.md exists
|
||||
if [[ ! -f "$NEW_PLAN" ]]; then
|
||||
log_error "No plan.md found at $NEW_PLAN"
|
||||
log_info "Make sure you're working on a feature with a corresponding spec directory"
|
||||
if [[ "$HAS_GIT" != "true" ]]; then
|
||||
log_info "Use: export SPECIFY_FEATURE=your-feature-name or create a new feature first"
|
||||
fi
|
||||
exit 1
|
||||
fi
|
||||
|
||||
# Check if template exists (needed for new files)
|
||||
if [[ ! -f "$TEMPLATE_FILE" ]]; then
|
||||
log_warning "Template file not found at $TEMPLATE_FILE"
|
||||
log_warning "Creating new agent files will fail"
|
||||
fi
|
||||
}
|
||||
|
||||
#==============================================================================
|
||||
# Plan Parsing Functions
|
||||
#==============================================================================
|
||||
|
||||
extract_plan_field() {
|
||||
local field_pattern="$1"
|
||||
local plan_file="$2"
|
||||
|
||||
grep "^\*\*${field_pattern}\*\*: " "$plan_file" 2>/dev/null | \
|
||||
head -1 | \
|
||||
sed "s|^\*\*${field_pattern}\*\*: ||" | \
|
||||
sed 's/^[ \t]*//;s/[ \t]*$//' | \
|
||||
grep -v "NEEDS CLARIFICATION" | \
|
||||
grep -v "^N/A$" || echo ""
|
||||
}
|
||||
|
||||
parse_plan_data() {
|
||||
local plan_file="$1"
|
||||
|
||||
if [[ ! -f "$plan_file" ]]; then
|
||||
log_error "Plan file not found: $plan_file"
|
||||
return 1
|
||||
fi
|
||||
|
||||
if [[ ! -r "$plan_file" ]]; then
|
||||
log_error "Plan file is not readable: $plan_file"
|
||||
return 1
|
||||
fi
|
||||
|
||||
log_info "Parsing plan data from $plan_file"
|
||||
|
||||
NEW_LANG=$(extract_plan_field "Language/Version" "$plan_file")
|
||||
NEW_FRAMEWORK=$(extract_plan_field "Primary Dependencies" "$plan_file")
|
||||
NEW_DB=$(extract_plan_field "Storage" "$plan_file")
|
||||
NEW_PROJECT_TYPE=$(extract_plan_field "Project Type" "$plan_file")
|
||||
|
||||
# Log what we found
|
||||
if [[ -n "$NEW_LANG" ]]; then
|
||||
log_info "Found language: $NEW_LANG"
|
||||
else
|
||||
log_warning "No language information found in plan"
|
||||
fi
|
||||
|
||||
if [[ -n "$NEW_FRAMEWORK" ]]; then
|
||||
log_info "Found framework: $NEW_FRAMEWORK"
|
||||
fi
|
||||
|
||||
if [[ -n "$NEW_DB" ]] && [[ "$NEW_DB" != "N/A" ]]; then
|
||||
log_info "Found database: $NEW_DB"
|
||||
fi
|
||||
|
||||
if [[ -n "$NEW_PROJECT_TYPE" ]]; then
|
||||
log_info "Found project type: $NEW_PROJECT_TYPE"
|
||||
fi
|
||||
}
|
||||
|
||||
format_technology_stack() {
|
||||
local lang="$1"
|
||||
local framework="$2"
|
||||
local parts=()
|
||||
|
||||
# Add non-empty parts
|
||||
[[ -n "$lang" && "$lang" != "NEEDS CLARIFICATION" ]] && parts+=("$lang")
|
||||
[[ -n "$framework" && "$framework" != "NEEDS CLARIFICATION" && "$framework" != "N/A" ]] && parts+=("$framework")
|
||||
|
||||
# Join with proper formatting
|
||||
if [[ ${#parts[@]} -eq 0 ]]; then
|
||||
echo ""
|
||||
elif [[ ${#parts[@]} -eq 1 ]]; then
|
||||
echo "${parts[0]}"
|
||||
else
|
||||
# Join multiple parts with " + "
|
||||
local result="${parts[0]}"
|
||||
for ((i=1; i<${#parts[@]}; i++)); do
|
||||
result="$result + ${parts[i]}"
|
||||
done
|
||||
echo "$result"
|
||||
fi
|
||||
}
|
||||
|
||||
#==============================================================================
|
||||
# Template and Content Generation Functions
|
||||
#==============================================================================
|
||||
|
||||
get_project_structure() {
|
||||
local project_type="$1"
|
||||
|
||||
if [[ "$project_type" == *"web"* ]]; then
|
||||
echo "backend/\\nfrontend/\\ntests/"
|
||||
else
|
||||
echo "src/\\ntests/"
|
||||
fi
|
||||
}
|
||||
|
||||
get_commands_for_language() {
|
||||
local lang="$1"
|
||||
|
||||
case "$lang" in
|
||||
*"Python"*)
|
||||
echo "cd src && pytest && ruff check ."
|
||||
;;
|
||||
*"Rust"*)
|
||||
echo "cargo test && cargo clippy"
|
||||
;;
|
||||
*"JavaScript"*|*"TypeScript"*)
|
||||
echo "npm test \\&\\& npm run lint"
|
||||
;;
|
||||
*)
|
||||
echo "# Add commands for $lang"
|
||||
;;
|
||||
esac
|
||||
}
|
||||
|
||||
get_language_conventions() {
|
||||
local lang="$1"
|
||||
echo "$lang: Follow standard conventions"
|
||||
}
|
||||
|
||||
create_new_agent_file() {
|
||||
local target_file="$1"
|
||||
local temp_file="$2"
|
||||
local project_name="$3"
|
||||
local current_date="$4"
|
||||
|
||||
if [[ ! -f "$TEMPLATE_FILE" ]]; then
|
||||
log_error "Template not found at $TEMPLATE_FILE"
|
||||
return 1
|
||||
fi
|
||||
|
||||
if [[ ! -r "$TEMPLATE_FILE" ]]; then
|
||||
log_error "Template file is not readable: $TEMPLATE_FILE"
|
||||
return 1
|
||||
fi
|
||||
|
||||
log_info "Creating new agent context file from template..."
|
||||
|
||||
if ! cp "$TEMPLATE_FILE" "$temp_file"; then
|
||||
log_error "Failed to copy template file"
|
||||
return 1
|
||||
fi
|
||||
|
||||
# Replace template placeholders
|
||||
local project_structure
|
||||
project_structure=$(get_project_structure "$NEW_PROJECT_TYPE")
|
||||
|
||||
local commands
|
||||
commands=$(get_commands_for_language "$NEW_LANG")
|
||||
|
||||
local language_conventions
|
||||
language_conventions=$(get_language_conventions "$NEW_LANG")
|
||||
|
||||
# Perform substitutions with error checking using safer approach
|
||||
# Escape special characters for sed by using a different delimiter or escaping
|
||||
local escaped_lang=$(printf '%s\n' "$NEW_LANG" | sed 's/[\[\.*^$()+{}|]/\\&/g')
|
||||
local escaped_framework=$(printf '%s\n' "$NEW_FRAMEWORK" | sed 's/[\[\.*^$()+{}|]/\\&/g')
|
||||
local escaped_branch=$(printf '%s\n' "$CURRENT_BRANCH" | sed 's/[\[\.*^$()+{}|]/\\&/g')
|
||||
|
||||
# Build technology stack and recent change strings conditionally
|
||||
local tech_stack
|
||||
if [[ -n "$escaped_lang" && -n "$escaped_framework" ]]; then
|
||||
tech_stack="- $escaped_lang + $escaped_framework ($escaped_branch)"
|
||||
elif [[ -n "$escaped_lang" ]]; then
|
||||
tech_stack="- $escaped_lang ($escaped_branch)"
|
||||
elif [[ -n "$escaped_framework" ]]; then
|
||||
tech_stack="- $escaped_framework ($escaped_branch)"
|
||||
else
|
||||
tech_stack="- ($escaped_branch)"
|
||||
fi
|
||||
|
||||
local recent_change
|
||||
if [[ -n "$escaped_lang" && -n "$escaped_framework" ]]; then
|
||||
recent_change="- $escaped_branch: Added $escaped_lang + $escaped_framework"
|
||||
elif [[ -n "$escaped_lang" ]]; then
|
||||
recent_change="- $escaped_branch: Added $escaped_lang"
|
||||
elif [[ -n "$escaped_framework" ]]; then
|
||||
recent_change="- $escaped_branch: Added $escaped_framework"
|
||||
else
|
||||
recent_change="- $escaped_branch: Added"
|
||||
fi
|
||||
|
||||
local substitutions=(
|
||||
"s|\[PROJECT NAME\]|$project_name|"
|
||||
"s|\[DATE\]|$current_date|"
|
||||
"s|\[EXTRACTED FROM ALL PLAN.MD FILES\]|$tech_stack|"
|
||||
"s|\[ACTUAL STRUCTURE FROM PLANS\]|$project_structure|g"
|
||||
"s|\[ONLY COMMANDS FOR ACTIVE TECHNOLOGIES\]|$commands|"
|
||||
"s|\[LANGUAGE-SPECIFIC, ONLY FOR LANGUAGES IN USE\]|$language_conventions|"
|
||||
"s|\[LAST 3 FEATURES AND WHAT THEY ADDED\]|$recent_change|"
|
||||
)
|
||||
|
||||
for substitution in "${substitutions[@]}"; do
|
||||
if ! sed -i.bak -e "$substitution" "$temp_file"; then
|
||||
log_error "Failed to perform substitution: $substitution"
|
||||
rm -f "$temp_file" "$temp_file.bak"
|
||||
return 1
|
||||
fi
|
||||
done
|
||||
|
||||
# Convert \n sequences to actual newlines
|
||||
newline=$(printf '\n')
|
||||
sed -i.bak2 "s/\\\\n/${newline}/g" "$temp_file"
|
||||
|
||||
# Clean up backup files
|
||||
rm -f "$temp_file.bak" "$temp_file.bak2"
|
||||
|
||||
return 0
|
||||
}
|
||||
|
||||
|
||||
|
||||
|
||||
update_existing_agent_file() {
|
||||
local target_file="$1"
|
||||
local current_date="$2"
|
||||
|
||||
log_info "Updating existing agent context file..."
|
||||
|
||||
# Use a single temporary file for atomic update
|
||||
local temp_file
|
||||
temp_file=$(mktemp) || {
|
||||
log_error "Failed to create temporary file"
|
||||
return 1
|
||||
}
|
||||
|
||||
# Process the file in one pass
|
||||
local tech_stack=$(format_technology_stack "$NEW_LANG" "$NEW_FRAMEWORK")
|
||||
local new_tech_entries=()
|
||||
local new_change_entry=""
|
||||
|
||||
# Prepare new technology entries
|
||||
if [[ -n "$tech_stack" ]] && ! grep -q "$tech_stack" "$target_file"; then
|
||||
new_tech_entries+=("- $tech_stack ($CURRENT_BRANCH)")
|
||||
fi
|
||||
|
||||
if [[ -n "$NEW_DB" ]] && [[ "$NEW_DB" != "N/A" ]] && [[ "$NEW_DB" != "NEEDS CLARIFICATION" ]] && ! grep -q "$NEW_DB" "$target_file"; then
|
||||
new_tech_entries+=("- $NEW_DB ($CURRENT_BRANCH)")
|
||||
fi
|
||||
|
||||
# Prepare new change entry
|
||||
if [[ -n "$tech_stack" ]]; then
|
||||
new_change_entry="- $CURRENT_BRANCH: Added $tech_stack"
|
||||
elif [[ -n "$NEW_DB" ]] && [[ "$NEW_DB" != "N/A" ]] && [[ "$NEW_DB" != "NEEDS CLARIFICATION" ]]; then
|
||||
new_change_entry="- $CURRENT_BRANCH: Added $NEW_DB"
|
||||
fi
|
||||
|
||||
# Check if sections exist in the file
|
||||
local has_active_technologies=0
|
||||
local has_recent_changes=0
|
||||
|
||||
if grep -q "^## Active Technologies" "$target_file" 2>/dev/null; then
|
||||
has_active_technologies=1
|
||||
fi
|
||||
|
||||
if grep -q "^## Recent Changes" "$target_file" 2>/dev/null; then
|
||||
has_recent_changes=1
|
||||
fi
|
||||
|
||||
# Process file line by line
|
||||
local in_tech_section=false
|
||||
local in_changes_section=false
|
||||
local tech_entries_added=false
|
||||
local changes_entries_added=false
|
||||
local existing_changes_count=0
|
||||
local file_ended=false
|
||||
|
||||
while IFS= read -r line || [[ -n "$line" ]]; do
|
||||
# Handle Active Technologies section
|
||||
if [[ "$line" == "## Active Technologies" ]]; then
|
||||
echo "$line" >> "$temp_file"
|
||||
in_tech_section=true
|
||||
continue
|
||||
elif [[ $in_tech_section == true ]] && [[ "$line" =~ ^##[[:space:]] ]]; then
|
||||
# Add new tech entries before closing the section
|
||||
if [[ $tech_entries_added == false ]] && [[ ${#new_tech_entries[@]} -gt 0 ]]; then
|
||||
printf '%s\n' "${new_tech_entries[@]}" >> "$temp_file"
|
||||
tech_entries_added=true
|
||||
fi
|
||||
echo "$line" >> "$temp_file"
|
||||
in_tech_section=false
|
||||
continue
|
||||
elif [[ $in_tech_section == true ]] && [[ -z "$line" ]]; then
|
||||
# Add new tech entries before empty line in tech section
|
||||
if [[ $tech_entries_added == false ]] && [[ ${#new_tech_entries[@]} -gt 0 ]]; then
|
||||
printf '%s\n' "${new_tech_entries[@]}" >> "$temp_file"
|
||||
tech_entries_added=true
|
||||
fi
|
||||
echo "$line" >> "$temp_file"
|
||||
continue
|
||||
fi
|
||||
|
||||
# Handle Recent Changes section
|
||||
if [[ "$line" == "## Recent Changes" ]]; then
|
||||
echo "$line" >> "$temp_file"
|
||||
# Add new change entry right after the heading
|
||||
if [[ -n "$new_change_entry" ]]; then
|
||||
echo "$new_change_entry" >> "$temp_file"
|
||||
fi
|
||||
in_changes_section=true
|
||||
changes_entries_added=true
|
||||
continue
|
||||
elif [[ $in_changes_section == true ]] && [[ "$line" =~ ^##[[:space:]] ]]; then
|
||||
echo "$line" >> "$temp_file"
|
||||
in_changes_section=false
|
||||
continue
|
||||
elif [[ $in_changes_section == true ]] && [[ "$line" == "- "* ]]; then
|
||||
# Keep only first 2 existing changes
|
||||
if [[ $existing_changes_count -lt 2 ]]; then
|
||||
echo "$line" >> "$temp_file"
|
||||
((existing_changes_count++))
|
||||
fi
|
||||
continue
|
||||
fi
|
||||
|
||||
# Update timestamp
|
||||
if [[ "$line" =~ \*\*Last\ updated\*\*:.*[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9] ]]; then
|
||||
echo "$line" | sed "s/[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]/$current_date/" >> "$temp_file"
|
||||
else
|
||||
echo "$line" >> "$temp_file"
|
||||
fi
|
||||
done < "$target_file"
|
||||
|
||||
# Post-loop check: if we're still in the Active Technologies section and haven't added new entries
|
||||
if [[ $in_tech_section == true ]] && [[ $tech_entries_added == false ]] && [[ ${#new_tech_entries[@]} -gt 0 ]]; then
|
||||
printf '%s\n' "${new_tech_entries[@]}" >> "$temp_file"
|
||||
tech_entries_added=true
|
||||
fi
|
||||
|
||||
# If sections don't exist, add them at the end of the file
|
||||
if [[ $has_active_technologies -eq 0 ]] && [[ ${#new_tech_entries[@]} -gt 0 ]]; then
|
||||
echo "" >> "$temp_file"
|
||||
echo "## Active Technologies" >> "$temp_file"
|
||||
printf '%s\n' "${new_tech_entries[@]}" >> "$temp_file"
|
||||
tech_entries_added=true
|
||||
fi
|
||||
|
||||
if [[ $has_recent_changes -eq 0 ]] && [[ -n "$new_change_entry" ]]; then
|
||||
echo "" >> "$temp_file"
|
||||
echo "## Recent Changes" >> "$temp_file"
|
||||
echo "$new_change_entry" >> "$temp_file"
|
||||
changes_entries_added=true
|
||||
fi
|
||||
|
||||
# Move temp file to target atomically
|
||||
if ! mv "$temp_file" "$target_file"; then
|
||||
log_error "Failed to update target file"
|
||||
rm -f "$temp_file"
|
||||
return 1
|
||||
fi
|
||||
|
||||
return 0
|
||||
}
|
||||
#==============================================================================
|
||||
# Main Agent File Update Function
|
||||
#==============================================================================
|
||||
|
||||
update_agent_file() {
|
||||
local target_file="$1"
|
||||
local agent_name="$2"
|
||||
|
||||
if [[ -z "$target_file" ]] || [[ -z "$agent_name" ]]; then
|
||||
log_error "update_agent_file requires target_file and agent_name parameters"
|
||||
return 1
|
||||
fi
|
||||
|
||||
log_info "Updating $agent_name context file: $target_file"
|
||||
|
||||
local project_name
|
||||
project_name=$(basename "$REPO_ROOT")
|
||||
local current_date
|
||||
current_date=$(date +%Y-%m-%d)
|
||||
|
||||
# Create directory if it doesn't exist
|
||||
local target_dir
|
||||
target_dir=$(dirname "$target_file")
|
||||
if [[ ! -d "$target_dir" ]]; then
|
||||
if ! mkdir -p "$target_dir"; then
|
||||
log_error "Failed to create directory: $target_dir"
|
||||
return 1
|
||||
fi
|
||||
fi
|
||||
|
||||
if [[ ! -f "$target_file" ]]; then
|
||||
# Create new file from template
|
||||
local temp_file
|
||||
temp_file=$(mktemp) || {
|
||||
log_error "Failed to create temporary file"
|
||||
return 1
|
||||
}
|
||||
|
||||
if create_new_agent_file "$target_file" "$temp_file" "$project_name" "$current_date"; then
|
||||
if mv "$temp_file" "$target_file"; then
|
||||
log_success "Created new $agent_name context file"
|
||||
else
|
||||
log_error "Failed to move temporary file to $target_file"
|
||||
rm -f "$temp_file"
|
||||
return 1
|
||||
fi
|
||||
else
|
||||
log_error "Failed to create new agent file"
|
||||
rm -f "$temp_file"
|
||||
return 1
|
||||
fi
|
||||
else
|
||||
# Update existing file
|
||||
if [[ ! -r "$target_file" ]]; then
|
||||
log_error "Cannot read existing file: $target_file"
|
||||
return 1
|
||||
fi
|
||||
|
||||
if [[ ! -w "$target_file" ]]; then
|
||||
log_error "Cannot write to existing file: $target_file"
|
||||
return 1
|
||||
fi
|
||||
|
||||
if update_existing_agent_file "$target_file" "$current_date"; then
|
||||
log_success "Updated existing $agent_name context file"
|
||||
else
|
||||
log_error "Failed to update existing agent file"
|
||||
return 1
|
||||
fi
|
||||
fi
|
||||
|
||||
return 0
|
||||
}
|
||||
|
||||
#==============================================================================
|
||||
# Agent Selection and Processing
|
||||
#==============================================================================
|
||||
|
||||
update_specific_agent() {
|
||||
local agent_type="$1"
|
||||
|
||||
case "$agent_type" in
|
||||
claude)
|
||||
update_agent_file "$CLAUDE_FILE" "Claude Code"
|
||||
;;
|
||||
gemini)
|
||||
update_agent_file "$GEMINI_FILE" "Gemini CLI"
|
||||
;;
|
||||
copilot)
|
||||
update_agent_file "$COPILOT_FILE" "GitHub Copilot"
|
||||
;;
|
||||
cursor-agent)
|
||||
update_agent_file "$CURSOR_FILE" "Cursor IDE"
|
||||
;;
|
||||
qwen)
|
||||
update_agent_file "$QWEN_FILE" "Qwen Code"
|
||||
;;
|
||||
opencode)
|
||||
update_agent_file "$AGENTS_FILE" "opencode"
|
||||
;;
|
||||
codex)
|
||||
update_agent_file "$AGENTS_FILE" "Codex CLI"
|
||||
;;
|
||||
windsurf)
|
||||
update_agent_file "$WINDSURF_FILE" "Windsurf"
|
||||
;;
|
||||
kilocode)
|
||||
update_agent_file "$KILOCODE_FILE" "Kilo Code"
|
||||
;;
|
||||
auggie)
|
||||
update_agent_file "$AUGGIE_FILE" "Auggie CLI"
|
||||
;;
|
||||
roo)
|
||||
update_agent_file "$ROO_FILE" "Roo Code"
|
||||
;;
|
||||
codebuddy)
|
||||
update_agent_file "$CODEBUDDY_FILE" "CodeBuddy CLI"
|
||||
;;
|
||||
amp)
|
||||
update_agent_file "$AMP_FILE" "Amp"
|
||||
;;
|
||||
shai)
|
||||
update_agent_file "$SHAI_FILE" "SHAI"
|
||||
;;
|
||||
q)
|
||||
update_agent_file "$Q_FILE" "Amazon Q Developer CLI"
|
||||
;;
|
||||
*)
|
||||
log_error "Unknown agent type '$agent_type'"
|
||||
log_error "Expected: claude|gemini|copilot|cursor-agent|qwen|opencode|codex|windsurf|kilocode|auggie|roo|amp|shai|q"
|
||||
exit 1
|
||||
;;
|
||||
esac
|
||||
}
|
||||
|
||||
update_all_existing_agents() {
|
||||
local found_agent=false
|
||||
|
||||
# Check each possible agent file and update if it exists
|
||||
if [[ -f "$CLAUDE_FILE" ]]; then
|
||||
update_agent_file "$CLAUDE_FILE" "Claude Code"
|
||||
found_agent=true
|
||||
fi
|
||||
|
||||
if [[ -f "$GEMINI_FILE" ]]; then
|
||||
update_agent_file "$GEMINI_FILE" "Gemini CLI"
|
||||
found_agent=true
|
||||
fi
|
||||
|
||||
if [[ -f "$COPILOT_FILE" ]]; then
|
||||
update_agent_file "$COPILOT_FILE" "GitHub Copilot"
|
||||
found_agent=true
|
||||
fi
|
||||
|
||||
if [[ -f "$CURSOR_FILE" ]]; then
|
||||
update_agent_file "$CURSOR_FILE" "Cursor IDE"
|
||||
found_agent=true
|
||||
fi
|
||||
|
||||
if [[ -f "$QWEN_FILE" ]]; then
|
||||
update_agent_file "$QWEN_FILE" "Qwen Code"
|
||||
found_agent=true
|
||||
fi
|
||||
|
||||
if [[ -f "$AGENTS_FILE" ]]; then
|
||||
update_agent_file "$AGENTS_FILE" "Codex/opencode"
|
||||
found_agent=true
|
||||
fi
|
||||
|
||||
if [[ -f "$WINDSURF_FILE" ]]; then
|
||||
update_agent_file "$WINDSURF_FILE" "Windsurf"
|
||||
found_agent=true
|
||||
fi
|
||||
|
||||
if [[ -f "$KILOCODE_FILE" ]]; then
|
||||
update_agent_file "$KILOCODE_FILE" "Kilo Code"
|
||||
found_agent=true
|
||||
fi
|
||||
|
||||
if [[ -f "$AUGGIE_FILE" ]]; then
|
||||
update_agent_file "$AUGGIE_FILE" "Auggie CLI"
|
||||
found_agent=true
|
||||
fi
|
||||
|
||||
if [[ -f "$ROO_FILE" ]]; then
|
||||
update_agent_file "$ROO_FILE" "Roo Code"
|
||||
found_agent=true
|
||||
fi
|
||||
|
||||
if [[ -f "$CODEBUDDY_FILE" ]]; then
|
||||
update_agent_file "$CODEBUDDY_FILE" "CodeBuddy CLI"
|
||||
found_agent=true
|
||||
fi
|
||||
|
||||
if [[ -f "$SHAI_FILE" ]]; then
|
||||
update_agent_file "$SHAI_FILE" "SHAI"
|
||||
found_agent=true
|
||||
fi
|
||||
|
||||
if [[ -f "$Q_FILE" ]]; then
|
||||
update_agent_file "$Q_FILE" "Amazon Q Developer CLI"
|
||||
found_agent=true
|
||||
fi
|
||||
|
||||
# If no agent files exist, create a default Claude file
|
||||
if [[ "$found_agent" == false ]]; then
|
||||
log_info "No existing agent files found, creating default Claude file..."
|
||||
update_agent_file "$CLAUDE_FILE" "Claude Code"
|
||||
fi
|
||||
}
|
||||
print_summary() {
|
||||
echo
|
||||
log_info "Summary of changes:"
|
||||
|
||||
if [[ -n "$NEW_LANG" ]]; then
|
||||
echo " - Added language: $NEW_LANG"
|
||||
fi
|
||||
|
||||
if [[ -n "$NEW_FRAMEWORK" ]]; then
|
||||
echo " - Added framework: $NEW_FRAMEWORK"
|
||||
fi
|
||||
|
||||
if [[ -n "$NEW_DB" ]] && [[ "$NEW_DB" != "N/A" ]]; then
|
||||
echo " - Added database: $NEW_DB"
|
||||
fi
|
||||
|
||||
echo
|
||||
|
||||
log_info "Usage: $0 [claude|gemini|copilot|cursor-agent|qwen|opencode|codex|windsurf|kilocode|auggie|codebuddy|shai|q]"
|
||||
}
|
||||
|
||||
#==============================================================================
|
||||
# Main Execution
|
||||
#==============================================================================
|
||||
|
||||
main() {
|
||||
# Validate environment before proceeding
|
||||
validate_environment
|
||||
|
||||
log_info "=== Updating agent context files for feature $CURRENT_BRANCH ==="
|
||||
|
||||
# Parse the plan file to extract project information
|
||||
if ! parse_plan_data "$NEW_PLAN"; then
|
||||
log_error "Failed to parse plan data"
|
||||
exit 1
|
||||
fi
|
||||
|
||||
# Process based on agent type argument
|
||||
local success=true
|
||||
|
||||
if [[ -z "$AGENT_TYPE" ]]; then
|
||||
# No specific agent provided - update all existing agent files
|
||||
log_info "No agent specified, updating all existing agent files..."
|
||||
if ! update_all_existing_agents; then
|
||||
success=false
|
||||
fi
|
||||
else
|
||||
# Specific agent provided - update only that agent
|
||||
log_info "Updating specific agent: $AGENT_TYPE"
|
||||
if ! update_specific_agent "$AGENT_TYPE"; then
|
||||
success=false
|
||||
fi
|
||||
fi
|
||||
|
||||
# Print summary
|
||||
print_summary
|
||||
|
||||
if [[ "$success" == true ]]; then
|
||||
log_success "Agent context update completed successfully"
|
||||
exit 0
|
||||
else
|
||||
log_error "Agent context update completed with errors"
|
||||
exit 1
|
||||
fi
|
||||
}
|
||||
|
||||
# Execute main function if script is run directly
|
||||
if [[ "${BASH_SOURCE[0]}" == "${0}" ]]; then
|
||||
main "$@"
|
||||
fi
|
||||
|
||||
|
|
@ -0,0 +1,28 @@
|
|||
# [PROJECT NAME] Development Guidelines
|
||||
|
||||
Auto-generated from all feature plans. Last updated: [DATE]
|
||||
|
||||
## Active Technologies
|
||||
|
||||
[EXTRACTED FROM ALL PLAN.MD FILES]
|
||||
|
||||
## Project Structure
|
||||
|
||||
```text
|
||||
[ACTUAL STRUCTURE FROM PLANS]
|
||||
```
|
||||
|
||||
## Commands
|
||||
|
||||
[ONLY COMMANDS FOR ACTIVE TECHNOLOGIES]
|
||||
|
||||
## Code Style
|
||||
|
||||
[LANGUAGE-SPECIFIC, ONLY FOR LANGUAGES IN USE]
|
||||
|
||||
## Recent Changes
|
||||
|
||||
[LAST 3 FEATURES AND WHAT THEY ADDED]
|
||||
|
||||
<!-- MANUAL ADDITIONS START -->
|
||||
<!-- MANUAL ADDITIONS END -->
|
||||
|
|
@ -0,0 +1,40 @@
|
|||
# [CHECKLIST TYPE] Checklist: [FEATURE NAME]
|
||||
|
||||
**Purpose**: [Brief description of what this checklist covers]
|
||||
**Created**: [DATE]
|
||||
**Feature**: [Link to spec.md or relevant documentation]
|
||||
|
||||
**Note**: This checklist is generated by the `/speckit.checklist` command based on feature context and requirements.
|
||||
|
||||
<!--
|
||||
============================================================================
|
||||
IMPORTANT: The checklist items below are SAMPLE ITEMS for illustration only.
|
||||
|
||||
The /speckit.checklist command MUST replace these with actual items based on:
|
||||
- User's specific checklist request
|
||||
- Feature requirements from spec.md
|
||||
- Technical context from plan.md
|
||||
- Implementation details from tasks.md
|
||||
|
||||
DO NOT keep these sample items in the generated checklist file.
|
||||
============================================================================
|
||||
-->
|
||||
|
||||
## [Category 1]
|
||||
|
||||
- [ ] CHK001 First checklist item with clear action
|
||||
- [ ] CHK002 Second checklist item
|
||||
- [ ] CHK003 Third checklist item
|
||||
|
||||
## [Category 2]
|
||||
|
||||
- [ ] CHK004 Another category item
|
||||
- [ ] CHK005 Item with specific criteria
|
||||
- [ ] CHK006 Final item in this category
|
||||
|
||||
## Notes
|
||||
|
||||
- Check items off as completed: `[x]`
|
||||
- Add comments or findings inline
|
||||
- Link to relevant resources or documentation
|
||||
- Items are numbered sequentially for easy reference
|
||||
|
|
@ -0,0 +1,104 @@
|
|||
# Implementation Plan: [FEATURE]
|
||||
|
||||
**Branch**: `[###-feature-name]` | **Date**: [DATE] | **Spec**: [link]
|
||||
**Input**: Feature specification from `/specs/[###-feature-name]/spec.md`
|
||||
|
||||
**Note**: This template is filled in by the `/speckit.plan` command. See `.specify/templates/commands/plan.md` for the execution workflow.
|
||||
|
||||
## Summary
|
||||
|
||||
[Extract from feature spec: primary requirement + technical approach from research]
|
||||
|
||||
## Technical Context
|
||||
|
||||
<!--
|
||||
ACTION REQUIRED: Replace the content in this section with the technical details
|
||||
for the project. The structure here is presented in advisory capacity to guide
|
||||
the iteration process.
|
||||
-->
|
||||
|
||||
**Language/Version**: [e.g., Python 3.11, Swift 5.9, Rust 1.75 or NEEDS CLARIFICATION]
|
||||
**Primary Dependencies**: [e.g., FastAPI, UIKit, LLVM or NEEDS CLARIFICATION]
|
||||
**Storage**: [if applicable, e.g., PostgreSQL, CoreData, files or N/A]
|
||||
**Testing**: [e.g., pytest, XCTest, cargo test or NEEDS CLARIFICATION]
|
||||
**Target Platform**: [e.g., Linux server, iOS 15+, WASM or NEEDS CLARIFICATION]
|
||||
**Project Type**: [single/web/mobile - determines source structure]
|
||||
**Performance Goals**: [domain-specific, e.g., 1000 req/s, 10k lines/sec, 60 fps or NEEDS CLARIFICATION]
|
||||
**Constraints**: [domain-specific, e.g., <200ms p95, <100MB memory, offline-capable or NEEDS CLARIFICATION]
|
||||
**Scale/Scope**: [domain-specific, e.g., 10k users, 1M LOC, 50 screens or NEEDS CLARIFICATION]
|
||||
|
||||
## Constitution Check
|
||||
|
||||
*GATE: Must pass before Phase 0 research. Re-check after Phase 1 design.*
|
||||
|
||||
[Gates determined based on constitution file]
|
||||
|
||||
## Project Structure
|
||||
|
||||
### Documentation (this feature)
|
||||
|
||||
```text
|
||||
specs/[###-feature]/
|
||||
├── plan.md # This file (/speckit.plan command output)
|
||||
├── research.md # Phase 0 output (/speckit.plan command)
|
||||
├── data-model.md # Phase 1 output (/speckit.plan command)
|
||||
├── quickstart.md # Phase 1 output (/speckit.plan command)
|
||||
├── contracts/ # Phase 1 output (/speckit.plan command)
|
||||
└── tasks.md # Phase 2 output (/speckit.tasks command - NOT created by /speckit.plan)
|
||||
```
|
||||
|
||||
### Source Code (repository root)
|
||||
<!--
|
||||
ACTION REQUIRED: Replace the placeholder tree below with the concrete layout
|
||||
for this feature. Delete unused options and expand the chosen structure with
|
||||
real paths (e.g., apps/admin, packages/something). The delivered plan must
|
||||
not include Option labels.
|
||||
-->
|
||||
|
||||
```text
|
||||
# [REMOVE IF UNUSED] Option 1: Single project (DEFAULT)
|
||||
src/
|
||||
├── models/
|
||||
├── services/
|
||||
├── cli/
|
||||
└── lib/
|
||||
|
||||
tests/
|
||||
├── contract/
|
||||
├── integration/
|
||||
└── unit/
|
||||
|
||||
# [REMOVE IF UNUSED] Option 2: Web application (when "frontend" + "backend" detected)
|
||||
backend/
|
||||
├── src/
|
||||
│ ├── models/
|
||||
│ ├── services/
|
||||
│ └── api/
|
||||
└── tests/
|
||||
|
||||
frontend/
|
||||
├── src/
|
||||
│ ├── components/
|
||||
│ ├── pages/
|
||||
│ └── services/
|
||||
└── tests/
|
||||
|
||||
# [REMOVE IF UNUSED] Option 3: Mobile + API (when "iOS/Android" detected)
|
||||
api/
|
||||
└── [same as backend above]
|
||||
|
||||
ios/ or android/
|
||||
└── [platform-specific structure: feature modules, UI flows, platform tests]
|
||||
```
|
||||
|
||||
**Structure Decision**: [Document the selected structure and reference the real
|
||||
directories captured above]
|
||||
|
||||
## Complexity Tracking
|
||||
|
||||
> **Fill ONLY if Constitution Check has violations that must be justified**
|
||||
|
||||
| Violation | Why Needed | Simpler Alternative Rejected Because |
|
||||
|-----------|------------|-------------------------------------|
|
||||
| [e.g., 4th project] | [current need] | [why 3 projects insufficient] |
|
||||
| [e.g., Repository pattern] | [specific problem] | [why direct DB access insufficient] |
|
||||
|
|
@ -0,0 +1,115 @@
|
|||
# Feature Specification: [FEATURE NAME]
|
||||
|
||||
**Feature Branch**: `[###-feature-name]`
|
||||
**Created**: [DATE]
|
||||
**Status**: Draft
|
||||
**Input**: User description: "$ARGUMENTS"
|
||||
|
||||
## User Scenarios & Testing *(mandatory)*
|
||||
|
||||
<!--
|
||||
IMPORTANT: User stories should be PRIORITIZED as user journeys ordered by importance.
|
||||
Each user story/journey must be INDEPENDENTLY TESTABLE - meaning if you implement just ONE of them,
|
||||
you should still have a viable MVP (Minimum Viable Product) that delivers value.
|
||||
|
||||
Assign priorities (P1, P2, P3, etc.) to each story, where P1 is the most critical.
|
||||
Think of each story as a standalone slice of functionality that can be:
|
||||
- Developed independently
|
||||
- Tested independently
|
||||
- Deployed independently
|
||||
- Demonstrated to users independently
|
||||
-->
|
||||
|
||||
### User Story 1 - [Brief Title] (Priority: P1)
|
||||
|
||||
[Describe this user journey in plain language]
|
||||
|
||||
**Why this priority**: [Explain the value and why it has this priority level]
|
||||
|
||||
**Independent Test**: [Describe how this can be tested independently - e.g., "Can be fully tested by [specific action] and delivers [specific value]"]
|
||||
|
||||
**Acceptance Scenarios**:
|
||||
|
||||
1. **Given** [initial state], **When** [action], **Then** [expected outcome]
|
||||
2. **Given** [initial state], **When** [action], **Then** [expected outcome]
|
||||
|
||||
---
|
||||
|
||||
### User Story 2 - [Brief Title] (Priority: P2)
|
||||
|
||||
[Describe this user journey in plain language]
|
||||
|
||||
**Why this priority**: [Explain the value and why it has this priority level]
|
||||
|
||||
**Independent Test**: [Describe how this can be tested independently]
|
||||
|
||||
**Acceptance Scenarios**:
|
||||
|
||||
1. **Given** [initial state], **When** [action], **Then** [expected outcome]
|
||||
|
||||
---
|
||||
|
||||
### User Story 3 - [Brief Title] (Priority: P3)
|
||||
|
||||
[Describe this user journey in plain language]
|
||||
|
||||
**Why this priority**: [Explain the value and why it has this priority level]
|
||||
|
||||
**Independent Test**: [Describe how this can be tested independently]
|
||||
|
||||
**Acceptance Scenarios**:
|
||||
|
||||
1. **Given** [initial state], **When** [action], **Then** [expected outcome]
|
||||
|
||||
---
|
||||
|
||||
[Add more user stories as needed, each with an assigned priority]
|
||||
|
||||
### Edge Cases
|
||||
|
||||
<!--
|
||||
ACTION REQUIRED: The content in this section represents placeholders.
|
||||
Fill them out with the right edge cases.
|
||||
-->
|
||||
|
||||
- What happens when [boundary condition]?
|
||||
- How does system handle [error scenario]?
|
||||
|
||||
## Requirements *(mandatory)*
|
||||
|
||||
<!--
|
||||
ACTION REQUIRED: The content in this section represents placeholders.
|
||||
Fill them out with the right functional requirements.
|
||||
-->
|
||||
|
||||
### Functional Requirements
|
||||
|
||||
- **FR-001**: System MUST [specific capability, e.g., "allow users to create accounts"]
|
||||
- **FR-002**: System MUST [specific capability, e.g., "validate email addresses"]
|
||||
- **FR-003**: Users MUST be able to [key interaction, e.g., "reset their password"]
|
||||
- **FR-004**: System MUST [data requirement, e.g., "persist user preferences"]
|
||||
- **FR-005**: System MUST [behavior, e.g., "log all security events"]
|
||||
|
||||
*Example of marking unclear requirements:*
|
||||
|
||||
- **FR-006**: System MUST authenticate users via [NEEDS CLARIFICATION: auth method not specified - email/password, SSO, OAuth?]
|
||||
- **FR-007**: System MUST retain user data for [NEEDS CLARIFICATION: retention period not specified]
|
||||
|
||||
### Key Entities *(include if feature involves data)*
|
||||
|
||||
- **[Entity 1]**: [What it represents, key attributes without implementation]
|
||||
- **[Entity 2]**: [What it represents, relationships to other entities]
|
||||
|
||||
## Success Criteria *(mandatory)*
|
||||
|
||||
<!--
|
||||
ACTION REQUIRED: Define measurable success criteria.
|
||||
These must be technology-agnostic and measurable.
|
||||
-->
|
||||
|
||||
### Measurable Outcomes
|
||||
|
||||
- **SC-001**: [Measurable metric, e.g., "Users can complete account creation in under 2 minutes"]
|
||||
- **SC-002**: [Measurable metric, e.g., "System handles 1000 concurrent users without degradation"]
|
||||
- **SC-003**: [User satisfaction metric, e.g., "90% of users successfully complete primary task on first attempt"]
|
||||
- **SC-004**: [Business metric, e.g., "Reduce support tickets related to [X] by 50%"]
|
||||
|
|
@ -0,0 +1,251 @@
|
|||
---
|
||||
|
||||
description: "Task list template for feature implementation"
|
||||
---
|
||||
|
||||
# Tasks: [FEATURE NAME]
|
||||
|
||||
**Input**: Design documents from `/specs/[###-feature-name]/`
|
||||
**Prerequisites**: plan.md (required), spec.md (required for user stories), research.md, data-model.md, contracts/
|
||||
|
||||
**Tests**: The examples below include test tasks. Tests are OPTIONAL - only include them if explicitly requested in the feature specification.
|
||||
|
||||
**Organization**: Tasks are grouped by user story to enable independent implementation and testing of each story.
|
||||
|
||||
## Format: `[ID] [P?] [Story] Description`
|
||||
|
||||
- **[P]**: Can run in parallel (different files, no dependencies)
|
||||
- **[Story]**: Which user story this task belongs to (e.g., US1, US2, US3)
|
||||
- Include exact file paths in descriptions
|
||||
|
||||
## Path Conventions
|
||||
|
||||
- **Single project**: `src/`, `tests/` at repository root
|
||||
- **Web app**: `backend/src/`, `frontend/src/`
|
||||
- **Mobile**: `api/src/`, `ios/src/` or `android/src/`
|
||||
- Paths shown below assume single project - adjust based on plan.md structure
|
||||
|
||||
<!--
|
||||
============================================================================
|
||||
IMPORTANT: The tasks below are SAMPLE TASKS for illustration purposes only.
|
||||
|
||||
The /speckit.tasks command MUST replace these with actual tasks based on:
|
||||
- User stories from spec.md (with their priorities P1, P2, P3...)
|
||||
- Feature requirements from plan.md
|
||||
- Entities from data-model.md
|
||||
- Endpoints from contracts/
|
||||
|
||||
Tasks MUST be organized by user story so each story can be:
|
||||
- Implemented independently
|
||||
- Tested independently
|
||||
- Delivered as an MVP increment
|
||||
|
||||
DO NOT keep these sample tasks in the generated tasks.md file.
|
||||
============================================================================
|
||||
-->
|
||||
|
||||
## Phase 1: Setup (Shared Infrastructure)
|
||||
|
||||
**Purpose**: Project initialization and basic structure
|
||||
|
||||
- [ ] T001 Create project structure per implementation plan
|
||||
- [ ] T002 Initialize [language] project with [framework] dependencies
|
||||
- [ ] T003 [P] Configure linting and formatting tools
|
||||
|
||||
---
|
||||
|
||||
## Phase 2: Foundational (Blocking Prerequisites)
|
||||
|
||||
**Purpose**: Core infrastructure that MUST be complete before ANY user story can be implemented
|
||||
|
||||
**⚠️ CRITICAL**: No user story work can begin until this phase is complete
|
||||
|
||||
Examples of foundational tasks (adjust based on your project):
|
||||
|
||||
- [ ] T004 Setup database schema and migrations framework
|
||||
- [ ] T005 [P] Implement authentication/authorization framework
|
||||
- [ ] T006 [P] Setup API routing and middleware structure
|
||||
- [ ] T007 Create base models/entities that all stories depend on
|
||||
- [ ] T008 Configure error handling and logging infrastructure
|
||||
- [ ] T009 Setup environment configuration management
|
||||
|
||||
**Checkpoint**: Foundation ready - user story implementation can now begin in parallel
|
||||
|
||||
---
|
||||
|
||||
## Phase 3: User Story 1 - [Title] (Priority: P1) 🎯 MVP
|
||||
|
||||
**Goal**: [Brief description of what this story delivers]
|
||||
|
||||
**Independent Test**: [How to verify this story works on its own]
|
||||
|
||||
### Tests for User Story 1 (OPTIONAL - only if tests requested) ⚠️
|
||||
|
||||
> **NOTE: Write these tests FIRST, ensure they FAIL before implementation**
|
||||
|
||||
- [ ] T010 [P] [US1] Contract test for [endpoint] in tests/contract/test_[name].py
|
||||
- [ ] T011 [P] [US1] Integration test for [user journey] in tests/integration/test_[name].py
|
||||
|
||||
### Implementation for User Story 1
|
||||
|
||||
- [ ] T012 [P] [US1] Create [Entity1] model in src/models/[entity1].py
|
||||
- [ ] T013 [P] [US1] Create [Entity2] model in src/models/[entity2].py
|
||||
- [ ] T014 [US1] Implement [Service] in src/services/[service].py (depends on T012, T013)
|
||||
- [ ] T015 [US1] Implement [endpoint/feature] in src/[location]/[file].py
|
||||
- [ ] T016 [US1] Add validation and error handling
|
||||
- [ ] T017 [US1] Add logging for user story 1 operations
|
||||
|
||||
**Checkpoint**: At this point, User Story 1 should be fully functional and testable independently
|
||||
|
||||
---
|
||||
|
||||
## Phase 4: User Story 2 - [Title] (Priority: P2)
|
||||
|
||||
**Goal**: [Brief description of what this story delivers]
|
||||
|
||||
**Independent Test**: [How to verify this story works on its own]
|
||||
|
||||
### Tests for User Story 2 (OPTIONAL - only if tests requested) ⚠️
|
||||
|
||||
- [ ] T018 [P] [US2] Contract test for [endpoint] in tests/contract/test_[name].py
|
||||
- [ ] T019 [P] [US2] Integration test for [user journey] in tests/integration/test_[name].py
|
||||
|
||||
### Implementation for User Story 2
|
||||
|
||||
- [ ] T020 [P] [US2] Create [Entity] model in src/models/[entity].py
|
||||
- [ ] T021 [US2] Implement [Service] in src/services/[service].py
|
||||
- [ ] T022 [US2] Implement [endpoint/feature] in src/[location]/[file].py
|
||||
- [ ] T023 [US2] Integrate with User Story 1 components (if needed)
|
||||
|
||||
**Checkpoint**: At this point, User Stories 1 AND 2 should both work independently
|
||||
|
||||
---
|
||||
|
||||
## Phase 5: User Story 3 - [Title] (Priority: P3)
|
||||
|
||||
**Goal**: [Brief description of what this story delivers]
|
||||
|
||||
**Independent Test**: [How to verify this story works on its own]
|
||||
|
||||
### Tests for User Story 3 (OPTIONAL - only if tests requested) ⚠️
|
||||
|
||||
- [ ] T024 [P] [US3] Contract test for [endpoint] in tests/contract/test_[name].py
|
||||
- [ ] T025 [P] [US3] Integration test for [user journey] in tests/integration/test_[name].py
|
||||
|
||||
### Implementation for User Story 3
|
||||
|
||||
- [ ] T026 [P] [US3] Create [Entity] model in src/models/[entity].py
|
||||
- [ ] T027 [US3] Implement [Service] in src/services/[service].py
|
||||
- [ ] T028 [US3] Implement [endpoint/feature] in src/[location]/[file].py
|
||||
|
||||
**Checkpoint**: All user stories should now be independently functional
|
||||
|
||||
---
|
||||
|
||||
[Add more user story phases as needed, following the same pattern]
|
||||
|
||||
---
|
||||
|
||||
## Phase N: Polish & Cross-Cutting Concerns
|
||||
|
||||
**Purpose**: Improvements that affect multiple user stories
|
||||
|
||||
- [ ] TXXX [P] Documentation updates in docs/
|
||||
- [ ] TXXX Code cleanup and refactoring
|
||||
- [ ] TXXX Performance optimization across all stories
|
||||
- [ ] TXXX [P] Additional unit tests (if requested) in tests/unit/
|
||||
- [ ] TXXX Security hardening
|
||||
- [ ] TXXX Run quickstart.md validation
|
||||
|
||||
---
|
||||
|
||||
## Dependencies & Execution Order
|
||||
|
||||
### Phase Dependencies
|
||||
|
||||
- **Setup (Phase 1)**: No dependencies - can start immediately
|
||||
- **Foundational (Phase 2)**: Depends on Setup completion - BLOCKS all user stories
|
||||
- **User Stories (Phase 3+)**: All depend on Foundational phase completion
|
||||
- User stories can then proceed in parallel (if staffed)
|
||||
- Or sequentially in priority order (P1 → P2 → P3)
|
||||
- **Polish (Final Phase)**: Depends on all desired user stories being complete
|
||||
|
||||
### User Story Dependencies
|
||||
|
||||
- **User Story 1 (P1)**: Can start after Foundational (Phase 2) - No dependencies on other stories
|
||||
- **User Story 2 (P2)**: Can start after Foundational (Phase 2) - May integrate with US1 but should be independently testable
|
||||
- **User Story 3 (P3)**: Can start after Foundational (Phase 2) - May integrate with US1/US2 but should be independently testable
|
||||
|
||||
### Within Each User Story
|
||||
|
||||
- Tests (if included) MUST be written and FAIL before implementation
|
||||
- Models before services
|
||||
- Services before endpoints
|
||||
- Core implementation before integration
|
||||
- Story complete before moving to next priority
|
||||
|
||||
### Parallel Opportunities
|
||||
|
||||
- All Setup tasks marked [P] can run in parallel
|
||||
- All Foundational tasks marked [P] can run in parallel (within Phase 2)
|
||||
- Once Foundational phase completes, all user stories can start in parallel (if team capacity allows)
|
||||
- All tests for a user story marked [P] can run in parallel
|
||||
- Models within a story marked [P] can run in parallel
|
||||
- Different user stories can be worked on in parallel by different team members
|
||||
|
||||
---
|
||||
|
||||
## Parallel Example: User Story 1
|
||||
|
||||
```bash
|
||||
# Launch all tests for User Story 1 together (if tests requested):
|
||||
Task: "Contract test for [endpoint] in tests/contract/test_[name].py"
|
||||
Task: "Integration test for [user journey] in tests/integration/test_[name].py"
|
||||
|
||||
# Launch all models for User Story 1 together:
|
||||
Task: "Create [Entity1] model in src/models/[entity1].py"
|
||||
Task: "Create [Entity2] model in src/models/[entity2].py"
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Implementation Strategy
|
||||
|
||||
### MVP First (User Story 1 Only)
|
||||
|
||||
1. Complete Phase 1: Setup
|
||||
2. Complete Phase 2: Foundational (CRITICAL - blocks all stories)
|
||||
3. Complete Phase 3: User Story 1
|
||||
4. **STOP and VALIDATE**: Test User Story 1 independently
|
||||
5. Deploy/demo if ready
|
||||
|
||||
### Incremental Delivery
|
||||
|
||||
1. Complete Setup + Foundational → Foundation ready
|
||||
2. Add User Story 1 → Test independently → Deploy/Demo (MVP!)
|
||||
3. Add User Story 2 → Test independently → Deploy/Demo
|
||||
4. Add User Story 3 → Test independently → Deploy/Demo
|
||||
5. Each story adds value without breaking previous stories
|
||||
|
||||
### Parallel Team Strategy
|
||||
|
||||
With multiple developers:
|
||||
|
||||
1. Team completes Setup + Foundational together
|
||||
2. Once Foundational is done:
|
||||
- Developer A: User Story 1
|
||||
- Developer B: User Story 2
|
||||
- Developer C: User Story 3
|
||||
3. Stories complete and integrate independently
|
||||
|
||||
---
|
||||
|
||||
## Notes
|
||||
|
||||
- [P] tasks = different files, no dependencies
|
||||
- [Story] label maps task to specific user story for traceability
|
||||
- Each user story should be independently completable and testable
|
||||
- Verify tests fail before implementing
|
||||
- Commit after each task or logical group
|
||||
- Stop at any checkpoint to validate story independently
|
||||
- Avoid: vague tasks, same file conflicts, cross-story dependencies that break independence
|
||||
|
|
@ -0,0 +1,29 @@
|
|||
# prosberry_produkcija Development Guidelines
|
||||
|
||||
Auto-generated from all feature plans. Last updated: 2025-11-17
|
||||
|
||||
## Active Technologies
|
||||
|
||||
- Bash/Shell (for `posodobi_blog.sh`), HTML, CSS, JavaScript (for existing `main.js`). + `jq` (for `posodobi_blog.sh`). (001-add-blog)
|
||||
|
||||
## Project Structure
|
||||
|
||||
```text
|
||||
src/
|
||||
tests/
|
||||
```
|
||||
|
||||
## Commands
|
||||
|
||||
npm test && npm run lint
|
||||
|
||||
## Code Style
|
||||
|
||||
Bash/Shell (for `posodobi_blog.sh`), HTML, CSS, JavaScript (for existing `main.js`).: Follow standard conventions
|
||||
|
||||
## Recent Changes
|
||||
|
||||
- 001-add-blog: Added Bash/Shell (for `posodobi_blog.sh`), HTML, CSS, JavaScript (for existing `main.js`). + `jq` (for `posodobi_blog.sh`).
|
||||
|
||||
<!-- MANUAL ADDITIONS START -->
|
||||
<!-- MANUAL ADDITIONS END -->
|
||||
|
|
@ -0,0 +1,115 @@
|
|||
## 1. Opis Projekta
|
||||
|
||||
**Prosberry.si** je profesionalna spletna stran za podjetje **PROSBERRY, Amra Kurešepi Zulji s.p.** Stran služi kot digitalna vizitka in informacijska točka za storitve, ki jih podjetje ponuja. Glavni cilj projekta je predstaviti strokovnost in osebni pristop Amre Kurešepi Zulji na področju jezikovnega izobraževanja in medkulturnega posredovanja.
|
||||
|
||||
Spletna stran je zasnovana kot statična stran (HTML, CSS, JavaScript), kar zagotavlja hitro nalaganje in enostavno vzdrževanje. Za funkcionalnost kontaktnega obrazca se uporablja PHP. Projekt vključuje tudi nabor skript za avtomatizacijo (Python in Shell), ki poenostavljajo procese, kot so optimizacija slik in posodabljanje ponavljajočih se elementov (glava, noga).
|
||||
|
||||
### Glavne funkcionalnosti in vsebine:
|
||||
- **Predstavitev storitev:** Podroben opis jezikovnih tečajev (angleščina, albanščina, slovenščina), medkulturnega posredovanja in specializiranih delavnic.
|
||||
- **Osebna predstavitev:** Stran "Kdo sem" z osebno zgodbo in kvalifikacijami izvajalke.
|
||||
- **Cenik in reference:** Pregled cen storitev in mnenja zadovoljnih strank.
|
||||
- **Kontaktni obrazec:** Enostaven način za pošiljanje povpraševanj.
|
||||
- **Pogosta vprašanja (FAQ):** Odgovori na najpogostejša vprašanja za lažje informiranje obiskovalcev.
|
||||
- **Odziven dizajn:** Stran je prilagojena za optimalen prikaz na različnih napravah (mobilni telefoni, tablice, namizni računalniki).
|
||||
|
||||
## 2. Struktura Projekta (Zemljevid)
|
||||
|
||||
```
|
||||
.
|
||||
├── assets
|
||||
│ ├── favicon
|
||||
│ │ └── site.webmanifest
|
||||
│ ├── images/
|
||||
│ └── pdf/
|
||||
├── cene-in-reference
|
||||
│ └── index.html
|
||||
├── cene-in-sodelovanja
|
||||
│ └── index.html
|
||||
├── css
|
||||
│ ├── animations.css
|
||||
│ └── style.css
|
||||
├── delavnice
|
||||
│ └── index.html
|
||||
├── js
|
||||
│ └── main.js
|
||||
├── kdo-sem
|
||||
│ └── index.html
|
||||
├── kontakt
|
||||
│ ├── index.html
|
||||
│ └── process_form.php
|
||||
│── politika-zasebnosti
|
||||
│ └── index.html
|
||||
├── pogosta-vprasanja
|
||||
│ └── index.html
|
||||
├── ponudba
|
||||
│ └── index.html
|
||||
├── skupaj-za-vkljucevanje
|
||||
│ ├── delavnica-od-tujca-do-sosolca
|
||||
│ │ └── index.html
|
||||
│ ├── delavnica-sola-in-starsi
|
||||
│ │ └── index.html
|
||||
│ ├── delavnica-vrtec-novi-zacetki
|
||||
│ │ └── index.html
|
||||
│ ├── delavnica-zakaj-znati-slovensko
|
||||
│ │ └── index.html
|
||||
│ └── medkulturno-posredovanje
|
||||
│ └── index.html
|
||||
├── error_log
|
||||
├── footer-template.html
|
||||
├── header-template.html
|
||||
├── generate_responsive_images.py
|
||||
├── index.html
|
||||
├── minify_js.py
|
||||
├── optimize_images.py
|
||||
├── robots.txt
|
||||
├── sitemap.xml
|
||||
├── update-footer.sh
|
||||
└── update-menus.sh
|
||||
```
|
||||
|
||||
## 3. Opis Datotek in Map
|
||||
|
||||
### 📁 Korenske datoteke in mape
|
||||
|
||||
- **`index.html`**: Glavna vstopna stran (domača stran), ki pozdravi obiskovalca in na kratko predstavi ključne storitve ter ga usmeri na podstrani.
|
||||
- **`kdo-sem/index.html`**: Stran "Kdo sem", ki vsebuje podrobnejšo osebno predstavitev Amre Kurešepi Zulji, njeno zgodbo in strokovno ozadje.
|
||||
- **`ponudba/index.html`**: Stran, ki podrobno predstavlja ponudbo jezikovnih tečajev in medkulturnega posredovanja.
|
||||
- **`cene-in-reference/index.html`**: Stran s cenikom za posamezne storitve in referencami (mnenji) strank.
|
||||
- **`cene-in-sodelovanja/index.html`**: Alternativna ali starejša stran za cene, ki uporabnika preusmeri na kontaktno stran za več informacij.
|
||||
- **`kontakt/index.html`**: Stran s kontaktnimi podatki in obrazcem za pošiljanje sporočil.
|
||||
- **`pogosta-vprasanja/index.html`**: Stran z zbranimi pogostimi vprašanji in odgovori (FAQ).
|
||||
- **`politika-zasebnosti/index.html`**: Pravna stran, ki opisuje politiko varovanja osebnih podatkov v skladu z GDPR.
|
||||
- **`delavnice/index.html`**: Pregledna stran, ki deluje kot kazalo za vse razpoložljive delavnice in vodi do njihovih podstrani.
|
||||
- **`skupaj-za-vkljucevanje/`**: Mapa, ki združuje vsebine, povezane s programom "Skupaj za vključevanje". Vsebuje podstrani za medkulturno posredovanje in posamezne delavnice.
|
||||
|
||||
### 📁 `assets/`
|
||||
Mapa za vse statične vire, kot so slike, ikone in dokumenti.
|
||||
- **`favicon/site.webmanifest`**: Manifest datoteka, ki brskalnikom omogoča, da spletno stran prikažejo z lastnostmi spletne aplikacije (npr. ikona na domačem zaslonu).
|
||||
- **`images/`**: Mapa, kjer so shranjene vse slike, uporabljene na spletni strani.
|
||||
- **`pdf/`**: Mapa za PDF dokumente, ki ponujajo podrobnejše opise delavnic.
|
||||
|
||||
### 📁 `css/`
|
||||
Mapa za stilsko oblikovanje spletne strani.
|
||||
- **`style.css`**: Glavna in obsežna CSS datoteka, ki vsebuje vse stile za celotno spletno stran, vključno z odzivnostjo in oblikovanjem posameznih sekcij.
|
||||
- **`animations.css`**: Ločena CSS datoteka, namenjena izključno animacijam.
|
||||
|
||||
### 📁 `js/`
|
||||
Mapa za JavaScript kodo, ki skrbi za interaktivnost.
|
||||
- **`main.js`**: Osrednja JavaScript datoteka, ki upravlja:
|
||||
- Delovanje navigacije (mobilni meni, večnivojski dropdown meniji).
|
||||
- Interaktivne elemente, kot so "harmonika" (accordion) na straneh s pogostimi vprašanji.
|
||||
- Inicializacijo knjižnice AOS (Animate On Scroll) za animacije ob drsenju.
|
||||
- Logiko za pošiljanje podatkov iz kontaktnega obrazca.
|
||||
|
||||
### ⚙️ Backend in konfiguracija
|
||||
- **`kontakt/process_form.php`**: PHP skripta, ki na strežniški strani obdela podatke, poslane preko kontaktnega obrazca, in jih pošlje na e-poštni naslov.
|
||||
- **`robots.txt`**: Datoteka, ki spletnim iskalnikom (npr. Google) daje navodila, katere dele spletne strani naj indeksirajo in katerih ne.
|
||||
- **`sitemap.xml`**: Zemljevid spletnega mesta v XML formatu, ki iskalnikom pomaga pri lažjem in učinkovitejšem odkrivanju vseh podstrani.
|
||||
- **`error_log`**: Samodejno generirana datoteka s strani strežnika, ki beleži morebitne PHP napake.
|
||||
|
||||
### 🛠️ Orodja za avtomatizacijo in vzdrževanje
|
||||
- **`header-template.html`** in **`footer-template.html`**: Predlogi za glavo in nogo spletne strani. Uporabljata se za centralno upravljanje teh elementov, da jih ni treba ročno urejati na vsaki strani posebej.
|
||||
- **`update-menus.sh`** in **`update-footer.sh`**: Shell skripti, ki avtomatizirata posodabljanje glave in noge. Skripta prebere vsebino iz predloge in jo vstavi v vse `.html` datoteke v projektu.
|
||||
- **`optimize_images.py`**: Python skripta za optimizacijo slik. Slike pretvori v sodoben in učinkovit `.webp` format, jih po potrebi pomanjša in originale shrani v varnostno kopijo.
|
||||
- **`generate_responsive_images.py`**: Python skripta, ki iz originalnih slik ustvari več manjših različic za odziven prikaz na različnih velikostih zaslonov.
|
||||
- **`minify_js.py`**: Preprosta Python skripta, ki iz datoteke `main.js` odstrani komentarje in odvečne presledke ter tako zmanjša njeno velikost za hitrejše nalaganje.
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 345 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 419 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 84 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 63 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 65 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 56 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 53 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 36 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 55 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 47 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 495 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 73 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 74 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 86 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 52 KiB |
|
|
@ -0,0 +1,72 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="sl">
|
||||
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<title>__ARTICLE_TITLE__ - Prosberry</title>
|
||||
<meta name="description" content="__ARTICLE_SUMMARY__">
|
||||
<link rel="preconnect" href="https://fonts.googleapis.com">
|
||||
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
|
||||
<link rel="stylesheet"
|
||||
href="https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;500;600;700&display=swap">
|
||||
<link rel="stylesheet" href="https://unpkg.com/aos@next/dist/aos.css" />
|
||||
<link rel="stylesheet" href="/css/style.css?v=1763500835">
|
||||
<link rel="stylesheet" href="/css/animations.css">
|
||||
<link rel="icon" type="image/png" sizes="96x96" href="/assets/favicon/favicon-96x96.png">
|
||||
<link rel="icon" type="image/svg+xml" href="/assets/favicon/favicon.svg">
|
||||
<link rel="shortcut icon" href="/assets/favicon/favicon.ico">
|
||||
<link rel="apple-touch-icon" sizes="180x180" href="/assets/favicon/apple-touch-icon.png">
|
||||
<link rel="manifest" href="/assets/favicon/site.webmanifest">
|
||||
</head>
|
||||
|
||||
<body>
|
||||
__HEADER_CONTENT__
|
||||
<main>
|
||||
<section class="article-hero">
|
||||
<div class="article-hero-text">
|
||||
<p class="article-date">__ARTICLE_DATE__</p>
|
||||
<h1>__ARTICLE_TITLE__</h1>
|
||||
<p class="article-summary">__ARTICLE_SUMMARY__</p>
|
||||
</div>
|
||||
<div class="article-hero-image" style="background-image: url('__ARTICLE_IMAGE__');"></div>
|
||||
</section>
|
||||
<section class="article-content-section">
|
||||
<div class="article-grid" data-aos="fade-up">
|
||||
<article class="article-card">
|
||||
<div class="article-card-body">
|
||||
__ARTICLE_CONTENT__
|
||||
</div>
|
||||
</article>
|
||||
<aside class="article-sidebar">
|
||||
<div class="sidebar-card">
|
||||
<h3>Povezave</h3>
|
||||
<a href="/blog/">Vsi članki</a>
|
||||
<a href="/skupaj-za-vkljucevanje/">Skupaj za vključevanje</a>
|
||||
<a href="/kontakt/">Kontakt</a>
|
||||
</div>
|
||||
<div class="sidebar-card">
|
||||
<h3>Podpora</h3>
|
||||
<p>Potrebujete pomoč pri razumevanju kulturne dinamike v razredu?</p>
|
||||
<a class="cta-button" href="/kontakt/">Pišite nam</a>
|
||||
</div>
|
||||
</aside>
|
||||
</div>
|
||||
</section>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvarimo prostor za učenje, razumevanje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
__FOOTER_CONTENT__
|
||||
<script src="https://unpkg.com/aos@next/dist/aos.js" defer></script>
|
||||
<script src="/js/main.js" defer></script>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
|
@ -0,0 +1,375 @@
|
|||
<!-- {
|
||||
"title": "Medkulturnost: prostor za rast v razredih in skupinah vrtca",
|
||||
"date": "2025-11-17",
|
||||
"image": "/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/1.png",
|
||||
"summary": "Kako ustvariti varen prostor za učno povezovanje v razredih in skupinah vrtca, kjer so otroci iz različnih kulturnih okolij."
|
||||
} -->
|
||||
<!DOCTYPE html>
|
||||
<html lang="sl">
|
||||
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<title>Medkulturnost: prostor za rast v razredih in skupinah vrtca | Prosberry</title>
|
||||
<meta name="description"
|
||||
content="Kako ustvariti varen prostor za učno povezovanje v razredih in skupinah vrtca, kjer so otroci iz različnih kulturnih okolij.">
|
||||
<link rel="preconnect" href="https://fonts.googleapis.com">
|
||||
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
|
||||
<link rel="stylesheet"
|
||||
href="https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;500;600;700&display=swap">
|
||||
<link rel="stylesheet" href="https://unpkg.com/aos@next/dist/aos.css">
|
||||
<link rel="stylesheet" href="/css/style.css">
|
||||
<link rel="stylesheet" href="/css/animations.css">
|
||||
<link rel="icon" type="image/png" sizes="96x96" href="/assets/favicon/favicon-96x96.png">
|
||||
<link rel="icon" type="image/svg+xml" href="/assets/favicon/favicon.svg">
|
||||
<link rel="shortcut icon" href="/assets/favicon/favicon.ico">
|
||||
<link rel="apple-touch-icon" sizes="180x180" href="/assets/favicon/apple-touch-icon.png">
|
||||
<link rel="manifest" href="/assets/favicon/site.webmanifest">
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<header class="main-header">
|
||||
<nav class="nav-container">
|
||||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
<div class="nav-links">
|
||||
<a href="/">Naslovnica</a>
|
||||
<!-- Zavihek "Ponudba" je zdaj dropdown meni -->
|
||||
<div class="dropdown">
|
||||
<button class="dropbtn">Ponudba</button>
|
||||
<div class="dropdown-content">
|
||||
<a href="/ponudba/">Splošne ponudbe</a>
|
||||
<!-- Celoten meni "Skupaj za vključevanje" je premaknjen sem -->
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Skupaj za vključevanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Delavnice</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<!-- Konec menija "Ponudba" -->
|
||||
<div class="dropdown">
|
||||
<button class="dropbtn">Skupaj za vključevanje</button>
|
||||
<div class="dropdown-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Delavnice</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<a href="/kdo-sem">Kdo sem</a>
|
||||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
<span></span>
|
||||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
<main>
|
||||
<section class="contact-hero blog-hero">
|
||||
<div class="contact-hero-content" data-aos="fade-up">
|
||||
<span class="contact-hero-kicker">17. november 2025</span>
|
||||
<h1>Medkulturnost: prostor za rast v razredih in skupinah vrtca</h1>
|
||||
|
||||
</div>
|
||||
<div class="contact-hero-shape shape-a"></div>
|
||||
<div class="contact-hero-shape shape-b"></div>
|
||||
<div class="contact-hero-shape shape-c"></div>
|
||||
<div class="contact-hero-shape shape-d"></div>
|
||||
</section>
|
||||
|
||||
<section class="blog-content">
|
||||
<div class="blog-layout-wrapper">
|
||||
<div class="blog-main-column">
|
||||
<article class="blog-article-content" data-aos="fade-up">
|
||||
|
||||
|
||||
<div class="article-body-text">
|
||||
<div class="article-inline-image float-left">
|
||||
<img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/1.png"
|
||||
alt="Medkulturnost prostor za rast" loading="lazy">
|
||||
</div>
|
||||
|
||||
<p>V mnogih slovenskih šolah in vrtcih so danes v razredih in
|
||||
skupinah tudi otroci iz različnih kulturnih okolij. Takšna raznolikost prinaša svoje
|
||||
izzive, a hkrati ogromno priložnosti za rast, empatijo in nove poglede. Ta stik med
|
||||
različnimi kulturami – to, čemur pravimo medkulturnost – pomeni, da se učimo razumeti,
|
||||
spoštovati in ceniti različne običaje, jezike in načine izražanja, hkrati pa ohranjamo
|
||||
svojo identiteto. V praksi to pomeni ustvariti prijazno in spodbudno vzdušje, kjer se
|
||||
vsak otrok počuti varno in vključeno.</p>
|
||||
|
||||
<h2>Kaj pomenijo medkulturne razlike v razredu in vrtcu?</h2>
|
||||
|
||||
<div class="article-inline-image float-right">
|
||||
<img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/2.png"
|
||||
alt="Medkulturne razlike" loading="lazy">
|
||||
</div>
|
||||
|
||||
<p>Medkulturne razlike se ne kažejo le v jeziku, praznovanjih ali videzu otrok, temveč
|
||||
predvsem v načinu razmišljanja, izražanja in vedenja – v stvareh, ki so pogosto
|
||||
nevidne,
|
||||
dokler nanje ne opozorimo. Vsak otrok prihaja iz okolja, kjer so bile določene
|
||||
vrednote
|
||||
in navade učene, cenjene in razumljene nekoliko drugače. To vpliva na to, kako se
|
||||
vključuje v razred ali skupino, sodeluje in doživlja šolo ali vrtec kot varen
|
||||
prostor za
|
||||
napredovanje in razvoj.</p>
|
||||
<p><strong>Pomembno:</strong> To niso pravila, temveč opazovanja. Otroci iz iste države
|
||||
se
|
||||
lahko med seboj zelo razlikujejo – vsak prinese svojo zgodbo, družinske vrednote in
|
||||
izkušnje. Te razlike so priložnost za razumevanje in odprtost, ne razlog za sodbo
|
||||
ali
|
||||
primerjavo.</p>
|
||||
|
||||
<h2>Kako se otroci izražajo: besede, tišina in pogledi</h2>
|
||||
|
||||
<div class="article-inline-image float-left">
|
||||
<img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/3.png"
|
||||
alt="Kako se otroci izražajo" loading="lazy">
|
||||
</div>
|
||||
|
||||
<p>V razredu ali skupini se otroci ne izražajo samo z besedami – govorica telesa, očesni
|
||||
stik in tišina prav tako povedo veliko o tem, kako se počutijo, razumejo učne vsebine in
|
||||
sodelujejo z drugimi. Razumevanje teh razlik je ključ do uspešne medkulturne
|
||||
komunikacije, saj različni načini izražanja pogosto izhajajo iz kulturnega ozadja otrok.
|
||||
</p>
|
||||
|
||||
<ul>
|
||||
<li><strong>Komunikacija in odnos do avtoritete:</strong> Nekateri otroci so
|
||||
neposredni
|
||||
in povedo stvari naravnost, drugi pa uporabljajo bolj taktičen ali previden
|
||||
način
|
||||
izražanja, da ohranijo harmonijo. Enako velja za odnos do učiteljev – v
|
||||
nekaterih
|
||||
kulturah je avtoriteta formalna in nedotakljiva, drugje pa bolj partnerska in
|
||||
pogajalska. Če tega ne prepoznamo, lahko napačno razumemo otrokove motive ali
|
||||
namene.</li>
|
||||
<li><strong>Tišina in aktivno sodelovanje:</strong> Nekateri otroci bodo takoj
|
||||
delili
|
||||
svoje mnenje, drugi pa raje poslušajo in premislijo, preden spregovorijo. Ti
|
||||
trenutki tišine niso znak nezainteresiranosti, temveč drugačen način učenja in
|
||||
participacije, ki ga je pomembno razumeti v kontekstu njihove kulturne izkušnje.
|
||||
</li>
|
||||
<li><strong>Očesni stik in neverbalna komunikacija:</strong> Neposreden očesni stik
|
||||
je v
|
||||
nekaterih kulturah znak pozornosti in iskrenosti, v drugih pa lahko pomeni
|
||||
predrznost ali nespoštovanje. Geste, mimika in fizična bližina se prav tako
|
||||
razlikujejo – nasmeh je lahko znak prijaznosti ali način, kako otrok skrije
|
||||
neprijetna čustva. Če ne poznamo kulturnega ozadja, lahko napačno
|
||||
interpretiramo,
|
||||
zakaj se otrok vede na določen način.</li>
|
||||
</ul>
|
||||
<div class="article-inline-image float-right">
|
||||
<img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/4.png"
|
||||
alt="Nasvet" loading="lazy">
|
||||
</div>
|
||||
<p>➡️ <strong>Nasvet:</strong> Ne sklepajte avtomatično, da otrok ne želi sodelovati ali
|
||||
ni
|
||||
pozoren. Opazujte, poslušajte in prilagajajte interpretacijo kulturnemu kontekstu.
|
||||
Uporabite igre, delo v parih ali manjše skupine, da omogočite postopno vključevanje
|
||||
in
|
||||
udobno interakcijo.</p>
|
||||
|
||||
<h2>Primeri iz prakse</h2>
|
||||
<ol>
|
||||
<li><strong>Učenka iz Ukrajine ne sodeluje pri ustnih odgovorih</strong> Učitelj
|
||||
lahko
|
||||
pomisli, da se noče vključiti, a v resnici še ni samozavestna v slovenščini ali
|
||||
se
|
||||
boji neposrednega nastopa v tujem jeziku.</li>
|
||||
<p>➡️ <strong>Nasvet:</strong> Ponudite možnost pisnega odgovarjanja ali dela v
|
||||
paru.
|
||||
Spodbujajte postopno vključevanje brez pritiska.</p>
|
||||
<li><strong>Starši otrok iz Albanije se ne udeležijo roditeljskega sestanka</strong>
|
||||
Ni
|
||||
nujno, da jih ne zanima – morda se zaradi omejenega znanja jezika počutijo
|
||||
nelagodno
|
||||
pri javnem izražanju svojih mnenj.</li>
|
||||
<p>➡️ <strong>Nasvet:</strong> Povabilo pošljite v preprostem jeziku in ponudite
|
||||
možnost
|
||||
prvega individualnega srečanja, da zgradite zaupanje.</p>
|
||||
<li><strong>Otrok iz Sirije se izogiba očesnemu stiku</strong> V nekaterih kulturah
|
||||
je
|
||||
neposreden očesni stik lahko razumljen kot predrznost ali nespoštovanje, zato se
|
||||
ga
|
||||
otrok izogiba.</li>
|
||||
<p>➡️ <strong>Nasvet:</strong> Pristopite z razumevanjem in uporabite igre ali
|
||||
naloge,
|
||||
ki omogočajo sodelovanje brez pritiska na neposreden očesni stik.</p>
|
||||
</ol>
|
||||
|
||||
<h2>5 praktičnih nasvetov</h2>
|
||||
|
||||
<div class="article-inline-image float-right">
|
||||
<img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/5.png"
|
||||
alt="Praktični nasveti" loading="lazy">
|
||||
</div>
|
||||
|
||||
<ol>
|
||||
<li><strong>Vprašajte, ne predvidevajte.</strong> Vsaka družina ima svojo zgodbo –
|
||||
pristopite z radovednostjo, ne s sodbo.</li>
|
||||
<li><strong>Učite o raznolikosti.</strong> Pogovorite se o različnih jezikih,
|
||||
praznikih
|
||||
in običajih – otroci bodo to doživeli kot bogastvo, ne kot razliko.</li>
|
||||
<li><strong>Ustvarite varno okolje.</strong> Naj učenci vedo, da je v redu, če
|
||||
delajo
|
||||
napake v jeziku. Vzdušje sprejemanja spodbuja učenje.</li>
|
||||
<li><strong>Sodelujte s starši.</strong> Tudi kratka sporočila o napredku otroka
|
||||
gradijo
|
||||
zaupanje.</li>
|
||||
<li><strong>Povežite se s strokovnjaki.</strong> Delavnice medkulturnega
|
||||
posredovanja
|
||||
ali svetovanja lahko učiteljem in staršem pomagajo bolje razumeti kulturne
|
||||
razlike v
|
||||
praksi.</li>
|
||||
</ol>
|
||||
|
||||
<h2>Zaključek</h2>
|
||||
<div class="article-inline-image float-left">
|
||||
<img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/6.png"
|
||||
alt="Zaključek" loading="lazy">
|
||||
</div>
|
||||
<p>Medkulturnost v razredu ni ovira, ampak priložnost, da skupaj ustvarimo okolje, kjer
|
||||
se
|
||||
vsak otrok počuti slišan, spoštovan in sprejet. Z nekaj razumevanja, potrpežljivosti
|
||||
in
|
||||
medsebojnega sodelovanja lahko razred postane resnično bogata skupnost. Delite svoje
|
||||
izkušnje in vprašanja v kontaktnem obrazcu – skupaj lahko gradimo močnejše in bolj
|
||||
vključujoče šolske in vrtčevske skupnosti.</p>
|
||||
</div>
|
||||
</article>
|
||||
</div>
|
||||
|
||||
<aside class="blog-sidebar">
|
||||
<div class="sidebar-card">
|
||||
<h3>Povezane teme</h3>
|
||||
<div class="sidebar-links">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">Medkulturno posredovanje</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Delavnica: Šola in starši
|
||||
priseljenci</a>
|
||||
<a href="/blog/">Vsi članki</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="sidebar-card">
|
||||
<h3>Potrebujete pomoč?</h3>
|
||||
<p class="sidebar-card-text">Stopite v stik za podporo pri medkulturnem razumevanju</p>
|
||||
<a class="cta-button" href="/kontakt/">Kontaktirajte nas</a>
|
||||
</div>
|
||||
</aside>
|
||||
</div>
|
||||
</section>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvarimo prostor za učenje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
<footer>
|
||||
<div class="footer-content">
|
||||
<div class="footer-logo">
|
||||
<h3>PROSBERRY</h3>
|
||||
</div>
|
||||
<div class="footer-links">
|
||||
<p><a href="/politika-zasebnosti/">Politika zasebnosti</a></p>
|
||||
</div>
|
||||
<div class="footer-contact">
|
||||
<p>Email: <a href="mailto:info@prosberry.si">info@prosberry.si</a></p>
|
||||
<p>Tel: <a href="tel:+38630312855">+386 30 312 855</a></p>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
<script src="https://unpkg.com/aos@next/dist/aos.js" defer></script>
|
||||
<script src="/js/main.js" defer></script>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
|
@ -0,0 +1,215 @@
|
|||
<!-- {
|
||||
"title": "Sample Article Title",
|
||||
"date": "2025-11-17",
|
||||
"image": "/assets/images/blog/sample-image.webp",
|
||||
"summary": "This is a sample summary for the article. It should be one or two sentences long."
|
||||
} -->
|
||||
<!DOCTYPE html>
|
||||
<html lang="sl">
|
||||
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<title>Sample Article Title - Prosberry</title>
|
||||
<meta name="description"
|
||||
content="This is a sample summary for the article. It should be one or two sentences long.">
|
||||
<link rel="preconnect" href="https://fonts.googleapis.com">
|
||||
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
|
||||
<link rel="stylesheet"
|
||||
href="https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;500;600;700&display=swap">
|
||||
<link rel="stylesheet" href="https://unpkg.com/aos@next/dist/aos.css" />
|
||||
<link rel="stylesheet" href="/css/style.css?v=1763500835">
|
||||
<link rel="stylesheet" href="/css/animations.css">
|
||||
<link rel="icon" type="image/png" sizes="96x96" href="/assets/favicon/favicon-96x96.png">
|
||||
<link rel="icon" type="image/svg+xml" href="/assets/favicon/favicon.svg">
|
||||
<link rel="shortcut icon" href="/assets/favicon/favicon.ico">
|
||||
<link rel="apple-touch-icon" sizes="180x180" href="/assets/favicon/apple-touch-icon.png">
|
||||
<link rel="manifest" href="/assets/favicon/site.webmanifest">
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<header class="main-header">
|
||||
<nav class="nav-container">
|
||||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
<div class="nav-links">
|
||||
<a href="/">Naslovnica</a>
|
||||
<!-- Zavihek "Ponudba" je zdaj dropdown meni -->
|
||||
<div class="dropdown">
|
||||
<button class="dropbtn">Ponudba</button>
|
||||
<div class="dropdown-content">
|
||||
<a href="/ponudba/">Splošne ponudbe</a>
|
||||
<!-- Celoten meni "Skupaj za vključevanje" je premaknjen sem -->
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Skupaj za vključevanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Delavnice</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<!-- Konec menija "Ponudba" -->
|
||||
<div class="dropdown">
|
||||
<button class="dropbtn">Skupaj za vključevanje</button>
|
||||
<div class="dropdown-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Delavnice</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<a href="/kdo-sem">Kdo sem</a>
|
||||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
<span></span>
|
||||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
<main>
|
||||
<section class="article-hero">
|
||||
<div class="article-hero-text">
|
||||
<p class="article-date">17. november 2025</p>
|
||||
<h1>Sample Article Title</h1>
|
||||
<p class="article-summary">This is a sample summary for the article. It should be one or two sentences
|
||||
long.</p>
|
||||
</div>
|
||||
<div class="article-hero-image" style="background-image: url('/assets/images/blog/sample-image.webp');">
|
||||
</div>
|
||||
</section>
|
||||
<section class="article-content-section">
|
||||
<div class="article-grid" data-aos="fade-up">
|
||||
<article class="article-card">
|
||||
<div class="article-card-body">
|
||||
|
||||
</div>
|
||||
</article>
|
||||
<aside class="article-sidebar">
|
||||
<div class="sidebar-card">
|
||||
<h3>Povezave</h3>
|
||||
<a href="/blog/">Vsi članki</a>
|
||||
<a href="/skupaj-za-vkljucevanje/">Skupaj za vključevanje</a>
|
||||
<a href="/kontakt/">Kontakt</a>
|
||||
</div>
|
||||
<div class="sidebar-card">
|
||||
<h3>Podpora</h3>
|
||||
<p>Potrebujete pomoč pri razumevanju kulturne dinamike v razredu?</p>
|
||||
<a class="cta-button" href="/kontakt/">Pišite nam</a>
|
||||
</div>
|
||||
</aside>
|
||||
</div>
|
||||
</section>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvarimo prostor za učenje, razumevanje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
<footer>
|
||||
<div class="footer-content">
|
||||
<div class="footer-logo">
|
||||
<h3>PROSBERRY</h3>
|
||||
</div>
|
||||
<div class="footer-links">
|
||||
<p><a href="/politika-zasebnosti/">Politika zasebnosti</a></p>
|
||||
</div>
|
||||
<div class="footer-contact">
|
||||
<p>Email: <a href="mailto:info@prosberry.si">info@prosberry.si</a></p>
|
||||
<p>Tel: <a href="tel:+38630312855">+386 30 312 855</a></p>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
<script src="https://unpkg.com/aos@next/dist/aos.js" defer></script>
|
||||
<script src="/js/main.js" defer></script>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
|
@ -0,0 +1,216 @@
|
|||
<!-- {
|
||||
"title": "Dojemanje časa, točnosti in discipline – od juga proti severu Evrope",
|
||||
"date": "2025-11-18",
|
||||
"image": "/assets/images/blog/time-discipline.webp",
|
||||
"summary": "Medkulturne razlike v dojemanju časa segajo od sproščenih odnosov na jugu do natančne discipline na severu Evrope, zato je pomembno razumeti, kaj posamezne skupine resnično sporočajo z zamudo ali redom."
|
||||
} -->
|
||||
<!DOCTYPE html>
|
||||
<html lang="sl">
|
||||
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<title>Dojemanje časa, točnosti in discipline – od juga proti severu Evrope - Prosberry</title>
|
||||
<meta name="description"
|
||||
content="Medkulturne razlike v dojemanju časa segajo od sproščenih odnosov na jugu do natančne discipline na severu Evrope, zato je pomembno razumeti, kaj posamezne skupine resnično sporočajo z zamudo ali redom.">
|
||||
<link rel="preconnect" href="https://fonts.googleapis.com">
|
||||
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
|
||||
<link rel="stylesheet"
|
||||
href="https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;500;600;700&display=swap">
|
||||
<link rel="stylesheet" href="https://unpkg.com/aos@next/dist/aos.css" />
|
||||
<link rel="stylesheet" href="/css/style.css?v=1763500835">
|
||||
<link rel="stylesheet" href="/css/animations.css">
|
||||
<link rel="icon" type="image/png" sizes="96x96" href="/assets/favicon/favicon-96x96.png">
|
||||
<link rel="icon" type="image/svg+xml" href="/assets/favicon/favicon.svg">
|
||||
<link rel="shortcut icon" href="/assets/favicon/favicon.ico">
|
||||
<link rel="apple-touch-icon" sizes="180x180" href="/assets/favicon/apple-touch-icon.png">
|
||||
<link rel="manifest" href="/assets/favicon/site.webmanifest">
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<header class="main-header">
|
||||
<nav class="nav-container">
|
||||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
<div class="nav-links">
|
||||
<a href="/">Naslovnica</a>
|
||||
<!-- Zavihek "Ponudba" je zdaj dropdown meni -->
|
||||
<div class="dropdown">
|
||||
<button class="dropbtn">Ponudba</button>
|
||||
<div class="dropdown-content">
|
||||
<a href="/ponudba/">Splošne ponudbe</a>
|
||||
<!-- Celoten meni "Skupaj za vključevanje" je premaknjen sem -->
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Skupaj za vključevanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Delavnice</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<!-- Konec menija "Ponudba" -->
|
||||
<div class="dropdown">
|
||||
<button class="dropbtn">Skupaj za vključevanje</button>
|
||||
<div class="dropdown-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Delavnice</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<a href="/kdo-sem">Kdo sem</a>
|
||||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
<span></span>
|
||||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
<main>
|
||||
<section class="article-hero">
|
||||
<div class="article-hero-text">
|
||||
<p class="article-date">18. november 2025</p>
|
||||
<h1>Dojemanje časa, točnosti in discipline – od juga proti severu Evrope</h1>
|
||||
<p class="article-summary">Medkulturne razlike v dojemanju časa segajo od sproščenih odnosov na jugu do
|
||||
natančne discipline na severu Evrope, zato je pomembno razumeti, kaj posamezne skupine resnično
|
||||
sporočajo z zamudo ali redom.</p>
|
||||
</div>
|
||||
<div class="article-hero-image" style="background-image: url('/assets/images/blog/time-discipline.webp');">
|
||||
</div>
|
||||
</section>
|
||||
<section class="article-content-section">
|
||||
<div class="article-grid" data-aos="fade-up">
|
||||
<article class="article-card">
|
||||
<div class="article-card-body">
|
||||
|
||||
</div>
|
||||
</article>
|
||||
<aside class="article-sidebar">
|
||||
<div class="sidebar-card">
|
||||
<h3>Povezave</h3>
|
||||
<a href="/blog/">Vsi članki</a>
|
||||
<a href="/skupaj-za-vkljucevanje/">Skupaj za vključevanje</a>
|
||||
<a href="/kontakt/">Kontakt</a>
|
||||
</div>
|
||||
<div class="sidebar-card">
|
||||
<h3>Podpora</h3>
|
||||
<p>Potrebujete pomoč pri razumevanju kulturne dinamike v razredu?</p>
|
||||
<a class="cta-button" href="/kontakt/">Pišite nam</a>
|
||||
</div>
|
||||
</aside>
|
||||
</div>
|
||||
</section>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvarimo prostor za učenje, razumevanje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
<footer>
|
||||
<div class="footer-content">
|
||||
<div class="footer-logo">
|
||||
<h3>PROSBERRY</h3>
|
||||
</div>
|
||||
<div class="footer-links">
|
||||
<p><a href="/politika-zasebnosti/">Politika zasebnosti</a></p>
|
||||
</div>
|
||||
<div class="footer-contact">
|
||||
<p>Email: <a href="mailto:info@prosberry.si">info@prosberry.si</a></p>
|
||||
<p>Tel: <a href="tel:+38630312855">+386 30 312 855</a></p>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
<script src="https://unpkg.com/aos@next/dist/aos.js" defer></script>
|
||||
<script src="/js/main.js" defer></script>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
|
@ -0,0 +1,245 @@
|
|||
<!-- {
|
||||
"title": "Prihaja kmalu",
|
||||
"date": "2025-11-15",
|
||||
"image": "/assets/images/blog/2025-11-15-prihaja-kmalu/header.png",
|
||||
"summary": "Prihajajo novi članki o medkulturnih temah; vmes si lahko preberete že objavljeno vsebino."
|
||||
} -->
|
||||
<!DOCTYPE html>
|
||||
<html lang="sl">
|
||||
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<title>Prihaja kmalu | Prosberry</title>
|
||||
<meta name="description"
|
||||
content="Prihajajo novi članki o medkulturnih izzivih in praksah. Medtem si lahko preberete obstoječe prispevke in se povežete z nami.">
|
||||
<link rel="preconnect" href="https://fonts.googleapis.com">
|
||||
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
|
||||
<link rel="stylesheet"
|
||||
href="https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;500;600;700&display=swap">
|
||||
<link rel="stylesheet" href="https://unpkg.com/aos@next/dist/aos.css">
|
||||
<link rel="stylesheet" href="/css/style.css">
|
||||
<link rel="stylesheet" href="/css/animations.css">
|
||||
<link rel="icon" type="image/png" sizes="96x96" href="/assets/favicon/favicon-96x96.png">
|
||||
<link rel="icon" type="image/svg+xml" href="/assets/favicon/favicon.svg">
|
||||
<link rel="shortcut icon" href="/assets/favicon/favicon.ico">
|
||||
<link rel="apple-touch-icon" sizes="180x180" href="/assets/favicon/apple-touch-icon.png">
|
||||
<link rel="manifest" href="/assets/favicon/site.webmanifest">
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<header class="main-header">
|
||||
<nav class="nav-container">
|
||||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
<div class="nav-links">
|
||||
<a href="/">Naslovnica</a>
|
||||
<!-- Zavihek "Ponudba" je zdaj dropdown meni -->
|
||||
<div class="dropdown">
|
||||
<button class="dropbtn">Ponudba</button>
|
||||
<div class="dropdown-content">
|
||||
<a href="/ponudba/">Splošne ponudbe</a>
|
||||
<!-- Celoten meni "Skupaj za vključevanje" je premaknjen sem -->
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Skupaj za vključevanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Delavnice</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<!-- Konec menija "Ponudba" -->
|
||||
<div class="dropdown">
|
||||
<button class="dropbtn">Skupaj za vključevanje</button>
|
||||
<div class="dropdown-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Delavnice</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<a href="/kdo-sem">Kdo sem</a>
|
||||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
<span></span>
|
||||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
<main>
|
||||
<section class="contact-hero blog-hero">
|
||||
<div class="contact-hero-content" data-aos="fade-up">
|
||||
<span class="contact-hero-kicker">16. november 2025</span>
|
||||
<h1>Prihaja kmalu</h1>
|
||||
</div>
|
||||
<div class="contact-hero-shape shape-a"></div>
|
||||
<div class="contact-hero-shape shape-b"></div>
|
||||
<div class="contact-hero-shape shape-c"></div>
|
||||
<div class="contact-hero-shape shape-d"></div>
|
||||
</section>
|
||||
|
||||
<section class="blog-content">
|
||||
<div class="blog-layout-wrapper">
|
||||
<div class="blog-main-column">
|
||||
<article class="blog-article-content" data-aos="fade-up">
|
||||
<div class="article-intro-two-column"
|
||||
style="display:flex; flex-wrap:wrap; gap:1rem; align-items:center; margin-bottom:2.5rem;">
|
||||
<p style="flex:1 1 360px; margin:0; line-height:1.7; font-size:1.1rem; text-align:justify;">
|
||||
Prihajajo novi članki o medkulturnih temah, na katerih delamo v ozadju. Medtem ko dokončujemo
|
||||
vsebine, si lahko preberete že objavljene prispevke in najdete navdih ali praktične ideje za delo
|
||||
s skupinami. Novi naslovi bodo kmalu razkriti – spremljajte nas na tej strani ali preko kontaktnega
|
||||
obrazca.
|
||||
</p>
|
||||
<div style="flex:1 1 280px; text-align:right;">
|
||||
<img src="/assets/images/blog/2025-11-18-dojemanje-casa-tocnosti-discipline/1.png"
|
||||
alt="Prihaja kmalu" loading="lazy"
|
||||
style="max-width:130%; height:auto; display:inline-block;">
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="article-body-text">
|
||||
<h2>Ostanite na tekočem</h2>
|
||||
<p>Ko bomo pripravljeni, boste tu našli nove prispevke o dojemanju časa, raznolikosti v učnih skupinah
|
||||
ali vpeljevanju strukturiranih praks v multikulturnih okoljih. Zdaj pa vas vabimo, da preberete
|
||||
prej objavljene članke:</p>
|
||||
<ul>
|
||||
<li><a href="/blog/clanki/2025-11-17-medkulturnost-prostor-za-rast.html">Medkulturnost: prostor za rast v razredih in skupinah vrtca</a></li>
|
||||
<li><a href="/blog/clanki/2025-11-18-dojemanje-casa-tocnosti-discipline.html">Dojemanje časa, točnosti in discipline – od juga proti severu Evrope</a></li>
|
||||
</ul>
|
||||
<p>Če si želite svežega vpogleda, izberite enega od zgornjih člankov ali pokličite, da skupaj najdemo podporne poti.</p>
|
||||
</div>
|
||||
</article>
|
||||
</div>
|
||||
|
||||
<aside class="blog-sidebar" data-aos="fade-up" data-aos-delay="150">
|
||||
<div class="sidebar-card">
|
||||
<h3>Povezane teme</h3>
|
||||
<div class="sidebar-links">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">Medkulturno posredovanje</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Delavnica: Šola in starši
|
||||
priseljenci</a>
|
||||
<a href="/blog/">Vsi članki</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="sidebar-card">
|
||||
<h3>Potrebujete pomoč?</h3>
|
||||
<p class="sidebar-card-text">Stopite v stik za podporo pri medkulturnem razumevanju</p>
|
||||
<a class="cta-button" href="/kontakt/">Kontaktirajte nas</a>
|
||||
</div>
|
||||
</aside>
|
||||
</div>
|
||||
</section>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvarimo prostor za učenje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
<footer>
|
||||
<div class="footer-content">
|
||||
<div class="footer-logo">
|
||||
<h3>PROSBERRY</h3>
|
||||
</div>
|
||||
<div class="footer-links">
|
||||
<p><a href="/politika-zasebnosti/">Politika zasebnosti</a></p>
|
||||
</div>
|
||||
<div class="footer-contact">
|
||||
<p>Email: <a href="mailto:info@prosberry.si">info@prosberry.si</a></p>
|
||||
<p>Tel: <a href="tel:+38630312855">+386 30 312 855</a></p>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
<script src="https://unpkg.com/aos@next/dist/aos.js" defer></script>
|
||||
<script src="/js/main.js" defer></script>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
|
@ -0,0 +1,245 @@
|
|||
<!-- {
|
||||
"title": "Prihaja kmalu",
|
||||
"date": "2025-11-16",
|
||||
"image": "/assets/images/blog/2025-11-16-prihaja-kmalu/header.png",
|
||||
"summary": "Prihajali bodo novi članki o medkulturnih temah; vmes si lahko preberete že objavljeno vsebino."
|
||||
} -->
|
||||
<!DOCTYPE html>
|
||||
<html lang="sl">
|
||||
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<title>Prihaja kmalu | Prosberry</title>
|
||||
<meta name="description"
|
||||
content="Prihajajo novi članki o medkulturnih izzivih in praksah. Medtem si lahko preberete obstoječe prispevke in se povežete z nami.">
|
||||
<link rel="preconnect" href="https://fonts.googleapis.com">
|
||||
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
|
||||
<link rel="stylesheet"
|
||||
href="https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;500;600;700&display=swap">
|
||||
<link rel="stylesheet" href="https://unpkg.com/aos@next/dist/aos.css">
|
||||
<link rel="stylesheet" href="/css/style.css">
|
||||
<link rel="stylesheet" href="/css/animations.css">
|
||||
<link rel="icon" type="image/png" sizes="96x96" href="/assets/favicon/favicon-96x96.png">
|
||||
<link rel="icon" type="image/svg+xml" href="/assets/favicon/favicon.svg">
|
||||
<link rel="shortcut icon" href="/assets/favicon/favicon.ico">
|
||||
<link rel="apple-touch-icon" sizes="180x180" href="/assets/favicon/apple-touch-icon.png">
|
||||
<link rel="manifest" href="/assets/favicon/site.webmanifest">
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<header class="main-header">
|
||||
<nav class="nav-container">
|
||||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
<div class="nav-links">
|
||||
<a href="/">Naslovnica</a>
|
||||
<!-- Zavihek "Ponudba" je zdaj dropdown meni -->
|
||||
<div class="dropdown">
|
||||
<button class="dropbtn">Ponudba</button>
|
||||
<div class="dropdown-content">
|
||||
<a href="/ponudba/">Splošne ponudbe</a>
|
||||
<!-- Celoten meni "Skupaj za vključevanje" je premaknjen sem -->
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Skupaj za vključevanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Delavnice</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<!-- Konec menija "Ponudba" -->
|
||||
<div class="dropdown">
|
||||
<button class="dropbtn">Skupaj za vključevanje</button>
|
||||
<div class="dropdown-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Delavnice</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<a href="/kdo-sem">Kdo sem</a>
|
||||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
<span></span>
|
||||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
<main>
|
||||
<section class="contact-hero blog-hero">
|
||||
<div class="contact-hero-content" data-aos="fade-up">
|
||||
<span class="contact-hero-kicker">16. november 2025</span>
|
||||
<h1>Prihaja kmalu</h1>
|
||||
</div>
|
||||
<div class="contact-hero-shape shape-a"></div>
|
||||
<div class="contact-hero-shape shape-b"></div>
|
||||
<div class="contact-hero-shape shape-c"></div>
|
||||
<div class="contact-hero-shape shape-d"></div>
|
||||
</section>
|
||||
|
||||
<section class="blog-content">
|
||||
<div class="blog-layout-wrapper">
|
||||
<div class="blog-main-column">
|
||||
<article class="blog-article-content" data-aos="fade-up">
|
||||
<div class="article-intro-two-column"
|
||||
style="display:flex; flex-wrap:wrap; gap:1rem; align-items:center; margin-bottom:2.5rem;">
|
||||
<p style="flex:1 1 360px; margin:0; line-height:1.7; font-size:1.1rem; text-align:justify;">
|
||||
Prihajajo novi članki o medkulturnih temah, na katerih delamo v ozadju. Medtem ko dokončujemo
|
||||
vsebine, si lahko preberete že objavljene prispevke in najdete navdih ali praktične ideje za delo
|
||||
s skupinami. Novi naslovi bodo kmalu razkriti – spremljajte nas na tej strani ali preko kontaktnega
|
||||
obrazca.
|
||||
</p>
|
||||
<div style="flex:1 1 280px; text-align:right;">
|
||||
<img src="/assets/images/blog/2025-11-18-dojemanje-casa-tocnosti-discipline/1.png"
|
||||
alt="Prihaja kmalu" loading="lazy"
|
||||
style="max-width:130%; height:auto; display:inline-block;">
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="article-body-text">
|
||||
<h2>Ostanite na tekočem</h2>
|
||||
<p>Ko bomo pripravljeni, boste tu našli nove prispevke o dojemanju časa, raznolikosti v učnih skupinah
|
||||
ali vpeljevanju strukturiranih praks v multikulturnih okoljih. Zdaj pa vas vabimo, da preberete
|
||||
prej objavljene članke:</p>
|
||||
<ul>
|
||||
<li><a href="/blog/clanki/2025-11-17-medkulturnost-prostor-za-rast.html">Medkulturnost: prostor za rast v razredih in skupinah vrtca</a></li>
|
||||
<li><a href="/blog/clanki/2025-11-18-dojemanje-casa-tocnosti-discipline.html">Dojemanje časa, točnosti in discipline – od juga proti severu Evrope</a></li>
|
||||
</ul>
|
||||
<p>Če si želite svežega vpogleda, izberite enega od zgornjih člankov ali pokličite, da skupaj najdemo podporne poti.</p>
|
||||
</div>
|
||||
</article>
|
||||
</div>
|
||||
|
||||
<aside class="blog-sidebar" data-aos="fade-up" data-aos-delay="150">
|
||||
<div class="sidebar-card">
|
||||
<h3>Povezane teme</h3>
|
||||
<div class="sidebar-links">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">Medkulturno posredovanje</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Delavnica: Šola in starši
|
||||
priseljenci</a>
|
||||
<a href="/blog/">Vsi članki</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="sidebar-card">
|
||||
<h3>Potrebujete pomoč?</h3>
|
||||
<p class="sidebar-card-text">Stopite v stik za podporo pri medkulturnem razumevanju</p>
|
||||
<a class="cta-button" href="/kontakt/">Kontaktirajte nas</a>
|
||||
</div>
|
||||
</aside>
|
||||
</div>
|
||||
</section>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvarimo prostor za učenje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
<footer>
|
||||
<div class="footer-content">
|
||||
<div class="footer-logo">
|
||||
<h3>PROSBERRY</h3>
|
||||
</div>
|
||||
<div class="footer-links">
|
||||
<p><a href="/politika-zasebnosti/">Politika zasebnosti</a></p>
|
||||
</div>
|
||||
<div class="footer-contact">
|
||||
<p>Email: <a href="mailto:info@prosberry.si">info@prosberry.si</a></p>
|
||||
<p>Tel: <a href="tel:+38630312855">+386 30 312 855</a></p>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
<script src="https://unpkg.com/aos@next/dist/aos.js" defer></script>
|
||||
<script src="/js/main.js" defer></script>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
|
@ -0,0 +1,352 @@
|
|||
<!-- {
|
||||
"title": "Medkulturnost: prostor za rast v razredih in skupinah vrtca",
|
||||
"date": "2025-11-17",
|
||||
"image": "/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/header.png",
|
||||
"summary": "V razredih in skupinah vrtca si ustvarimo varen prostor, kjer se otroci iz različnih kultur počutijo vključene."
|
||||
} -->
|
||||
<!DOCTYPE html>
|
||||
<html lang="sl">
|
||||
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<title>Medkulturnost: prostor za rast v razredih in skupinah vrtca | Prosberry</title>
|
||||
<meta name="description"
|
||||
content="Kako ustvariti varen prostor za učno povezovanje v razredih in skupinah vrtca, kjer so otroci iz različnih kulturnih okolij.">
|
||||
<link rel="preconnect" href="https://fonts.googleapis.com">
|
||||
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
|
||||
<link rel="stylesheet"
|
||||
href="https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;500;600;700&display=swap">
|
||||
<link rel="stylesheet" href="https://unpkg.com/aos@next/dist/aos.css">
|
||||
<link rel="stylesheet" href="/css/style.css">
|
||||
<link rel="stylesheet" href="/css/animations.css">
|
||||
<link rel="icon" type="image/png" sizes="96x96" href="/assets/favicon/favicon-96x96.png">
|
||||
<link rel="icon" type="image/svg+xml" href="/assets/favicon/favicon.svg">
|
||||
<link rel="shortcut icon" href="/assets/favicon/favicon.ico">
|
||||
<link rel="apple-touch-icon" sizes="180x180" href="/assets/favicon/apple-touch-icon.png">
|
||||
<link rel="manifest" href="/assets/favicon/site.webmanifest">
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<header class="main-header">
|
||||
<nav class="nav-container">
|
||||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
<div class="nav-links">
|
||||
<a href="/">Naslovnica</a>
|
||||
<!-- Zavihek "Ponudba" je zdaj dropdown meni -->
|
||||
<div class="dropdown">
|
||||
<button class="dropbtn">Ponudba</button>
|
||||
<div class="dropdown-content">
|
||||
<a href="/ponudba/">Splošne ponudbe</a>
|
||||
<!-- Celoten meni "Skupaj za vključevanje" je premaknjen sem -->
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Skupaj za vključevanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Delavnice</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<!-- Konec menija "Ponudba" -->
|
||||
<div class="dropdown">
|
||||
<button class="dropbtn">Skupaj za vključevanje</button>
|
||||
<div class="dropdown-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Delavnice</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<a href="/kdo-sem">Kdo sem</a>
|
||||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
<span></span>
|
||||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
<main>
|
||||
<section class="contact-hero blog-hero">
|
||||
<div class="contact-hero-content" data-aos="fade-up">
|
||||
<span class="contact-hero-kicker">17. november 2025</span>
|
||||
<h1>Medkulturnost: prostor za rast v razredih in skupinah vrtca</h1>
|
||||
|
||||
</div>
|
||||
<div class="contact-hero-shape shape-a"></div>
|
||||
<div class="contact-hero-shape shape-b"></div>
|
||||
<div class="contact-hero-shape shape-c"></div>
|
||||
<div class="contact-hero-shape shape-d"></div>
|
||||
</section>
|
||||
|
||||
<section class="blog-content">
|
||||
<div class="blog-layout-wrapper">
|
||||
<div class="blog-main-column">
|
||||
<article class="blog-article-content" data-aos="fade-up">
|
||||
|
||||
|
||||
<div class="article-body-text">
|
||||
<div class="article-inline-image float-left">
|
||||
<img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/1.png"
|
||||
alt="Medkulturnost prostor za rast" loading="lazy">
|
||||
</div>
|
||||
|
||||
<p>V mnogih slovenskih šolah in vrtcih so danes v razredih in skupinah tudi otroci iz
|
||||
različnih kulturnih okolij. Takšna raznolikost prinaša svoje izzive, a hkrati ogromno
|
||||
priložnosti za rast, empatijo in nove poglede. Ta stik med različnimi kulturami – to,
|
||||
čemur pravimo medkulturnost – pomeni, da se učimo razumeti, spoštovati in ceniti različne
|
||||
običaje, jezike in načine izražanja, hkrati pa ohranjamo svojo identiteto. V praksi to
|
||||
pomeni ustvariti prijazno in spodbudno vzdušje, kjer se vsak otrok počuti varno in
|
||||
vključeno. Kako lahko v razredih in skupinah vrtca zagotovimo, da se vsak otrok počuti
|
||||
udobno?</p>
|
||||
|
||||
<h2>Kaj pomenijo medkulturne razlike v razredu in vrtcu?</h2>
|
||||
|
||||
<div class="article-inline-image float-right article-image-wide">
|
||||
<img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/2.png"
|
||||
alt="Medkulturne razlike" loading="lazy" style="width:100%; height:auto;">
|
||||
</div>
|
||||
|
||||
<p>Medkulturne razlike se ne kažejo le v jeziku, praznovanjih ali videzu otrok, temveč
|
||||
predvsem v načinu razmišljanja, izražanja in vedenja – v stvareh, ki so pogosto
|
||||
nevidne,
|
||||
dokler nanje ne opozorimo.</p>
|
||||
<p>Vsak otrok prihaja iz okolja, kjer so bile določene vrednote in navade učene, cenjene in
|
||||
razumljene nekoliko drugače. To vpliva na to, kako se vključuje v razred ali skupino,
|
||||
sodeluje in doživlja šolo ali vrtec kot varen prostor za napredovanje in razvoj.</p>
|
||||
<p><strong>Pomembno:</strong> To niso pravila, temveč opazovanja. Otroci iz iste države se
|
||||
lahko med seboj zelo razlikujejo – vsak prinese svojo zgodbo, družinske vrednote in
|
||||
izkušnje. Te razlike so priložnost za razumevanje in odprtost, ne razlog za sodbo ali
|
||||
primerjavo.</p>
|
||||
|
||||
<h2>Kako se otroci izražajo: besede, tišina in pogledi</h2>
|
||||
|
||||
<div class="article-inline-image float-left article-image-wide">
|
||||
<img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/3.png"
|
||||
alt="Kako se otroci izražajo" loading="lazy" style="width:100%; height:auto;">
|
||||
</div>
|
||||
|
||||
<p>V razredu ali skupini se otroci ne izražajo samo z besedami – govorica telesa, očesni
|
||||
stik in tišina prav tako povedo veliko o tem, kako se počutijo, razumejo učne vsebine in
|
||||
sodelujejo z drugimi. Razumevanje teh razlik je ključ do uspešne medkulturne
|
||||
komunikacije, saj različni načini izražanja pogosto izhajajo iz kulturnega ozadja otrok.
|
||||
</p>
|
||||
|
||||
<ul>
|
||||
<li><strong>Komunikacija in odnos do avtoritete:</strong> Nekateri otroci so neposredni in
|
||||
povedo stvari naravnost, drugi pa uporabljajo bolj taktičen ali previden način
|
||||
izražanja, da ohranijo harmonijo. Enako velja za odnos do učiteljev – v nekaterih
|
||||
kulturah je avtoriteta formalna in nedotakljiva, drugje pa bolj partnerska in
|
||||
pogajalska. Če tega ne prepoznamo, lahko napačno razumemo otrokove motive ali namene.</li>
|
||||
<li><strong>Tišina in aktivno sodelovanje:</strong> Nekateri otroci bodo takoj delili svoje
|
||||
mnenje, drugi pa raje poslušajo in premislijo, preden spregovorijo. Ti trenutki tišine
|
||||
niso znak nezainteresiranosti, temveč drugačen način učenja in participacije, ki ga je
|
||||
pomembno razumeti v kontekstu njihove kulturne izkušnje.</li>
|
||||
<li><strong>Očesni stik in neverbalna komunikacija:</strong> Neposreden očesni stik je v
|
||||
nekaterih kulturah znak pozornosti in iskrenosti, v drugih pa lahko pomeni predrznost
|
||||
ali nespoštovanje. Geste, mimika in fizična bližina se prav tako razlikujejo – nasmeh je
|
||||
lahko znak prijaznosti ali način, kako otrok skrije neprijetna čustva. Če ne poznamo
|
||||
kulturnega ozadja, lahko napačno interpretiramo, zakaj se otrok vede na določen način.</li>
|
||||
</ul>
|
||||
<div class="article-inline-image float-right article-image-wide">
|
||||
<img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/4.png"
|
||||
alt="Nasvet" loading="lazy" style="width:100%; height:auto;">
|
||||
</div>
|
||||
<p>➡️<strong class="tip-label">Nasvet:</strong> Ne sklepajte avtomatično, da otrok ne želi sodelovati ali ni
|
||||
pozoren. Opazujte, poslušajte in prilagajajte interpretacijo kulturnemu kontekstu. Uporabite
|
||||
igre, delo v parih ali manjše skupine, da omogočite postopno vključevanje in udobno
|
||||
interakcijo.</p>
|
||||
|
||||
<h2>Primeri iz prakse</h2>
|
||||
<ol>
|
||||
<li><strong>Učenka iz Ukrajine ne sodeluje pri ustnih odgovorih.</strong> Učitelj lahko
|
||||
pomisli, da se noče vključiti, a v resnici še ni samozavestna v slovenščini ali se boji
|
||||
neposrednega nastopa v tujem jeziku.
|
||||
<p>➡️<strong class="tip-label">Nasvet:</strong> Ponudite možnost pisnega odgovarjanja ali dela v paru.
|
||||
Spodbujajte postopno vključevanje brez pritiska.</p>
|
||||
</li>
|
||||
<li><strong>Starši otrok iz Albanije se ne udeležijo roditeljskega sestanka.</strong> Ni
|
||||
nujno, da jih ne zanima – morda se zaradi omejenega znanja jezika počutijo nelagodno pri
|
||||
javnem izražanju svojih mnenj.
|
||||
<p>➡️<strong class="tip-label">Nasvet:</strong> Povabilo pošljite v preprostem jeziku in ponudite možnost
|
||||
prvega individualnega srečanja, da zgradite zaupanje.</p>
|
||||
</li>
|
||||
<li><strong>Otrok iz Sirije se izogiba očesnemu stiku.</strong> V nekaterih kulturah je
|
||||
neposreden očesni stik lahko razumljen kot predrznost ali nespoštovanje, zato se ga
|
||||
otrok izogiba.
|
||||
<p>➡️<strong class="tip-label">Nasvet:</strong> Pristopite z razumevanjem in uporabite igre ali naloge, ki
|
||||
omogočajo sodelovanje brez pritiska na neposreden očesni stik.</p>
|
||||
</li>
|
||||
</ol>
|
||||
|
||||
<h2>5 praktičnih nasvetov</h2>
|
||||
|
||||
<div class="article-inline-image float-right">
|
||||
<img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/5.png"
|
||||
alt="Praktični nasveti" loading="lazy">
|
||||
</div>
|
||||
|
||||
<ol>
|
||||
<li><strong>Vprašajte, ne predvidevajte.</strong> Vsaka družina ima svojo zgodbo –
|
||||
pristopite z radovednostjo, ne s sodbo.</li>
|
||||
<li><strong>Učite o raznolikosti.</strong> Pogovorite se o različnih jezikih, praznikih in
|
||||
običajih – otroci bodo to doživeli kot bogastvo, ne kot razliko.</li>
|
||||
<li><strong>Ustvarite varno okolje.</strong> Naj učenci vedo, da je v redu, če delajo napake
|
||||
v jeziku. Vzdušje sprejemanja spodbuja učenje.</li>
|
||||
<li><strong>Sodelujte s starši.</strong> Tudi kratka sporočila o napredku otroka gradijo
|
||||
zaupanje.</li>
|
||||
<li><strong>Povežite se s strokovnjaki.</strong> Delavnice medkulturnega posredovanja ali
|
||||
svetovanja lahko učiteljem in staršem pomagajo bolje razumeti kulturne razlike v
|
||||
praksi.</li>
|
||||
</ol>
|
||||
|
||||
<h2>Zaključek</h2>
|
||||
<div class="article-conclusion-block">
|
||||
<div class="article-inline-image article-image-wide conclusion-image">
|
||||
<img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/6.png"
|
||||
alt="Zaključek" loading="lazy" style="width:100%; height:auto;">
|
||||
</div>
|
||||
<div class="article-conclusion-text">
|
||||
<p>Medkulturnost v razredu ni ovira, ampak priložnost, da skupaj ustvarimo okolje,
|
||||
kjer se vsak otrok počuti slišan, spoštovan in sprejet. Z nekaj razumevanja,
|
||||
potrpežljivosti in medsebojnega sodelovanja lahko razred postane resnično bogata
|
||||
skupnost. Delite svoje izkušnje in vprašanja v kontaktnem obrazcu – skupaj lahko
|
||||
gradimo močnejše in bolj vključujoče šolske in vrtčevske skupnosti.</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</article>
|
||||
</div>
|
||||
|
||||
<aside class="blog-sidebar">
|
||||
<div class="sidebar-card">
|
||||
<h3>Povezane teme</h3>
|
||||
<div class="sidebar-links">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">Medkulturno posredovanje</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Delavnica: Šola in starši
|
||||
priseljenci</a>
|
||||
<a href="/blog/">Vsi članki</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="sidebar-card">
|
||||
<h3>Potrebujete pomoč?</h3>
|
||||
<p class="sidebar-card-text">Stopite v stik za podporo pri medkulturnem razumevanju</p>
|
||||
<a class="cta-button" href="/kontakt/">Kontaktirajte nas</a>
|
||||
</div>
|
||||
</aside>
|
||||
</div>
|
||||
</section>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvarimo prostor za učenje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
<footer>
|
||||
<div class="footer-content">
|
||||
<div class="footer-logo">
|
||||
<h3>PROSBERRY</h3>
|
||||
</div>
|
||||
<div class="footer-links">
|
||||
<p><a href="/politika-zasebnosti/">Politika zasebnosti</a></p>
|
||||
</div>
|
||||
<div class="footer-contact">
|
||||
<p>Email: <a href="mailto:info@prosberry.si">info@prosberry.si</a></p>
|
||||
<p>Tel: <a href="tel:+38630312855">+386 30 312 855</a></p>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
<script src="https://unpkg.com/aos@next/dist/aos.js" defer></script>
|
||||
<script src="/js/main.js" defer></script>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
|
@ -0,0 +1,337 @@
|
|||
<!-- {
|
||||
"title": "Dojemanje časa, točnosti in discipline – od juga proti severu Evrope",
|
||||
"date": "2025-11-18",
|
||||
"image": "/assets/images/blog/2025-11-18-dojemanje-casa-tocnosti-discipline/header.png",
|
||||
"summary": "Razumevanje časovne raznolikosti in disciplina v različnih kulturnih kontekstih pomaga zmanjšati nesporazume v razredu."
|
||||
} -->
|
||||
<!DOCTYPE html>
|
||||
<html lang="sl">
|
||||
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<title>Dojemanje časa, točnosti in discipline – od juga proti severu Evrope | Prosberry</title>
|
||||
<meta name="description"
|
||||
content="Medkulturne razlike v dojemanju časa segajo od sproščenih odnosov na jugu do natančne discipline na severu Evrope, zato je pomembno razumeti, kaj posamezne skupine resnično sporočajo z zamudo ali redom.">
|
||||
<link rel="preconnect" href="https://fonts.googleapis.com">
|
||||
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
|
||||
<link rel="stylesheet"
|
||||
href="https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;500;600;700&display=swap">
|
||||
<link rel="stylesheet" href="https://unpkg.com/aos@next/dist/aos.css">
|
||||
<link rel="stylesheet" href="/css/style.css">
|
||||
<link rel="stylesheet" href="/css/animations.css">
|
||||
<link rel="icon" type="image/png" sizes="96x96" href="/assets/favicon/favicon-96x96.png">
|
||||
<link rel="icon" type="image/svg+xml" href="/assets/favicon/favicon.svg">
|
||||
<link rel="shortcut icon" href="/assets/favicon/favicon.ico">
|
||||
<link rel="apple-touch-icon" sizes="180x180" href="/assets/favicon/apple-touch-icon.png">
|
||||
<link rel="manifest" href="/assets/favicon/site.webmanifest">
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<header class="main-header">
|
||||
<nav class="nav-container">
|
||||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
<div class="nav-links">
|
||||
<a href="/">Naslovnica</a>
|
||||
<!-- Zavihek "Ponudba" je zdaj dropdown meni -->
|
||||
<div class="dropdown">
|
||||
<button class="dropbtn">Ponudba</button>
|
||||
<div class="dropdown-content">
|
||||
<a href="/ponudba/">Splošne ponudbe</a>
|
||||
<!-- Celoten meni "Skupaj za vključevanje" je premaknjen sem -->
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Skupaj za vključevanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Delavnice</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<!-- Konec menija "Ponudba" -->
|
||||
<div class="dropdown">
|
||||
<button class="dropbtn">Skupaj za vključevanje</button>
|
||||
<div class="dropdown-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Delavnice</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<a href="/kdo-sem">Kdo sem</a>
|
||||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
<span></span>
|
||||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
<main>
|
||||
<section class="contact-hero blog-hero">
|
||||
<div class="contact-hero-content" data-aos="fade-up">
|
||||
<span class="contact-hero-kicker">18. november 2025</span>
|
||||
<h1>Dojemanje časa, točnosti in discipline – od juga proti severu Evrope</h1>
|
||||
</div>
|
||||
<div class="contact-hero-shape shape-a"></div>
|
||||
<div class="contact-hero-shape shape-b"></div>
|
||||
<div class="contact-hero-shape shape-c"></div>
|
||||
<div class="contact-hero-shape shape-d"></div>
|
||||
</section>
|
||||
|
||||
<section class="blog-content">
|
||||
<div class="blog-layout-wrapper">
|
||||
<div class="blog-main-column">
|
||||
<article class="blog-article-content" data-aos="fade-up">
|
||||
<div class="article-intro-two-column"
|
||||
style="display:flex; flex-wrap:wrap; gap:1rem; align-items:center; margin-bottom:2.5rem;">
|
||||
<p style="flex:2 1 360px; margin:0; line-height:1.7; font-size:1.1rem; text-align:justify;">
|
||||
Razumevanje časa, točnosti in discipline se med kulturami močno razlikuje. Čeprav so te
|
||||
vrednote prisotne povsod, jih ljudje doživljamo na različne načine – od bolj sproščenega
|
||||
odnosa na jugu do izrazito strukturiranega pristopa na severu. Te razlike ne pomenijo, da
|
||||
je nekdo »nereden«, »neodgovoren« ali »rigiden«; gre za kulturne orientacije, ki vplivajo
|
||||
na to, kako družine in otroci razumejo urnike, roke in pravila.
|
||||
</p>
|
||||
<div style="flex:1 1 260px; text-align:right;">
|
||||
<img src="/assets/images/blog/2025-11-18-dojemanje-casa-tocnosti-discipline/1.png"
|
||||
alt="Dojemanje časa, točnosti in discipline" loading="lazy"
|
||||
style="max-width:135%; height:auto; display:inline-block;">
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="article-body-text">
|
||||
|
||||
<h2>Južni Balkan – fleksibilen čas in poudarek na odnosih</h2>
|
||||
|
||||
<p>Na južnem Balkanu je odnos do časa pogosto sproščen in prilagodljiv. Pomembnejši od ure ali
|
||||
natančnega načrta je odnos med ljudmi — če se pogovor zavleče, je to lahko znak, da si
|
||||
vzel čas za drugega, ne pa neodgovornost. Zamuda nekaj minut (včasih tudi več) je
|
||||
razumljena kot nekaj običajnega. »Pridem čez pet minut« lahko pomeni karkoli med pet in
|
||||
petnajstimi minutami. :)</p>
|
||||
<p>Da je južnjaška časovna logika res posebna, dokazujejo številni vsakdanji primeri:</p>
|
||||
<ul>
|
||||
<li><strong>»Pridi na kavo«:</strong> Fraza lahko pomeni 10 minut ali tri ure. Kava je
|
||||
srečanje, pogovor, terapija in sprostitev v enem.</li>
|
||||
<li><strong>Razlaga zamud:</strong> Zamuda ni le razlog — zamuda je zgodba. »Zakaj zamuda?«: »Bom povedal, sedi.« In zgodba šteje.</li>
|
||||
<li><strong>Družinsko kosilo:</strong> Kosilo ob 13.00 se lahko začne ob 13.30 ali 14.15 —
|
||||
če je babica po poti srečala sosedo in je bilo treba »malo poklepetati«.</li>
|
||||
<li><strong>Srečanja, »ki nikoli ne končajo, ko naj bi«:</strong> Če se dogovor konča ob
|
||||
18.00, je povsem normalno, da ob 18.20 šele prehajate iz glavne teme na nepričakovano
|
||||
sladico, ker je nekdo ravno nekaj prinesel iz kuhinje.</li>
|
||||
</ul>
|
||||
|
||||
<div class="article-inline-image"
|
||||
style="max-width:none; width:100%; display:flex; flex-wrap:wrap; gap:1.5rem; align-items:flex-start; margin:0 0 1.5rem;">
|
||||
<div style="flex:1 1 320px; max-width:480px;">
|
||||
<img src="/assets/images/blog/2025-11-18-dojemanje-casa-tocnosti-discipline/2.png"
|
||||
alt="Druženje ob kavi" loading="lazy" style="width: 100%; height: auto;">
|
||||
</div>
|
||||
<p style="flex:1 1 320px; margin:0;">Pri disciplini starši in učitelji običajno kombinirajo
|
||||
avtoriteto in osebni odnos. Pravila so pomembna, a izjeme so sprejemljive, če za njimi
|
||||
stoji človeški razlog. Prav te razlike pogosto povzročijo nesporazume, ko se družine iz
|
||||
juga preselijo v bolj strukturirana okolja na severu.</p>
|
||||
</div>
|
||||
<p>➡️ V praksi v razredu to pomeni:</p>
|
||||
<ul>
|
||||
<li>zamuda na Balkanu se ne dojema kot nespoštovanje,</li>
|
||||
<li>pri delu je več spontanosti, manj minute-natančne točnosti,</li>
|
||||
<li>disciplina temelji na odnosu, ne na pravilih samih.</li>
|
||||
</ul>
|
||||
|
||||
<h2>Slovenija – med sproščenostjo in strukturiranostjo</h2>
|
||||
|
||||
<p>Slovenija stoji na prehodu med balkansko fleksibilnostjo in srednjeevropskim redom. Čas in
|
||||
točnost se cenita kot znak odgovornosti, vendar ostaja prostor za človeški faktor.</p>
|
||||
<p>Zamuda je pogosto razumljena kot neprofesionalna, a ob razlagi sprejemljiva. Disciplino
|
||||
oblikuje kombinacija formalnih pravil in osebnega odnosa — pravila veljajo, a s pogovorom
|
||||
se vedno najde rešitev.</p>
|
||||
|
||||
<div class="article-inline-image float-left">
|
||||
<img src="/assets/images/blog/2025-11-18-dojemanje-casa-tocnosti-discipline/3.png"
|
||||
alt="Pogovor in sodelovanje" loading="lazy">
|
||||
</div>
|
||||
|
||||
<p>➡️ V praksi:</p>
|
||||
<ul>
|
||||
<li>učitelji in starši se trudijo biti točni,</li>
|
||||
<li>razumejo pa, da življenje ni vedno predvidljivo,</li>
|
||||
<li>disciplina temelji na sodelovanju in spoštovanju.</li>
|
||||
</ul>
|
||||
|
||||
<h2>Srednja Evropa – čas kot obljuba in zanesljivost</h2>
|
||||
|
||||
<p>V srednji in severni Evropi je čas razumljen linearno in natančno, pogosto pravijo: »čas je
|
||||
denar«. Če je srečanje ob 8.00, to pomeni ob 8.00. Točnost je izraz spoštovanja,
|
||||
zanesljivosti in profesionalnosti. Zamuda, tudi majhna, se lahko razume kot motnja
|
||||
sistema. Pravila in roki se dosledno spoštujejo, saj zagotavljajo pravičnost in
|
||||
predvidljivost. Disciplina je visoka, otroci pa se zgodaj učijo samostojnosti in
|
||||
načrtovanja.</p>
|
||||
|
||||
<div class="article-inline-image float-right">
|
||||
<img src="/assets/images/blog/2025-11-18-dojemanje-casa-tocnosti-discipline/4.png"
|
||||
alt="Čas in natančnost" loading="lazy">
|
||||
</div>
|
||||
|
||||
<p>➡️ V praksi:</p>
|
||||
<ul>
|
||||
<li>dejavnosti se začnejo točno ob uri,</li>
|
||||
<li>roki so obvezujoči,</li>
|
||||
<li>red in struktura sta osnovni vrednoti.</li>
|
||||
</ul>
|
||||
|
||||
<h2>Zaključek</h2>
|
||||
|
||||
<div class="article-inline-image float-left">
|
||||
<img src="/assets/images/blog/2025-11-18-dojemanje-casa-tocnosti-discipline/5.png"
|
||||
alt="Sodelovanje in razumevanje" loading="lazy">
|
||||
</div>
|
||||
|
||||
<p>Če pogledamo »zemljevid časa« od juga proti severu, vidimo prehod od prilagodljivosti do
|
||||
poudarjene načrtnosti. Razumevanje teh razlik pomaga učiteljem, staršem in učencem
|
||||
zmanjšati nesporazume:</p>
|
||||
<ul>
|
||||
<li>zamuda ni vedno znak nespoštovanja,</li>
|
||||
<li>stroga disciplina ni nujno hladna,</li>
|
||||
<li>toplina juga in zanesljivost severa lahko odlično sobivata v istem razredu.</li>
|
||||
</ul>
|
||||
<p>Pomembno je dodati, da so opisane značilnosti splošna opažanja iz prakse in številnih
|
||||
pogovorov z ljudmi različnih okolij. Ne veljajo za vse in niso pravilo — vsaka družina,
|
||||
posameznik in razred svojo zgodbo piše po svoje.</p>
|
||||
<p>Če se pri svojem delu srečujete z bolj zapletenimi medkulturnimi izzivi ali situacijami, ste
|
||||
vabljeni, da nam pišete preko kontaktnega obrazca. Z veseljem bomo skupaj pogledali vaš
|
||||
primer in poiskali primerne poti ali rešitve.</p>
|
||||
</div>
|
||||
</article>
|
||||
</div>
|
||||
|
||||
<aside class="blog-sidebar" data-aos="fade-up" data-aos-delay="150">
|
||||
<div class="sidebar-card">
|
||||
<h3>Povezane teme</h3>
|
||||
<div class="sidebar-links">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">Medkulturno posredovanje</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Delavnica: Šola in starši
|
||||
priseljenci</a>
|
||||
<a href="/blog/">Vsi članki</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="sidebar-card">
|
||||
<h3>Potrebujete pomoč?</h3>
|
||||
<p class="sidebar-card-text">Stopite v stik za podporo pri medkulturnem razumevanju</p>
|
||||
<a class="cta-button" href="/kontakt/">Kontaktirajte nas</a>
|
||||
</div>
|
||||
</aside>
|
||||
</div>
|
||||
</section>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvarimo prostor za učenje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
<footer>
|
||||
<div class="footer-content">
|
||||
<div class="footer-logo">
|
||||
<h3>PROSBERRY</h3>
|
||||
</div>
|
||||
<div class="footer-links">
|
||||
<p><a href="/politika-zasebnosti/">Politika zasebnosti</a></p>
|
||||
</div>
|
||||
<div class="footer-contact">
|
||||
<p>Email: <a href="mailto:info@prosberry.si">info@prosberry.si</a></p>
|
||||
<p>Tel: <a href="tel:+38630312855">+386 30 312 855</a></p>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
<script src="https://unpkg.com/aos@next/dist/aos.js" defer></script>
|
||||
<script src="/js/main.js" defer></script>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
|
@ -0,0 +1,250 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="sl">
|
||||
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<title>Medkulturni kotiček - Prosberry</title>
|
||||
<meta name="description"
|
||||
content="Novice, razmisleki in napovedi iz sveta medkulturnega povezovanja in poučevanja angleščine, ki jih z vami deli Prosberry.">
|
||||
<link rel="preconnect" href="https://fonts.googleapis.com">
|
||||
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
|
||||
<link rel="stylesheet"
|
||||
href="https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;500;600;700&display=swap">
|
||||
<link rel="stylesheet" href="https://unpkg.com/aos@next/dist/aos.css" />
|
||||
<link rel="stylesheet" href="/css/style.css?v=1763500835">
|
||||
<link rel="stylesheet" href="/css/animations.css">
|
||||
<link rel="icon" type="image/png" sizes="96x96" href="/assets/favicon/favicon-96x96.png">
|
||||
<link rel="icon" type="image/svg+xml" href="/assets/favicon/favicon.svg">
|
||||
<link rel="shortcut icon" href="/assets/favicon/favicon.ico">
|
||||
<link rel="apple-touch-icon" sizes="180x180" href="/assets/favicon/apple-touch-icon.png">
|
||||
<link rel="manifest" href="/assets/favicon/site.webmanifest">
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<header class="main-header">
|
||||
<nav class="nav-container">
|
||||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
<div class="nav-links">
|
||||
<a href="/">Naslovnica</a>
|
||||
<!-- Zavihek "Ponudba" je zdaj dropdown meni -->
|
||||
<div class="dropdown">
|
||||
<button class="dropbtn">Ponudba</button>
|
||||
<div class="dropdown-content">
|
||||
<a href="/ponudba/">Splošne ponudbe</a>
|
||||
<!-- Celoten meni "Skupaj za vključevanje" je premaknjen sem -->
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Skupaj za vključevanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Delavnice</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<!-- Konec menija "Ponudba" -->
|
||||
<div class="dropdown">
|
||||
<button class="dropbtn">Skupaj za vključevanje</button>
|
||||
<div class="dropdown-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Delavnice</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<a href="/kdo-sem">Kdo sem</a>
|
||||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
<span></span>
|
||||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
|
||||
<main>
|
||||
<section class="contact-hero blog-hero">
|
||||
<div class="contact-hero-content" data-aos="fade-up">
|
||||
<span class="contact-hero-kicker">Zamisli, razumi, poveži</span>
|
||||
<h1>Medkulturni kotiček</h1>
|
||||
<p class="contact-hero-lead">Tu zbiramo izkušnje, nasvete in dobre prakse z jezikovnega in medkulturnega področja. Namen je ustvariti prostor srečanja, učenja in navdiha.</p>
|
||||
</div>
|
||||
<div class="contact-hero-shape shape-a"></div>
|
||||
<div class="contact-hero-shape shape-b"></div>
|
||||
<div class="contact-hero-shape shape-c"></div>
|
||||
<div class="contact-hero-shape shape-d"></div>
|
||||
</section>
|
||||
<section class="blog-content">
|
||||
<div class="blog-layout-wrapper">
|
||||
<div class="blog-main-column">
|
||||
<article class="featured-article" data-aos="fade-up">
|
||||
<a href="/blog/clanki/2025-11-18-dojemanje-casa-tocnosti-discipline.html">
|
||||
<img src="/assets/images/blog/2025-11-18-dojemanje-casa-tocnosti-discipline/header.png" alt="Dojemanje časa, točnosti in discipline – od juga proti severu Evrope">
|
||||
<div class="featured-article-content">
|
||||
<p class="article-date">18. november 2025</p>
|
||||
<h2>Dojemanje časa, točnosti in discipline – od juga proti severu Evrope</h2>
|
||||
<p>Razumevanje časovne raznolikosti in disciplina v različnih kulturnih kontekstih pomaga zmanjšati nesporazume v razredu.</p>
|
||||
</div>
|
||||
</a>
|
||||
</article>
|
||||
<div class="recent-articles-grid" data-aos="fade-up" data-aos-delay="100">
|
||||
|
||||
<article class="recent-card">
|
||||
<a href="/blog/clanki/2025-11-17-medkulturnost-prostor-za-rast.html">
|
||||
<img src="/assets/images/blog/2025-11-17-medkulturnost-prostor-za-rast/header.png" alt="Medkulturnost: prostor za rast v razredih in skupinah vrtca">
|
||||
<h3>Medkulturnost: prostor za rast v razredih in skupinah vrtca</h3>
|
||||
<p class="article-date">17.11.2025</p>
|
||||
<p>V razredih in skupinah vrtca si ustvarimo varen prostor, kjer se otroci iz različnih kultur počutijo vključene.</p>
|
||||
</a>
|
||||
</article>
|
||||
<article class="recent-card">
|
||||
<div class="placeholder-card-content">
|
||||
<img src="/assets/images/blog/2025-11-16-prihaja-kmalu/header.png"
|
||||
alt="ANGLEŠČINA, jezik, ki odpira vrata na poti do sebe in sveta">
|
||||
<h3>ANGLEŠČINA, jezik, ki odpira vrata na poti do sebe in sveta</h3>
|
||||
<p>Prihaja kmalu.</p>
|
||||
</div>
|
||||
</article>
|
||||
<article class="recent-card">
|
||||
<div class="placeholder-card-content">
|
||||
<img src="/assets/images/blog/2025-11-15-prihaja-kmalu/header.png"
|
||||
alt="Zakaj nekateri starši delujejo »neodzivno« in kako graditi medkulturno zaupanje?">
|
||||
<h3>Zakaj nekateri starši delujejo »neodzivno« in kako graditi medkulturno zaupanje?</h3>
|
||||
<p>Prihaja kmalu.</p>
|
||||
</div>
|
||||
</article>
|
||||
</div>
|
||||
</div>
|
||||
<aside class="blog-sidebar" data-aos="fade-up" data-aos-delay="150">
|
||||
<div class="sidebar-card">
|
||||
<h3>Seznam vsebin</h3>
|
||||
<ul class="older-articles-list">
|
||||
|
||||
<li><a href="/blog/clanki/2025-11-18-dojemanje-casa-tocnosti-discipline.html">Dojemanje časa, točnosti in discipline – od juga proti severu Evrope</a> - 18.11.2025</li>
|
||||
<li><a href="/blog/clanki/2025-11-17-medkulturnost-prostor-za-rast.html">Medkulturnost: prostor za rast v razredih in skupinah vrtca</a> - 17.11.2025</li>
|
||||
<li><span>ANGLEŠČINA, jezik, ki odpira vrata na poti do sebe in sveta</span> – Prihaja kmalu.</li>
|
||||
<li><span>Zakaj nekateri starši delujejo »neodzivno« in kako graditi medkulturno zaupanje?</span> – Prihaja kmalu.</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="sidebar-card">
|
||||
<h3>Arhiv</h3>
|
||||
<ul class="archive-list">
|
||||
<!-- Additional archive items if needed -->
|
||||
</ul>
|
||||
</div>
|
||||
</aside>
|
||||
</div>
|
||||
</section>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvarimo prostor za učenje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
<footer>
|
||||
<div class="footer-content">
|
||||
<div class="footer-logo">
|
||||
<h3>PROSBERRY</h3>
|
||||
</div>
|
||||
<div class="footer-links">
|
||||
<p><a href="/politika-zasebnosti/">Politika zasebnosti</a></p>
|
||||
</div>
|
||||
<div class="footer-contact">
|
||||
<p>Email: <a href="mailto:info@prosberry.si">info@prosberry.si</a></p>
|
||||
<p>Tel: <a href="tel:+38630312855">+386 30 312 855</a></p>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
<script src="https://unpkg.com/aos@next/dist/aos.js" defer></script>
|
||||
<script src="/js/main.js" defer></script>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
|
@ -0,0 +1,78 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="sl">
|
||||
|
||||
<head>
|
||||
<meta charset="UTF-8">
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||||
<title>Medkulturni kotiček - Prosberry</title>
|
||||
<meta name="description"
|
||||
content="Novice, razmisleki in napovedi iz sveta medkulturnega povezovanja in poučevanja angleščine, ki jih z vami deli Prosberry.">
|
||||
<link rel="preconnect" href="https://fonts.googleapis.com">
|
||||
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
|
||||
<link rel="stylesheet"
|
||||
href="https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;500;600;700&display=swap">
|
||||
<link rel="stylesheet" href="https://unpkg.com/aos@next/dist/aos.css" />
|
||||
<link rel="stylesheet" href="/css/style.css?v=1763500835">
|
||||
<link rel="stylesheet" href="/css/animations.css">
|
||||
<link rel="icon" type="image/png" sizes="96x96" href="/assets/favicon/favicon-96x96.png">
|
||||
<link rel="icon" type="image/svg+xml" href="/assets/favicon/favicon.svg">
|
||||
<link rel="shortcut icon" href="/assets/favicon/favicon.ico">
|
||||
<link rel="apple-touch-icon" sizes="180x180" href="/assets/favicon/apple-touch-icon.png">
|
||||
<link rel="manifest" href="/assets/favicon/site.webmanifest">
|
||||
</head>
|
||||
|
||||
<body>
|
||||
__HEADER_CONTENT__
|
||||
<main>
|
||||
<section class="contact-hero blog-hero">
|
||||
<div class="contact-hero-content" data-aos="fade-up">
|
||||
<span class="contact-hero-kicker">Zamisli, razumi, poveži</span>
|
||||
<h1>Medkulturni kotiček</h1>
|
||||
<p class="contact-hero-lead">__BLOG_LEAD__</p>
|
||||
</div>
|
||||
<div class="contact-hero-shape shape-a"></div>
|
||||
<div class="contact-hero-shape shape-b"></div>
|
||||
<div class="contact-hero-shape shape-c"></div>
|
||||
<div class="contact-hero-shape shape-d"></div>
|
||||
</section>
|
||||
<section class="blog-content">
|
||||
<div class="blog-layout-wrapper">
|
||||
<div class="blog-main-column">
|
||||
__NAJNOVEJSI_CLANEK__
|
||||
<div class="recent-articles-grid" data-aos="fade-up" data-aos-delay="100">
|
||||
__CAKAJOCI_CLANKI__
|
||||
</div>
|
||||
</div>
|
||||
<aside class="blog-sidebar" data-aos="fade-up" data-aos-delay="150">
|
||||
<div class="sidebar-card">
|
||||
<h3>__ARCHIVE_HEADING__</h3>
|
||||
<ul class="older-articles-list">
|
||||
__ARHIV_SEZNAM__
|
||||
</ul>
|
||||
</div>
|
||||
<div class="sidebar-card">
|
||||
<h3>Arhiv</h3>
|
||||
<ul class="archive-list">
|
||||
<!-- Additional archive items if needed -->
|
||||
</ul>
|
||||
</div>
|
||||
</aside>
|
||||
</div>
|
||||
</section>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvarimo prostor za učenje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
__FOOTER_CONTENT__
|
||||
<script src="https://unpkg.com/aos@next/dist/aos.js" defer></script>
|
||||
<script src="/js/main.js" defer></script>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
|
@ -30,7 +30,7 @@
|
|||
</head>
|
||||
|
||||
<body>
|
||||
<header class="main-header">
|
||||
<header class="main-header">
|
||||
<nav class="nav-container">
|
||||
<div class="logo">
|
||||
<a href="/">
|
||||
|
|
@ -38,8 +38,8 @@
|
|||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500"
|
||||
decoding="async" fetchpriority="high">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
|
|
@ -59,8 +59,7 @@
|
|||
<div class="dropdown-submenu-content">
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
</div>
|
||||
|
|
@ -71,11 +70,9 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj
|
||||
se
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in
|
||||
starši
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -89,8 +86,7 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od
|
||||
tujca do
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -107,8 +103,7 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
|
|
@ -120,8 +115,7 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
|
|
@ -130,8 +124,7 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo
|
||||
nove
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -150,6 +143,7 @@
|
|||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
|
|
@ -157,7 +151,7 @@
|
|||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
</header>
|
||||
|
||||
<main>
|
||||
<section class="rates-hero">
|
||||
|
|
@ -236,7 +230,7 @@
|
|||
data-aos-delay="120">
|
||||
<div class="rates-testimonial-text">
|
||||
<div class="rates-testimonial-full">
|
||||
<p>V veliko veselje mi je nekaj malega napisati o Amri Kurešepi za njeno spletno stran v
|
||||
<p>V veliko veselje mi je nekaj malega napisati o Amri Kurešepi Zulji za njeno spletno stran v
|
||||
okencu 'kaj pravijo o meni'.</p>
|
||||
<p>Amra je prišla v Ljubljano iz Prištine in tu nadaljevala študij angleščine na
|
||||
bolonjski magistrski stopnji. Poleg predanega magistrskega študija se je ves čas
|
||||
|
|
@ -253,7 +247,7 @@
|
|||
naslovom "Factors that Influence the Process of Learning Foreign Languages and Some
|
||||
Potential Effects of Multilingualism" (Dejavniki, ki vplivajo na proces učenja tujih
|
||||
jezikov in nekaj morebitnih učinkov večjezičnosti).</p>
|
||||
<p>V luči mojega osebnega poznavanja kolegice Amre Kurešepi sem prepričan, da lastnosti,
|
||||
<p>V luči mojega osebnega poznavanja kolegice Amre Kurešepi Zulji sem prepričan, da lastnosti,
|
||||
ki jih je izkazovala že med študijem, tj. zavzetost, resnost, odgovornost,
|
||||
samostojnost in ustvarjalnost, izkazuje pri vsakem delu, ki ga opravlja.</p>
|
||||
</div>
|
||||
|
|
@ -285,7 +279,7 @@
|
|||
<p>Na osnovni šoli, kjer sem zaposlena kot svetovalna delavka imamo tudi kar nekaj otrok
|
||||
iz Kosova. Sodelovanje s temi družinami je poseben izziv, zaradi jezikovnih in tudi
|
||||
medkulturnih razlik. Večina staršev naših albanskih otrok ne govori slovensko, niti
|
||||
angleško, tako da je bila Amra Kurešepi izjemno v pomoč pri prevajanju na sestankih
|
||||
angleško, tako da je bila Amra Kurešepi Zulji izjemno v pomoč pri prevajanju na sestankih
|
||||
s temi družinami.</p>
|
||||
<p>Z današnjo tehnologijo si s prevajalnikom sicer lahko prevedemo osnovne informacije,
|
||||
za bolj kočljive teme pa je pogovor v živo neprecenljiv. Kadar gre za teme, ki so za
|
||||
|
|
@ -300,8 +294,8 @@
|
|||
</div>
|
||||
</div>
|
||||
<div class="rates-testimonial-author">
|
||||
<p>mag. Barbara Vodopivec, socialna pedagoginja</p>
|
||||
<p>Svetovalna delavka, OŠ Livada, Ljubljana</p>
|
||||
<p>Barbara Vodopivec, univ. dipl. socialna pedagoginja in sistemska psihoterapevtka</p>
|
||||
<p>Svetovalna delavka v OŠ Livada, Ljubljana</p>
|
||||
</div>
|
||||
</article>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -31,8 +31,11 @@
|
|||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w" sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async" fetchpriority="high">
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
|
|
@ -50,7 +53,8 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
|
|
@ -62,20 +66,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -103,20 +111,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -127,6 +139,7 @@
|
|||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
|
|
@ -134,7 +147,7 @@
|
|||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
</header>
|
||||
|
||||
|
||||
|
||||
|
|
@ -146,7 +159,18 @@
|
|||
<a href="/kontakt" class="cta-button" data-aos="fade-up" data-aos-delay="200">Stopite v stik</a>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvariva prostor za učenje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
</main>
|
||||
|
||||
<footer>
|
||||
<div class="footer-content">
|
||||
|
|
|
|||
|
|
@ -0,0 +1,52 @@
|
|||
I am waiting for your answers to the following clarification questions regarding the blog feature specification:
|
||||
|
||||
## Question 1: `jq` Dependency Handling
|
||||
|
||||
**Context**:
|
||||
```markdown
|
||||
- What happens when `jq` is not installed on the system where `posodobi_blog.sh` is run? The script should ideally check for `jq` and provide a user-friendly error message if it's missing. [NEEDS CLARIFICATION: Should the script check for `jq` and exit with an error if not found, or assume `jq` is always available?]
|
||||
```
|
||||
**What we need to know**: Should the `posodobi_blog.sh` script explicitly check for the presence of `jq` and handle its absence?
|
||||
|
||||
**Suggested Answers**:
|
||||
|
||||
| Option | Answer | Implications |
|
||||
|--------|--------|--------------|
|
||||
| A | **Check for `jq` and exit with an error if not found.** | The script will be more robust and provide clear feedback to the user if `jq` is missing. This adds a small amount of complexity to the script. |
|
||||
| B | **Assume `jq` is always available.** | The script will be simpler, but might fail with cryptic errors if `jq` is not installed, requiring manual debugging. |
|
||||
|
||||
**Your choice**: _[Please respond with A or B]_
|
||||
|
||||
## Question 2: Malformed JSON Metadata Handling
|
||||
|
||||
**Context**:
|
||||
```markdown
|
||||
- How does the system handle malformed JSON metadata in an article file? The script should ideally skip the problematic article and log an error, rather than failing entirely. [NEEDS CLARIFICATION: Should malformed JSON cause the script to fail or skip the article with a warning?]
|
||||
```
|
||||
**What we need to know**: How should the `posodobi_blog.sh` script behave if it encounters malformed JSON metadata in an article file?
|
||||
|
||||
**Suggested Answers**:
|
||||
|
||||
| Option | Answer | Implications |
|
||||
|--------|--------|--------------|
|
||||
| A | **Skip the problematic article and log a warning.** | The script will continue processing other articles, ensuring the blog is mostly updated. The user will be informed about the issue with the specific article. |
|
||||
| B | **Fail the script entirely.** | The script will stop execution, forcing the user to fix the malformed JSON before any blog updates can proceed. This ensures data integrity but might be less user-friendly. |
|
||||
|
||||
**Your choice**: _[Please respond with A or B]_
|
||||
|
||||
## Question 3: Invalid Article Filename Convention
|
||||
|
||||
**Context**:
|
||||
```markdown
|
||||
- What happens if an article file does not follow the `YYYY-MM-DD-` naming convention? The script should ideally ignore such files or log a warning.
|
||||
```
|
||||
**What we need to know**: How should the `posodobi_blog.sh` script handle article files that do not adhere to the `YYYY-MM-DD-` naming convention?
|
||||
|
||||
**Suggested Answers**:
|
||||
|
||||
| Option | Answer | Implications |
|
||||
|--------|--------|--------------|
|
||||
| A | **Ignore such files and log a warning.** | The script will only process correctly named article files, and the user will be informed about any files that were skipped. This allows for flexibility but might hide issues if the user expects all files to be processed. |
|
||||
| B | **Fail the script entirely.** | The script will stop execution, forcing the user to rename incorrectly named files. This ensures strict adherence to the naming convention but might be less user-friendly. |
|
||||
|
||||
**Your choice**: _[Please respond with A or B]_
|
||||
7148
code_export.txt
7148
code_export.txt
File diff suppressed because one or more lines are too long
6023
css/style.css
6023
css/style.css
File diff suppressed because one or more lines are too long
|
|
@ -31,8 +31,11 @@
|
|||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w" sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async" fetchpriority="high">
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
|
|
@ -50,7 +53,8 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
|
|
@ -62,20 +66,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -103,20 +111,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -127,6 +139,7 @@
|
|||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
|
|
@ -134,7 +147,7 @@
|
|||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
</header>
|
||||
|
||||
<main>
|
||||
<section class="workshop-directory-hero">
|
||||
|
|
@ -209,7 +222,18 @@
|
|||
</div>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvariva prostor za učenje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
</main>
|
||||
|
||||
<footer>
|
||||
<div class="footer-content">
|
||||
|
|
|
|||
|
|
@ -0,0 +1,76 @@
|
|||
#!/bin/bash
|
||||
set -euo pipefail
|
||||
|
||||
css_file="css/style.css"
|
||||
|
||||
if [[ ! -f "$css_file" ]]; then
|
||||
echo "error: $css_file not found" >&2
|
||||
exit 1
|
||||
fi
|
||||
|
||||
python3 - <<'PY'
|
||||
from pathlib import Path
|
||||
|
||||
css_path = Path("css/style.css")
|
||||
text = css_path.read_text()
|
||||
|
||||
output = []
|
||||
token = []
|
||||
indent = 0
|
||||
idx = 0
|
||||
length = len(text)
|
||||
|
||||
def flush_token():
|
||||
if token:
|
||||
joined = " ".join("".join(token).split())
|
||||
token.clear()
|
||||
return joined
|
||||
return ""
|
||||
|
||||
while idx < length:
|
||||
if text.startswith("/*", idx):
|
||||
comment_end = text.find("*/", idx + 2)
|
||||
if comment_end == -1:
|
||||
comment_end = length - 2
|
||||
comment = text[idx : comment_end + 2]
|
||||
output.append(" " * (indent * 4) + comment.strip() + "\n")
|
||||
idx = comment_end + 2
|
||||
continue
|
||||
|
||||
c = text[idx]
|
||||
|
||||
if c.isspace():
|
||||
idx += 1
|
||||
continue
|
||||
|
||||
if c == "{":
|
||||
selector = flush_token()
|
||||
output.append(selector + " {\n")
|
||||
indent += 1
|
||||
idx += 1
|
||||
continue
|
||||
|
||||
if c == "}":
|
||||
pending = flush_token()
|
||||
if pending:
|
||||
output.append(" " * (indent * 4) + pending + "\n")
|
||||
indent = max(0, indent - 1)
|
||||
output.append(" " * (indent * 4) + "}\n\n")
|
||||
idx += 1
|
||||
continue
|
||||
|
||||
if c == ";":
|
||||
property_block = flush_token()
|
||||
if property_block:
|
||||
output.append(" " * (indent * 4) + property_block + ";\n")
|
||||
idx += 1
|
||||
continue
|
||||
|
||||
token.append(c)
|
||||
idx += 1
|
||||
|
||||
result = "".join(output).rstrip() + "\n"
|
||||
css_path.write_text(result)
|
||||
PY
|
||||
|
||||
echo "Formatted $css_file"
|
||||
|
|
@ -3,8 +3,11 @@
|
|||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w" sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async" fetchpriority="high">
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
|
|
@ -22,7 +25,8 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
|
|
@ -34,20 +38,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -75,20 +83,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -99,6 +111,7 @@
|
|||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
|
|
@ -106,4 +119,4 @@
|
|||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
</header>
|
||||
|
|
|
|||
39
index.html
39
index.html
|
|
@ -33,8 +33,11 @@
|
|||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w" sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async" fetchpriority="high">
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
|
|
@ -52,7 +55,8 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
|
|
@ -64,20 +68,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -105,20 +113,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -129,6 +141,7 @@
|
|||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
|
|
@ -136,7 +149,7 @@
|
|||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
</header>
|
||||
|
||||
<main>
|
||||
<!-- ===== ZAČETEK NOVE VSEBINE ===== -->
|
||||
|
|
@ -185,7 +198,7 @@
|
|||
</div>
|
||||
<div class="feature-card" data-aos="fade-up" data-aos-delay="300">
|
||||
<h3>Prejmi podporo, ko jo najbolj potrebuješ</h3>
|
||||
<p>Medkulturno posredovanje, ki vsakodnevne izzive naredi lažje za vse.</p>
|
||||
<p>Medkulturno posredovanje, ki vsakodnevne izzive naredi lažje za vse — v slovenščini, albanščini, srbščini in angleščini.</p>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/" class="cta-button">MK POSREDOVANJE</a>
|
||||
</div>
|
||||
</div>
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
|
|
@ -31,8 +31,11 @@
|
|||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w" sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async" fetchpriority="high">
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
|
|
@ -50,7 +53,8 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
|
|
@ -62,20 +66,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -103,20 +111,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -127,6 +139,7 @@
|
|||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
|
|
@ -134,7 +147,7 @@
|
|||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
</header>
|
||||
|
||||
|
||||
|
||||
|
|
@ -195,7 +208,18 @@
|
|||
</div>
|
||||
</section>
|
||||
|
||||
</main>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvariva prostor za učenje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
</main>
|
||||
|
||||
<footer>
|
||||
<div class="footer-content">
|
||||
|
|
|
|||
|
|
@ -31,8 +31,11 @@
|
|||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w" sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async" fetchpriority="high">
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
|
|
@ -50,7 +53,8 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
|
|
@ -62,20 +66,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -103,20 +111,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -127,6 +139,7 @@
|
|||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
|
|
@ -134,7 +147,7 @@
|
|||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
</header>
|
||||
<main>
|
||||
<section class="contact-hero">
|
||||
<div class="contact-hero-content" data-aos="fade-up">
|
||||
|
|
@ -196,7 +209,18 @@
|
|||
</div>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvariva prostor za učenje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
</main>
|
||||
<footer>
|
||||
<div class="footer-content">
|
||||
<div class="footer-logo">
|
||||
|
|
|
|||
|
|
@ -30,8 +30,11 @@
|
|||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w" sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async" fetchpriority="high">
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
|
|
@ -49,7 +52,8 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
|
|
@ -61,20 +65,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -102,20 +110,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -126,6 +138,7 @@
|
|||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
|
|
@ -133,7 +146,7 @@
|
|||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
</header>
|
||||
<main>
|
||||
<section class="faq-hero">
|
||||
<div class="faq-hero-container">
|
||||
|
|
@ -254,7 +267,18 @@
|
|||
</div>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvariva prostor za učenje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
</main>
|
||||
<footer>
|
||||
<div class="footer-content">
|
||||
<div class="footer-logo">
|
||||
|
|
|
|||
|
|
@ -31,8 +31,11 @@
|
|||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w" sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async" fetchpriority="high">
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
|
|
@ -50,7 +53,8 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
|
|
@ -62,20 +66,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -103,20 +111,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -127,6 +139,7 @@
|
|||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
|
|
@ -134,7 +147,7 @@
|
|||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
</header>
|
||||
<main>
|
||||
<section class="policy-hero">
|
||||
<div class="policy-hero-container">
|
||||
|
|
@ -208,7 +221,18 @@
|
|||
</article>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvariva prostor za učenje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
</main>
|
||||
<footer>
|
||||
<div class="footer-content">
|
||||
<div class="footer-logo">
|
||||
|
|
|
|||
|
|
@ -1,11 +1,14 @@
|
|||
<!DOCTYPE html>
|
||||
<html lang="sl">
|
||||
<head>
|
||||
|
||||
<head>
|
||||
<meta charset="UTF-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
|
||||
<title>Ponudba - Prosberry</title>
|
||||
<meta name="description" content="Odkrijte celotno ponudbo Prosberry: tečaji angleščine, albanščine in slovenščine za vse nivoje ter medkulturno posredovanje za institucije, šole in priseljence. Učenje in podpora prilagojena vašim potrebam.">
|
||||
<meta name="keywords" content="ponudba, tečaji angleščine, učenje albanščine, tečaji slovenščine, medkulturno posredovanje, inštrukcije, Prosberry, Amra Kurešepi Zulji">
|
||||
<meta name="description"
|
||||
content="Odkrijte celotno ponudbo Prosberry: tečaji angleščine, albanščine in slovenščine za vse nivoje ter medkulturno posredovanje za institucije, šole in priseljence. Učenje in podpora prilagojena vašim potrebam.">
|
||||
<meta name="keywords"
|
||||
content="ponudba, tečaji angleščine, učenje albanščine, tečaji slovenščine, medkulturno posredovanje, inštrukcije, Prosberry, Amra Kurešepi Zulji">
|
||||
<meta name="author" content="Amra Kurešepi Zulji">
|
||||
<link rel="preconnect" href="https://fonts.googleapis.com" />
|
||||
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
|
||||
|
|
@ -13,7 +16,8 @@
|
|||
<link rel="dns-prefetch" href="https://fonts.googleapis.com" />
|
||||
<link rel="dns-prefetch" href="https://fonts.gstatic.com" />
|
||||
<link rel="dns-prefetch" href="https://unpkg.com" />
|
||||
<link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;500;600;700&display=swap" />
|
||||
<link rel="stylesheet"
|
||||
href="https://fonts.googleapis.com/css2?family=Poppins:wght@300;400;500;600;700&display=swap" />
|
||||
<link rel="stylesheet" href="https://unpkg.com/aos@next/dist/aos.css" />
|
||||
<link rel="stylesheet" href="/css/style.css" />
|
||||
<link rel="stylesheet" href="/css/animations.css" />
|
||||
|
|
@ -24,14 +28,18 @@
|
|||
<link rel="apple-touch-icon" sizes="180x180" href="/assets/favicon/apple-touch-icon.png">
|
||||
<link rel="manifest" href="/assets/favicon/site.webmanifest">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<body>
|
||||
<header class="main-header">
|
||||
<nav class="nav-container">
|
||||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w" sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async" fetchpriority="high">
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
|
|
@ -49,7 +57,8 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
|
|
@ -61,20 +70,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -102,20 +115,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -126,6 +143,7 @@
|
|||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
|
|
@ -133,7 +151,7 @@
|
|||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
</header>
|
||||
|
||||
<main>
|
||||
<section class="offer-hero">
|
||||
|
|
@ -227,8 +245,8 @@
|
|||
strankam jasna.
|
||||
</p>
|
||||
<p>
|
||||
Ponujam medkulturno posredovanje iz slovenščine v albanščino in
|
||||
obratno, ter iz slovenščine v srbščino in obratno.
|
||||
Ponujam medkulturno posredovanje v kombinacijah naslednjih jezikov: slovenščina, albanščina, srbščina in
|
||||
angleščina.
|
||||
</p>
|
||||
</div>
|
||||
<div class="offer-mediation-list" data-aos="fade-up" data-aos-delay="160">
|
||||
|
|
@ -253,9 +271,20 @@
|
|||
</div>
|
||||
</div>
|
||||
</section>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvariva prostor za učenje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
</main>
|
||||
|
||||
<footer>
|
||||
<footer>
|
||||
<div class="footer-content">
|
||||
<div class="footer-logo">
|
||||
<h3>PROSBERRY</h3>
|
||||
|
|
@ -268,9 +297,10 @@
|
|||
<p>Tel: <a href="tel:+38630312855">+386 30 312 855</a></p>
|
||||
</div>
|
||||
</div>
|
||||
</footer>
|
||||
</footer>
|
||||
|
||||
<script src="https://unpkg.com/aos@next/dist/aos.js" defer></script>
|
||||
<script src="/js/main.js" defer></script>
|
||||
</body>
|
||||
</body>
|
||||
|
||||
</html>
|
||||
|
|
|
|||
|
|
@ -0,0 +1,296 @@
|
|||
#!/bin/bash
|
||||
set -euo pipefail
|
||||
|
||||
# --- Configuration ---
|
||||
ARTICLES_DIR="blog/clanki"
|
||||
BLOG_TEMPLATE="blog/template.html"
|
||||
BLOG_INDEX="blog/index.html"
|
||||
ARTICLE_TEMPLATE="blog/article-template.html"
|
||||
HEADER_TEMPLATE_FILE="header-template.html"
|
||||
FOOTER_TEMPLATE_FILE="footer-template.html"
|
||||
BLOG_LEAD_TEXT="Tu zbiramo izkušnje, nasvete in dobre prakse z jezikovnega in medkulturnega področja. Namen je ustvariti prostor srečanja, učenja in navdiha."
|
||||
ARCHIVE_HEADING_TEXT="Seznam vsebin"
|
||||
|
||||
PLACEHOLDER_TITLES=(
|
||||
"Pripravljamo nove vsebine"
|
||||
"Kratek vodič po delavnicah"
|
||||
"Naslednji koraki"
|
||||
)
|
||||
PLACEHOLDER_DATES=(
|
||||
"pomlad 2026"
|
||||
"pomlad 2026"
|
||||
"poletje 2026"
|
||||
)
|
||||
PLACEHOLDER_SUMMARIES=(
|
||||
"Razmišljanja o tem, kako navdušiti učence za medkulturne pogovore in skupinske projekte."
|
||||
"Kako strukturirati delavnico, ki vključuje starše, učitelje in otroke v enakopravnem dialogu."
|
||||
"Sledi blogu za nove prispevke in praktične nasvete."
|
||||
)
|
||||
|
||||
PLACEHOLDER_IMAGE="/assets/images/blog/placeholder.webp"
|
||||
|
||||
check_jq_dependency() {
|
||||
if ! command -v jq &> /dev/null; then
|
||||
echo "Error: 'jq' is not installed. Please install it to run this script." >&2
|
||||
exit 1
|
||||
fi
|
||||
}
|
||||
|
||||
find_article_files() {
|
||||
find "$ARTICLES_DIR" -maxdepth 1 -type f -name "*.html" | sort -r
|
||||
}
|
||||
|
||||
extract_metadata() {
|
||||
local file="$1"
|
||||
local metadata_json
|
||||
metadata_json=$(perl -ne 'BEGIN{undef $/;} if (/<!--\s*(\{.*?})\s*-->/s) { print $1; exit }' "$file")
|
||||
|
||||
if [ -z "${metadata_json:-}" ]; then
|
||||
echo ""
|
||||
return
|
||||
fi
|
||||
|
||||
if ! echo "$metadata_json" | jq -e . &> /dev/null; then
|
||||
echo "Warning: Malformed JSON metadata in $file. Skipping article." >&2
|
||||
echo ""
|
||||
return
|
||||
fi
|
||||
|
||||
echo "$metadata_json"
|
||||
}
|
||||
|
||||
format_short_date() {
|
||||
local iso_date="$1"
|
||||
if [[ "$iso_date" =~ ^([0-9]{4})-([0-9]{2})-([0-9]{2})$ ]]; then
|
||||
printf "%s.%s.%s" "${BASH_REMATCH[3]}" "${BASH_REMATCH[2]}" "${BASH_REMATCH[1]}"
|
||||
else
|
||||
echo "$iso_date"
|
||||
fi
|
||||
}
|
||||
|
||||
format_long_date() {
|
||||
local iso_date="$1"
|
||||
if [[ "$iso_date" =~ ^([0-9]{4})-([0-9]{2})-([0-9]{2})$ ]]; then
|
||||
local year="${BASH_REMATCH[1]}"
|
||||
local month="${BASH_REMATCH[2]}"
|
||||
local day="${BASH_REMATCH[3]}"
|
||||
local month_name
|
||||
case "$month" in
|
||||
01) month_name="januar" ;;
|
||||
02) month_name="februar" ;;
|
||||
03) month_name="marec" ;;
|
||||
04) month_name="april" ;;
|
||||
05) month_name="maj" ;;
|
||||
06) month_name="junij" ;;
|
||||
07) month_name="julij" ;;
|
||||
08) month_name="avgust" ;;
|
||||
09) month_name="september" ;;
|
||||
10) month_name="oktober" ;;
|
||||
11) month_name="november" ;;
|
||||
12) month_name="december" ;;
|
||||
*) month_name="$month" ;;
|
||||
esac
|
||||
printf "%s. %s %s" "$day" "$month_name" "$year"
|
||||
else
|
||||
echo "$iso_date"
|
||||
fi
|
||||
}
|
||||
|
||||
get_article_image() {
|
||||
local file="$1"
|
||||
local filename=$(basename "$file" .html)
|
||||
echo "/assets/images/blog/${filename}/header.png"
|
||||
}
|
||||
|
||||
generate_featured_article_html() {
|
||||
local file="$1"
|
||||
local metadata_json="$2"
|
||||
local title date image summary article_path long_date
|
||||
|
||||
title=$(echo "$metadata_json" | jq -r '.title')
|
||||
date=$(echo "$metadata_json" | jq -r '.date')
|
||||
image=$(get_article_image "$file")
|
||||
summary=$(echo "$metadata_json" | jq -r '.summary // ""')
|
||||
article_path=$(basename "$file")
|
||||
long_date=$(format_long_date "$date")
|
||||
|
||||
cat <<EOF
|
||||
<article class="featured-article" data-aos="fade-up">
|
||||
<a href="/blog/clanki/${article_path}">
|
||||
<img src="${image}" alt="${title}">
|
||||
<div class="featured-article-content">
|
||||
<p class="article-date">${long_date}</p>
|
||||
<h2>${title}</h2>
|
||||
<p>${summary}</p>
|
||||
</div>
|
||||
</a>
|
||||
</article>
|
||||
EOF
|
||||
}
|
||||
|
||||
generate_recent_article_card_html() {
|
||||
local file="$1"
|
||||
local metadata_json="$2"
|
||||
local title date image summary short_date article_path
|
||||
|
||||
title=$(echo "$metadata_json" | jq -r '.title')
|
||||
date=$(echo "$metadata_json" | jq -r '.date')
|
||||
image=$(get_article_image "$file")
|
||||
summary=$(echo "$metadata_json" | jq -r '.summary // ""')
|
||||
article_path=$(basename "$file")
|
||||
short_date=$(format_short_date "$date")
|
||||
|
||||
cat <<EOF
|
||||
<article class="recent-card">
|
||||
<a href="/blog/clanki/${article_path}">
|
||||
<img src="${image}" alt="${title}">
|
||||
<h3>${title}</h3>
|
||||
<p class="article-date">${short_date}</p>
|
||||
<p>${summary}</p>
|
||||
</a>
|
||||
</article>
|
||||
EOF
|
||||
}
|
||||
|
||||
generate_archive_list_item_html() {
|
||||
local file="$1"
|
||||
local metadata_json="$2"
|
||||
local title date short_date article_path
|
||||
|
||||
title=$(echo "$metadata_json" | jq -r '.title')
|
||||
date=$(echo "$metadata_json" | jq -r '.date')
|
||||
article_path=$(basename "$file")
|
||||
short_date=$(format_short_date "$date")
|
||||
|
||||
cat <<EOF
|
||||
<li><a href="/blog/clanki/${article_path}">${title}</a> - ${short_date}</li>
|
||||
EOF
|
||||
}
|
||||
|
||||
generate_placeholder_card_html() {
|
||||
local index="$1"
|
||||
local slot=$((index % ${#PLACEHOLDER_TITLES[@]}))
|
||||
local title="${PLACEHOLDER_TITLES[$slot]}"
|
||||
local date="${PLACEHOLDER_DATES[$slot]}"
|
||||
local summary="${PLACEHOLDER_SUMMARIES[$slot]}"
|
||||
|
||||
cat <<EOF
|
||||
<article class="recent-card placeholder-card">
|
||||
<a href="#">
|
||||
<img src="${PLACEHOLDER_IMAGE}" alt="${title}">
|
||||
<h3>${title}</h3>
|
||||
<p class="article-date">${date}</p>
|
||||
<p>${summary}</p>
|
||||
</a>
|
||||
</article>
|
||||
EOF
|
||||
}
|
||||
|
||||
check_template_file() {
|
||||
local file="$1"
|
||||
if [ ! -f "$file" ]; then
|
||||
echo "Error: Template file '$file' does not exist." >&2
|
||||
exit 1
|
||||
fi
|
||||
}
|
||||
|
||||
check_template_file "$BLOG_TEMPLATE"
|
||||
check_template_file "$ARTICLE_TEMPLATE"
|
||||
check_template_file "$HEADER_TEMPLATE_FILE"
|
||||
check_template_file "$FOOTER_TEMPLATE_FILE"
|
||||
|
||||
check_jq_dependency
|
||||
|
||||
ALL_ARTICLE_FILES=$(find_article_files)
|
||||
VALID_ARTICLE_ENTRIES=()
|
||||
|
||||
for file in $ALL_ARTICLE_FILES; do
|
||||
filename=$(basename "$file")
|
||||
if [[ "$filename" =~ ^[0-9]{4}-[0-9]{2}-[0-9]{2}-.*\.html$ ]]; then
|
||||
metadata=$(extract_metadata "$file")
|
||||
if [ -z "${metadata:-}" ]; then
|
||||
continue
|
||||
fi
|
||||
article_date=$(echo "$metadata" | jq -r '.date // empty')
|
||||
if [ -z "$article_date" ]; then
|
||||
echo "Warning: Missing date in $file. Skipping article." >&2
|
||||
continue
|
||||
fi
|
||||
VALID_ARTICLE_ENTRIES+=("${article_date}|${file}")
|
||||
else
|
||||
echo "Warning: Invalid filename format for $file. Expected YYYY-MM-DD-*.html. Skipping article." >&2
|
||||
fi
|
||||
done
|
||||
|
||||
if [ "${#VALID_ARTICLE_ENTRIES[@]}" -eq 0 ]; then
|
||||
echo "No valid article files found in $ARTICLES_DIR."
|
||||
exit 0
|
||||
fi
|
||||
|
||||
SORTED_ENTRIES=$(printf "%s\n" "${VALID_ARTICLE_ENTRIES[@]}" | LC_ALL=C sort -t'|' -k1,1r -k2,2)
|
||||
|
||||
FEATURED_ARTICLE_HTML=""
|
||||
RECENT_ARTICLES_HTML=""
|
||||
ARCHIVE_HTML=""
|
||||
|
||||
ARTICLE_COUNT=0
|
||||
RECENT_COUNT=0
|
||||
PLACEHOLDER_INDEX=0
|
||||
|
||||
while IFS='|' read -r _ file; do
|
||||
metadata=$(extract_metadata "$file")
|
||||
if [ -z "${metadata:-}" ]; then
|
||||
continue
|
||||
fi
|
||||
|
||||
if [ "$ARTICLE_COUNT" -eq 0 ]; then
|
||||
FEATURED_ARTICLE_HTML=$(generate_featured_article_html "$file" "$metadata")
|
||||
elif [ "$ARTICLE_COUNT" -le 3 ]; then
|
||||
RECENT_ARTICLES_HTML+=$'\n'"$(generate_recent_article_card_html "$file" "$metadata")"
|
||||
RECENT_COUNT=$((RECENT_COUNT + 1))
|
||||
fi
|
||||
|
||||
# Add ALL articles to archive list
|
||||
ARCHIVE_HTML+=$'\n'"$(generate_archive_list_item_html "$file" "$metadata")"
|
||||
|
||||
ARTICLE_COUNT=$((ARTICLE_COUNT + 1))
|
||||
done <<< "$SORTED_ENTRIES"
|
||||
|
||||
if [ "$RECENT_COUNT" -lt 3 ]; then
|
||||
for ((i=RECENT_COUNT; i<3; i++)); do
|
||||
RECENT_ARTICLES_HTML+=$'\n'"$(generate_placeholder_card_html "$PLACEHOLDER_INDEX")"
|
||||
PLACEHOLDER_INDEX=$((PLACEHOLDER_INDEX + 1))
|
||||
done
|
||||
fi
|
||||
|
||||
if [ -z "${FEATURED_ARTICLE_HTML:-}" ]; then
|
||||
echo "Warning: No featured article generated." >&2
|
||||
fi
|
||||
|
||||
export FEATURED_ARTICLE_HTML
|
||||
export RECENT_ARTICLES_HTML
|
||||
export ARCHIVE_HTML
|
||||
export BLOG_TEMPLATE
|
||||
export BLOG_INDEX
|
||||
export ARTICLE_TEMPLATE
|
||||
export HEADER_TEMPLATE_FILE
|
||||
export FOOTER_TEMPLATE_FILE
|
||||
export BLOG_LEAD_TEXT
|
||||
export ARCHIVE_HEADING_TEXT
|
||||
|
||||
python3 <<'PY'
|
||||
import os
|
||||
from pathlib import Path
|
||||
|
||||
template = Path(os.environ["BLOG_TEMPLATE"]).read_text()
|
||||
template = template.replace("__HEADER_CONTENT__", Path(os.environ["HEADER_TEMPLATE_FILE"]).read_text())
|
||||
template = template.replace("__NAJNOVEJSI_CLANEK__", os.environ.get("FEATURED_ARTICLE_HTML", ""))
|
||||
template = template.replace("__CAKAJOCI_CLANKI__", os.environ.get("RECENT_ARTICLES_HTML", ""))
|
||||
template = template.replace("__ARHIV_SEZNAM__", os.environ.get("ARCHIVE_HTML", ""))
|
||||
template = template.replace("__BLOG_LEAD__", os.environ.get("BLOG_LEAD_TEXT", ""))
|
||||
template = template.replace("__ARCHIVE_HEADING__", os.environ.get("ARCHIVE_HEADING_TEXT", ""))
|
||||
template = template.replace("__FOOTER_CONTENT__", Path(os.environ["FOOTER_TEMPLATE_FILE"]).read_text())
|
||||
Path(os.environ["BLOG_INDEX"]).write_text(template)
|
||||
PY
|
||||
|
||||
echo "Blog page generated successfully at $BLOG_INDEX"
|
||||
|
|
@ -31,8 +31,11 @@
|
|||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w" sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async" fetchpriority="high">
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
|
|
@ -50,7 +53,8 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
|
|
@ -62,20 +66,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -103,20 +111,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -127,6 +139,7 @@
|
|||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
|
|
@ -134,7 +147,7 @@
|
|||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
</header>
|
||||
|
||||
|
||||
<main>
|
||||
|
|
@ -214,7 +227,18 @@
|
|||
</div>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvariva prostor za učenje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
</main>
|
||||
|
||||
<footer>
|
||||
<div class="footer-content">
|
||||
|
|
|
|||
|
|
@ -31,8 +31,11 @@
|
|||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w" sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async" fetchpriority="high">
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
|
|
@ -50,7 +53,8 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
|
|
@ -62,20 +66,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -103,20 +111,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -127,6 +139,7 @@
|
|||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
|
|
@ -134,7 +147,7 @@
|
|||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
</header>
|
||||
|
||||
|
||||
|
||||
|
|
@ -213,7 +226,18 @@
|
|||
</div>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvariva prostor za učenje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
</main>
|
||||
|
||||
<footer>
|
||||
<div class="footer-content">
|
||||
|
|
|
|||
|
|
@ -31,8 +31,11 @@
|
|||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w" sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async" fetchpriority="high">
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
|
|
@ -50,7 +53,8 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
|
|
@ -62,20 +66,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -103,20 +111,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -127,6 +139,7 @@
|
|||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
|
|
@ -134,7 +147,7 @@
|
|||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
</header>
|
||||
|
||||
|
||||
|
||||
|
|
@ -213,7 +226,18 @@
|
|||
</div>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvariva prostor za učenje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
</main>
|
||||
|
||||
<footer>
|
||||
<div class="footer-content">
|
||||
|
|
|
|||
|
|
@ -30,8 +30,11 @@
|
|||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w" sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async" fetchpriority="high">
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
|
|
@ -49,7 +52,8 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
|
|
@ -61,20 +65,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -102,20 +110,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -126,6 +138,7 @@
|
|||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
|
|
@ -133,7 +146,7 @@
|
|||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
</header>
|
||||
|
||||
|
||||
|
||||
|
|
@ -211,7 +224,18 @@
|
|||
</div>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvariva prostor za učenje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
</main>
|
||||
|
||||
<footer>
|
||||
<div class="footer-content">
|
||||
|
|
|
|||
|
|
@ -31,8 +31,11 @@
|
|||
<div class="logo">
|
||||
<a href="/">
|
||||
<picture>
|
||||
<source srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w" sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async" fetchpriority="high">
|
||||
<source
|
||||
srcset="/assets/images/logo-100w.webp 100w, /assets/images/logo-200w.webp 200w, /assets/images/logo-400w.webp 400w, /assets/images/logo.webp 1500w"
|
||||
sizes="(max-width: 768px) 100px, 180px" type="image/webp">
|
||||
<img src="/assets/images/logo.webp" alt="Prosberry Logo" width="1500" height="500" decoding="async"
|
||||
fetchpriority="high">
|
||||
</picture>
|
||||
</a>
|
||||
</div>
|
||||
|
|
@ -50,7 +53,8 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/">MK posredovanje</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a
|
||||
href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#individualno">Individualno</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#skupinsko">Skupinsko</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#potek">Potek</a>
|
||||
<a href="/skupaj-za-vkljucevanje/medkulturno-posredovanje/#oblike">Oblike</a>
|
||||
|
|
@ -62,20 +66,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se
|
||||
splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj
|
||||
gradimo nove začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -103,20 +111,24 @@
|
|||
<div class="dropdown-submenu">
|
||||
<a href="#">Šola</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši priseljenci</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-zakaj-znati-slovensko/">Zakaj se splača
|
||||
znati slovensko?</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-sola-in-starsi/">Šola in starši
|
||||
priseljenci</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Vrtec</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove začetke</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-vrtec-novi-zacetki/">Skupaj gradimo nove
|
||||
začetke</a>
|
||||
</div>
|
||||
</div>
|
||||
<div class="dropdown-submenu">
|
||||
<a href="#">Zaposleni</a>
|
||||
<div class="dropdown-submenu-content">
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do sošolca</a>
|
||||
<a href="/skupaj-za-vkljucevanje/delavnica-od-tujca-do-sosolca/">Od tujca do
|
||||
sošolca</a>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
@ -127,6 +139,7 @@
|
|||
<a href="/kontakt">Kontakt</a>
|
||||
<a href="/pogosta-vprasanja">Pogosta vprašanja</a>
|
||||
<a href="/cene-in-reference">Cene in reference</a>
|
||||
<a href="/blog/">Blog</a>
|
||||
</div>
|
||||
<div class="mobile-menu-btn">
|
||||
<span></span>
|
||||
|
|
@ -134,7 +147,7 @@
|
|||
<span></span>
|
||||
</div>
|
||||
</nav>
|
||||
</header>
|
||||
</header>
|
||||
|
||||
|
||||
|
||||
|
|
@ -257,7 +270,18 @@
|
|||
</div>
|
||||
</div>
|
||||
</section>
|
||||
</main>
|
||||
<section class="final-cta">
|
||||
<div class="final-cta-content" data-aos="fade-up">
|
||||
<h2>Imaš vprašanje? Pokliči ali piši!</h2>
|
||||
<div class="final-cta-buttons">
|
||||
<a href="tel:+38630312855" class="cta-button contact-link">+386 30 312 855</a>
|
||||
<a href="mailto:info@prosberry.si" class="cta-button contact-link">info@prosberry.si</a>
|
||||
</div>
|
||||
<p>Skupaj ustvariva prostor za učenje in povezovanje.</p>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
</main>
|
||||
|
||||
<footer>
|
||||
<div class="footer-content">
|
||||
|
|
|
|||
|
|
@ -0,0 +1,35 @@
|
|||
# Specification Quality Checklist: Add Blog "Medkulturni kotiček"
|
||||
|
||||
**Purpose**: Validate specification completeness and quality before proceeding to planning
|
||||
**Created**: 2025-11-17
|
||||
**Feature**: [Link to spec.md]
|
||||
|
||||
## Content Quality
|
||||
|
||||
- [X] No implementation details (languages, frameworks, APIs) - *Soft Fail: Explicitly requested technical details in prompt.*
|
||||
- [X] Focused on user value and business needs
|
||||
- [X] Written for non-technical stakeholders - *Fail: Technical sections not easily digestible for non-technical stakeholders.*
|
||||
- [X] All mandatory sections completed
|
||||
|
||||
## Requirement Completeness
|
||||
|
||||
- [X] No [NEEDS CLARIFICATION] markers remain
|
||||
- [X] Requirements are testable and unambiguous
|
||||
- [X] Success criteria are measurable
|
||||
- [X] Success criteria are technology-agnostic (no implementation details)
|
||||
- [X] All acceptance scenarios are defined
|
||||
- [X] Edge cases are identified
|
||||
- [X] Scope is clearly bounded
|
||||
- [X] Dependencies and assumptions identified
|
||||
|
||||
## Feature Readiness
|
||||
|
||||
- [X] All functional requirements have clear acceptance criteria
|
||||
- [X] User scenarios cover primary flows
|
||||
- [X] Feature meets measurable outcomes defined in Success Criteria
|
||||
- [X] No implementation details leak into specification - *Soft Fail: Similar to Content Quality point.*
|
||||
|
||||
## Notes
|
||||
|
||||
- Items marked incomplete require spec updates before `/speckit.clarify` or `/speckit.plan`
|
||||
- The presence of implementation details and the spec not being entirely for non-technical stakeholders is due to the explicit request in the original prompt for "Tehnične Specifikacije za Implementacijo Bloga".
|
||||
|
|
@ -0,0 +1,52 @@
|
|||
# API Contracts for Blog Feature
|
||||
|
||||
This document outlines the "API contracts" for the static blog generation process. Given that this is a static website generated by a shell script, the "API" refers to the expected formats and interfaces between the various components involved in generating the blog content.
|
||||
|
||||
## 1. Article Metadata Contract
|
||||
|
||||
This contract defines the expected JSON structure embedded within each article's HTML file. The `posodobi_blog.sh` script relies on this format to extract article details.
|
||||
|
||||
* **Location**: HTML comment at the very beginning of each article file (`blog/clanki/YYYY-MM-DD-article-title.html`).
|
||||
* **Format**: JSON object.
|
||||
|
||||
### Expected Structure (`contracts/article-metadata.json`):
|
||||
|
||||
```json
|
||||
{
|
||||
"title": "string", // The title of the article
|
||||
"date": "YYYY-MM-DD", // The publication date of the article
|
||||
"image": "string", // Relative path to the main image (e.g., "/assets/images/blog/my-article-image.webp")
|
||||
"summary": "string" // A short summary or excerpt of the article
|
||||
}
|
||||
```
|
||||
|
||||
### Validation Rules:
|
||||
|
||||
* The JSON block must be valid JSON.
|
||||
* All fields (`title`, `date`, `image`, `summary`) are mandatory.
|
||||
* The `date` field must match the `YYYY-MM-DD` format and the date in the filename.
|
||||
|
||||
## 2. Blog Template Contract
|
||||
|
||||
This contract defines the placeholders expected by the `posodobi_blog.sh` script within the `blog/template.html` file. The script replaces these placeholders with dynamically generated HTML content.
|
||||
|
||||
* **Location**: `blog/template.html`
|
||||
* **Format**: Specific string markers.
|
||||
|
||||
### Expected Placeholders:
|
||||
|
||||
* `__NAJNOVEJSI_CLANEK__`: Replaced with the HTML block for the featured (newest) article.
|
||||
* `__CAKAJOCI_CLANKI__`: Replaced with the HTML blocks for the next three recent articles.
|
||||
* `__ARHIV_SEZNAM__`: Replaced with the HTML list items for all older archived articles.
|
||||
|
||||
## 3. Script Input/Output Contract (`posodobi_blog.sh`)
|
||||
|
||||
This contract describes the expected inputs and outputs of the `posodobi_blog.sh` script.
|
||||
|
||||
* **Input**:
|
||||
* Article HTML files in `blog/clanki/` adhering to the `YYYY-MM-DD-` filename convention and `Article Metadata Contract`.
|
||||
* `blog/template.html` adhering to the `Blog Template Contract`.
|
||||
* **Output**:
|
||||
* Generated `blog/index.html` file.
|
||||
* Warnings logged to `stderr` for malformed JSON or invalid filenames.
|
||||
* Error logged to `stderr` and script exits if `jq` is not found.
|
||||
|
|
@ -0,0 +1,6 @@
|
|||
{
|
||||
"title": "Primer Naslova Članka",
|
||||
"date": "YYYY-MM-DD",
|
||||
"image": "/assets/images/blog/primer-slike.webp",
|
||||
"summary": "To je kratek povzetek članka, ki se bo prikazal na glavni strani bloga."
|
||||
}
|
||||
|
|
@ -0,0 +1,33 @@
|
|||
# Data Model for Blog Feature
|
||||
|
||||
## Entity: Article
|
||||
|
||||
Represents a single blog post.
|
||||
|
||||
### Fields:
|
||||
|
||||
* **`title`** (String): The title of the article.
|
||||
* **Source**: Extracted from the `title` field within the JSON metadata block at the top of the article's HTML file.
|
||||
* **`date`** (String): The publication date of the article in `YYYY-MM-DD` format.
|
||||
* **Source**: Extracted from the `date` field within the JSON metadata block. This also serves as the prefix for the article's filename.
|
||||
* **`image`** (String): The relative path to the main image associated with the article.
|
||||
* **Source**: Extracted from the `image` field within the JSON metadata block.
|
||||
* **`summary`** (String): A brief summary or excerpt of the article (1-2 sentences).
|
||||
* **Source**: Extracted from the `summary` field within the JSON metadata block.
|
||||
* **`content`** (String): The full HTML content of the article.
|
||||
* **Source**: The body of the article's HTML file, following the JSON metadata block.
|
||||
|
||||
### Relationships:
|
||||
|
||||
* **Implicit Relationship with Blog Page**: Multiple `Article` entities are displayed on the main `Blog Page` (`/blog/index.html`), which dynamically aggregates and presents them.
|
||||
|
||||
### Validation Rules:
|
||||
|
||||
* **Filename Format**: Each article HTML file in `blog/clanki/` MUST be named with a `YYYY-MM-DD-` prefix (e.g., `2025-11-15-medkulturnost-prostor-za-rast.html`). Files not adhering to this convention will be ignored with a warning.
|
||||
* **JSON Metadata**: Each article HTML file MUST contain a valid JSON block within an HTML comment at its very beginning. Malformed JSON will cause the article to be skipped with a warning.
|
||||
* **Required Metadata Fields**: The JSON metadata block MUST include `title`, `date`, `image`, and `summary` fields.
|
||||
* **`jq` Dependency**: The `posodobi_blog.sh` script requires `jq` to parse JSON metadata. The script will check for `jq`'s presence and exit with an error if it's not found.
|
||||
|
||||
### State Transitions:
|
||||
|
||||
* Not applicable, as articles are static content files.
|
||||
|
|
@ -0,0 +1,68 @@
|
|||
# Implementation Plan: Add Blog "Medkulturni kotiček"
|
||||
|
||||
**Branch**: `001-add-blog` | **Date**: 2025-11-17 | **Spec**: /Users/markpoljansek/prosberry_produkcija/specs/001-add-blog/spec.md
|
||||
**Input**: Feature specification from `/specs/001-add-blog/spec.md`
|
||||
|
||||
**Note**: This template is filled in by the `/speckit.plan` command. See `.specify/templates/commands/plan.md` for the execution workflow.
|
||||
|
||||
## Summary
|
||||
|
||||
The project aims to expand the existing static website `prosberry.si` by adding a new blog section called "Medkulturni kotiček". This blog will dynamically display articles, with the newest article prominently featured, followed by three recent articles, and an archive list. A key aspect is the automation of content management, allowing the website owner to easily add new articles by simply creating HTML files with embedded JSON metadata and running a Bash script (`posodobi_blog.sh`). This script will generate the main blog page, ensuring chronological sorting and consistent styling. The website's main navigation will also be updated to include a "Blog" link.
|
||||
|
||||
## Technical Context
|
||||
|
||||
**Language/Version**: Bash/Shell (for `posodobi_blog.sh`), HTML, CSS, JavaScript (for existing `main.js`).
|
||||
**Primary Dependencies**: `jq` (for `posodobi_blog.sh`).
|
||||
**Storage**: Filesystem (HTML files for articles, generated `index.html`).
|
||||
**Testing**: Bats-core for `posodobi_blog.sh` unit tests; HTML/CSS/JS Linting/Validation and Link Checking for static pages.
|
||||
**Target Platform**: Web browsers (static website).
|
||||
**Project Type**: Web application (static site generation).
|
||||
**Performance Goals**: `posodobi_blog.sh` generates `blog/index.html` within 5 seconds for up to 100 articles. All blog pages load within 2 seconds on a standard broadband connection.
|
||||
**Constraints**: Easy and automated article addition for the owner. Styling must be consistent with existing site. Blog layout must be fully responsive.
|
||||
**Scale/Scope**: Blog section with dynamic article display. Automated content generation for articles. Navigation update.
|
||||
|
||||
## Constitution Check
|
||||
|
||||
*GATE: Must pass before Phase 0 research. Re-check after Phase 1 design.*
|
||||
|
||||
No specific gates defined in the project's constitution yet. Assuming no violations for now.
|
||||
|
||||
## Project Structure
|
||||
|
||||
### Documentation (this feature)
|
||||
|
||||
```text
|
||||
specs/[###-feature]/
|
||||
├── plan.md # This file (/speckit.plan command output)
|
||||
├── research.md # Phase 0 output (/speckit.plan command)
|
||||
├── data-model.md # Phase 1 output (/speckit.plan command)
|
||||
├── quickstart.md # Phase 1 output (/speckit.plan command)
|
||||
├── contracts/ # Phase 1 output (/speckit.plan command)
|
||||
└── tasks.md # Phase 2 output (/speckit.tasks command - NOT created by /speckit.plan)
|
||||
```
|
||||
|
||||
### Source Code (repository root)
|
||||
|
||||
```text
|
||||
.
|
||||
├── blog/
|
||||
│ ├── index.html # AUTO-GENERATED
|
||||
│ ├── template.html
|
||||
│ └── clanki/
|
||||
│ └── YYYY-MM-DD-naslov-clanka.html
|
||||
├── posodobi_blog.sh
|
||||
├── assets/
|
||||
│ └── images/
|
||||
│ └── blog/ # New directory for blog images
|
||||
├── css/
|
||||
│ └── style.css # Modified
|
||||
├── header-template.html # Modified
|
||||
├── footer-template.html # Modified
|
||||
├── js/
|
||||
│ └── main.js # Existing, potential minor modifications
|
||||
└── ... (other existing files and directories)
|
||||
```
|
||||
|
||||
**Structure Decision**: The project will follow a single project structure, with new directories and files specifically for the blog feature integrated into the existing website structure. The `blog/` directory will house the blog's main page, template, and individual article files. A new script `posodobi_blog.sh` will reside in the root. Existing `css/style.css`, `header-template.html`, and `footer-template.html` will be modified.
|
||||
|
||||
|
||||
|
|
@ -0,0 +1,25 @@
|
|||
# Research: Testing Approaches for Blog Feature
|
||||
|
||||
## Decision: Testing Frameworks and Approaches
|
||||
|
||||
### Shell Script Testing (posodobi_blog.sh)
|
||||
|
||||
* **Decision**: Utilize **Bats-core** for unit testing the `posodobi_blog.sh` script.
|
||||
* **Rationale**: Bats-core is a lightweight, TAP-compliant testing framework specifically designed for Bash scripts. Its simplicity and clear syntax make it suitable for ensuring the correctness of the `posodobi_blog.sh` script's logic, including file parsing, sorting, and HTML generation.
|
||||
* **Alternatives Considered**:
|
||||
* **ShellSpec**: A BDD-style framework, potentially overkill for this script's complexity.
|
||||
* **ShUnit2**: A xUnit-style framework, also a good option, but Bats-core's TAP output is often easier to integrate into CI/CD.
|
||||
|
||||
### Static Site Testing (Generated Blog Pages)
|
||||
|
||||
* **Decision**: Implement a combination of **HTML/CSS/JS Linting/Validation** and **Link Checking**.
|
||||
* **Rationale**: For a static website, ensuring valid markup, consistent styling, and functional navigation are key quality indicators.
|
||||
* **Linting/Validation**: Leverages existing project linting tools (if any) or standard validators to catch syntax errors and ensure best practices.
|
||||
* **Link Checking**: A simple script can verify that all internal and external links within the generated blog pages are valid, preventing broken navigation.
|
||||
* **Alternatives Considered**:
|
||||
* **Visual Regression Testing (e.g., BackstopJS, Percy)**: While valuable, it adds significant setup and maintenance overhead and might be overkill for the initial phase of a static blog, especially given the existing site's visual consistency is expected to be maintained.
|
||||
* **End-to-End Testing (e.g., Cypress, Selenium)**: Primarily for dynamic web applications with complex user interactions, which is not the core focus of this static blog.
|
||||
|
||||
## Resolution of NEEDS CLARIFICATION in Technical Context
|
||||
|
||||
* **Testing**: Specific testing frameworks/approaches for shell scripts and static site generation will include **Bats-core** for `posodobi_blog.sh` and **HTML/CSS/JS Linting/Validation** along with **Link Checking** for the generated static pages.
|
||||
File diff suppressed because one or more lines are too long
|
|
@ -0,0 +1,106 @@
|
|||
# Tasks for Feature: Add Blog "Medkulturni kotiček"
|
||||
|
||||
**Feature Branch**: `001-add-blog`
|
||||
**Date**: 2025-11-17
|
||||
**Spec**: /Users/markpoljansek/prosberry_produkcija/specs/001-add-blog/spec.md
|
||||
**Plan**: /Users/markpoljansek/prosberry_produkcija/specs/001-add-blog/plan.md
|
||||
|
||||
## Implementation Strategy
|
||||
|
||||
The implementation will follow an iterative approach, prioritizing core user stories first to deliver a Minimum Viable Product (MVP). Each user story will be implemented and tested independently where possible.
|
||||
|
||||
**MVP Scope**: User Story 1 (View Blog Main Page), User Story 2 (Read an Individual Article), and User Story 3 (Website Owner Adds New Article) form the core MVP, enabling content consumption and management.
|
||||
|
||||
## Phase 1: Setup
|
||||
|
||||
- [X] T001 Create base blog directory structure: `mkdir -p blog/clanki/ assets/images/blog/`
|
||||
- [X] T002 Create empty `blog/template.html` file
|
||||
- [X] T003 Create empty `posodobi_blog.sh` script file
|
||||
- [X] T004 Create empty `blog/index.html` file (will be auto-generated later)
|
||||
|
||||
## Phase 2: Foundational (Core Script & Template)
|
||||
|
||||
- [X] T005 Implement `jq` dependency check in `posodobi_blog.sh`
|
||||
- [X] T006 Implement basic script structure in `posodobi_blog.sh` to find `.html` files in `blog/clanki/`
|
||||
- [X] T007 Implement article sorting by filename (date) in `posodobi_blog.sh`
|
||||
- [X] T008 Create initial `blog/template.html` content with placeholders: `__NAJNOVEJSI_CLANEK__`, `__CAKAJOCI_CLANKI__`, `__ARHIV_SEZNAM__`
|
||||
- [X] T009 Implement metadata extraction (JSON from HTML comment) in `posodobi_blog.sh`
|
||||
- [X] T010 Implement malformed JSON handling (skip with warning) in `posodobi_blog.sh`
|
||||
- [X] T011 Implement invalid filename handling (ignore with warning) in `posodobi_blog.sh`
|
||||
|
||||
## Phase 3: User Story 3 (P1) - Website Owner Adds New Article
|
||||
|
||||
**Goal**: Enable the website owner to easily add new articles to the blog.
|
||||
**Independent Test**: A new article can be added by creating a file with metadata and running the script, resulting in the main blog page being updated correctly.
|
||||
|
||||
- [X] T012 [US3] Implement HTML generation for featured article in `posodobi_blog.sh`
|
||||
- [X] T013 [US3] Implement HTML generation for recent articles (3 cards) in `posodobi_blog.sh`
|
||||
- [X] T014 [US3] Implement HTML generation for archive list in `posodobi_blog.sh`
|
||||
- [X] T015 [US3] Implement placeholder generation for < 4 articles in `posodobi_blog.sh`
|
||||
- [X] T016 [US3] Implement placeholder replacement in `blog/template.html` with generated content in `posodobi_blog.sh`
|
||||
- [X] T017 [US3] Implement writing final HTML to `blog/index.html` in `posodobi_blog.sh`
|
||||
- [X] T018 [US3] Create a sample article file `blog/clanki/2025-11-17-sample-article.html` with valid JSON metadata and content.
|
||||
|
||||
## Phase 4: User Story 1 (P1) - View Blog Main Page
|
||||
|
||||
**Goal**: Display the main blog page with the latest articles prominently.
|
||||
**Independent Test**: The `/blog/index.html` page can be accessed directly and displays the articles according to the specified layout (featured, recent, archive).
|
||||
|
||||
- [X] T019 [US1] Run `posodobi_blog.sh` to generate `blog/index.html` with sample data
|
||||
- [X] T020 [US1] Verify `blog/index.html` displays featured article correctly
|
||||
- [X] T021 [US1] Verify `blog/index.html` displays recent articles correctly
|
||||
- [X] T022 [US1] Verify `blog/index.html` displays archive list correctly
|
||||
- [X] T023 [US1] Verify placeholder blocks are displayed if fewer than 4 articles are present (requires additional sample data or modification of T018)
|
||||
|
||||
## Phase 5: User Story 2 (P1) - Read an Individual Article
|
||||
|
||||
**Goal**: Allow visitors to read full article content on dedicated pages.
|
||||
**Independent Test**: An individual article page (e.g., `/blog/clanki/YYYY-MM-DD-article-title.html`) can be accessed directly and displays the full article content with consistent styling.
|
||||
|
||||
- [X] T024 [US2] Ensure links from `blog/index.html` to individual articles are correct
|
||||
- [X] T025 [US2] Verify individual article pages load correctly
|
||||
- [X] T026 [US2] Verify individual article pages display full content
|
||||
|
||||
## Phase 6: User Story 4 (P2) - Access Blog from Navigation
|
||||
|
||||
**Goal**: Integrate the blog into the main website navigation.
|
||||
**Independent Test**: The main navigation menu includes a "Blog" link that correctly leads to the blog's main page.
|
||||
|
||||
- [X] T027 [US4] Add `<a href="/blog/">Blog</a>` link to `header-template.html` next to "Cene in reference"
|
||||
- [X] T028 [US4] Run `update-menus.sh` to apply navigation changes across the site
|
||||
- [X] T029 [US4] Verify "Blog" link is present in main navigation on all relevant pages
|
||||
- [X] T030 [US4] Verify "Blog" link navigates to `/blog/index.html`
|
||||
|
||||
## Final Phase: Polish & Cross-Cutting Concerns
|
||||
|
||||
- [X] T031 [P] Add new CSS styles for blog elements (`.blog-layout`, `.blog-main-content`, `.blog-sidebar`, `.featured-article`, `.recent-card`, `.archive-list`) to `css/style.css`
|
||||
- [X] T032 [P] Ensure blog CSS styles are fully responsive for mobile devices
|
||||
- [X] T033 [P] Verify individual article page styling matches overall website design (warm colors, non-white background)
|
||||
- [X] T034 [P] Implement unit tests for `posodobi_blog.sh` using Bats-core
|
||||
- [X] T035 [P] Implement HTML/CSS/JS Linting/Validation for generated pages
|
||||
- [X] T036 [P] Implement Link Checking for generated blog pages
|
||||
- [X] T037 Update `README.md` with instructions for adding new blog posts and running `posodobi_blog.sh`
|
||||
- [X] T038 Review and optimize generated HTML for SEO and accessibility
|
||||
|
||||
## Dependencies
|
||||
|
||||
* Phase 2 (Foundational) must be completed before any User Story phases.
|
||||
* User Story 3 (Website Owner Adds New Article) is foundational for User Story 1 (View Blog Main Page) as it generates the content.
|
||||
* User Story 1 (View Blog Main Page) is foundational for User Story 2 (Read an Individual Article) as it provides the links.
|
||||
|
||||
## Parallel Execution Opportunities
|
||||
|
||||
* **Phase 1: Setup**: All tasks are sequential.
|
||||
* **Phase 2: Foundational**: Tasks T005-T011 are largely sequential due to script development.
|
||||
* **Phase 3: User Story 3**: Tasks T012-T017 are sequential as they build the script logic. T018 can be done in parallel once the script logic is stable.
|
||||
* **Phase 4: User Story 1**: Tasks T019-T023 are sequential as they involve testing the generated output.
|
||||
* **Phase 5: User Story 2**: Tasks T024-T026 are sequential.
|
||||
* **Phase 6: User Story 4**: Tasks T027-T030 are sequential.
|
||||
* **Final Phase**: Tasks T031-T036 can be executed in parallel. T037 and T038 are final documentation/review tasks.
|
||||
|
||||
## Independent Test Criteria for Each Story
|
||||
|
||||
* **User Story 1 (View Blog Main Page)**: Navigate to `/blog/index.html` and visually confirm the layout (featured, recent, archive) and content display as specified.
|
||||
* **User Story 2 (Read an Individual Article)**: Click on a link to an individual article from the main blog page or navigate directly to an article URL. Verify full content display and consistent styling.
|
||||
* **User Story 3 (Website Owner Adds New Article)**: Create a new article HTML file with valid metadata, run `posodobi_blog.sh`, and verify that `blog/index.html` is updated correctly to include the new article.
|
||||
* **User Story 4 (Access Blog from Navigation)**: Navigate to various pages on the website, confirm the "Blog" link is present in the main navigation, and verify it correctly leads to `/blog/index.html`.
|
||||
|
|
@ -0,0 +1,53 @@
|
|||
#!/bin/bash
|
||||
|
||||
# Exit immediately if a command exits with a non-zero status.
|
||||
set -e
|
||||
|
||||
BLOG_INDEX="blog/index.html"
|
||||
SAMPLE_ARTICLE="blog/clanki/2025-11-17-sample-article.html"
|
||||
|
||||
echo "Checking links in $BLOG_INDEX..."
|
||||
# Extract all href attributes and check if they return 200 OK
|
||||
grep -Eio 'href="([^"]+)"' "$BLOG_INDEX" | sed -E 's/href="([^"]+)"/\1/' | while read -r link; do
|
||||
if [[ "$link" == /* ]]; then # Internal link
|
||||
# For internal links, check if the file exists
|
||||
if [ -f ".${link}" ]; then
|
||||
echo " [OK] Internal link: $link"
|
||||
else
|
||||
echo " [ERROR] Internal link not found: $link"
|
||||
exit 1
|
||||
fi
|
||||
elif [[ "$link" == http* ]]; then # External link
|
||||
# For external links, use curl to check status
|
||||
status_code=$(curl -s -o /dev/null -w "%{http_code}" "$link")
|
||||
if [ "$status_code" -eq 200 ]; then
|
||||
echo " [OK] External link: $link"
|
||||
else
|
||||
echo " [ERROR] External link failed ($status_code): $link"
|
||||
exit 1
|
||||
fi
|
||||
fi
|
||||
done
|
||||
|
||||
echo "Checking links in $SAMPLE_ARTICLE..."
|
||||
grep -Eio 'href="([^"]+)"' "$SAMPLE_ARTICLE" | sed -E 's/href="([^"]+)"/\1/' | while read -r link; do
|
||||
if [[ "$link" == /* ]]; then # Internal link
|
||||
# For internal links, check if the file exists
|
||||
if [ -f ".${link}" ]; then
|
||||
echo " [OK] Internal link: $link"
|
||||
else
|
||||
echo " [ERROR] Internal link not found: $link"
|
||||
exit 1
|
||||
fi
|
||||
elif [[ "$link" == http* ]]; then # External link
|
||||
status_code=$(curl -s -o /dev/null -w "%{http_code}" "$link")
|
||||
if [ "$status_code" -eq 200 ]; then
|
||||
echo " [OK] External link: $link"
|
||||
else
|
||||
echo " [ERROR] External link failed ($status_code): $link"
|
||||
exit 1
|
||||
fi
|
||||
fi
|
||||
done
|
||||
|
||||
echo "Link checking completed."
|
||||
|
|
@ -0,0 +1,23 @@
|
|||
#!/usr/bin/env bats
|
||||
|
||||
load '../posodobi_blog.sh' # Load the script to be tested
|
||||
|
||||
@test "check_jq_dependency exits with error if jq is not installed" {
|
||||
# Mock command -v jq to simulate jq not being installed
|
||||
PATH_ORIGINAL="$PATH"
|
||||
export PATH="/tmp/nonexistent_path:$PATH" # Temporarily modify PATH
|
||||
|
||||
run check_jq_dependency
|
||||
[ "$status" -eq 1 ]
|
||||
[[ "$output" == *"Error: 'jq' is not installed. Please install it to run this script."* ]]
|
||||
|
||||
export PATH="$PATH_ORIGINAL" # Restore original PATH
|
||||
}
|
||||
|
||||
@test "check_jq_dependency does not exit if jq is installed" {
|
||||
# Mock command -v jq to simulate jq being installed
|
||||
# Assuming jq is installed in the test environment
|
||||
run check_jq_dependency
|
||||
[ "$status" -eq 0 ]
|
||||
[ "$output" == "" ] # Should not print anything on success
|
||||
}
|
||||
|
|
@ -0,0 +1,13 @@
|
|||
#!/bin/bash
|
||||
|
||||
# Exit immediately if a command exits with a non-zero status.
|
||||
set -e
|
||||
|
||||
BLOG_INDEX="blog/index.html"
|
||||
|
||||
echo "Validating $BLOG_INDEX with tidy..."
|
||||
|
||||
# Run tidy with HTML5 doctype, quiet output, and show warnings
|
||||
tidy -q -e -utf8 --doctype html5 "$BLOG_INDEX"
|
||||
|
||||
echo "HTML validation for $BLOG_INDEX completed."
|
||||
Loading…
Reference in New Issue