How glazovnick/test_employcity works
Project type and purpose
• This is a static, front-end–only web project that uses Gulp as a build system to compile SCSS, bundle assets, inject HTML partials, and output a ready-to-deploy site into the dist/ folder.
• Purpose: deliver a responsive, interactive landing page (Test_Employcity) hosted on GitHub Pages.
File structure
• app/ – all source files:
• index.html + HTML partials in app/parts/
• JavaScript entry in app/js/app.js
• Images in app/images/
• Styles in app/styles/sass/ broken into config + blocks + UI components
• dist/ – compiled output: HTML, CSS, JS, images, ready to serve.
• gulpfile.js, package.json – define build tasks, dependencies, scripts (npm run dev).
• .bowerrc, .gitignore – configure package management and ignore rules.
README for additional insights
• Lists tech stack: HTML5, CSS3/SCSS, Gulp, responsive layout (Flex/Grid), vanilla JS for animations.
• Notes deployment pipeline: compile → dist/ → push to gh-pages.
• No backend or external services—pure static asset pipeline.
a. Main components:
1. Developer workstation (source code editor, Node.js)
2. Source code repository (GitHub)
3. Gulp build pipeline with tasks (SCSS compiler, HTML injector, minifier, asset copier)
4. Output folder (dist/)
5. Hosting platform (GitHub Pages)
b. Relationships and data flow:
• Developers push/pull to GitHub.
• npm run dev / gulp reads app/ → processes files → writes dist/.
• CI or manual push of dist/ to gh-pages branch → GitHub Pages serves site.
c. Architectural patterns/principles:
• Build pipeline (task runner) pattern
• Modular SCSS architecture (config + blocks + UI components)
• Partial injection for DRY HTML
• Single-page asset bundling (no multi-page routing)
d. Key technologies/frameworks:
• Node.js + npm for dependency management
• Gulp for automation (plugins for Sass, HTML partials, image copying, minification)
• SCSS for style modularity
• Vanilla JS for DOM animations