How sephyron/angelcolberg-bu-1 works
Main Components and Layers
• Frontend Application – This is the heart of the portfolio website. Emphasize:
– The Angular application (located in the “app” folder) that contains app.js, config.js, and different controller files (main.controller.js, contact.controller.js, work.controller.js).
– The “components” folder which includes Angular directives (e.g., for main navigation, footer, responsive navigation, owl slider) and services (for local storage and query management).
– The “views” folder where your HTML templates (pages for home, projects, contact, work, error 404, etc.) are stored.
• Assets and Prototypes – The “assets” folder (and similar copies in “_build” and “images”) houses all the static resources. These include:
– Fonts (e.g. DepartureMono-Regular.otf)
– Style sheets (organized in “styles” and “styles/partials” and “styles/static”) and skins.
– Multiple project prototypes (e.g., “assets/prototypes/cloudon”, “assets/prototypes/fi-gps-?”, “assets/prototypes/unity”) that likely serve as interactive demos.
• Build and Deployment Infrastructure – This layer includes:
– Build tooling with “gulpfile.js”, package.json, and associated configuration files.
– The “_build” folder that contains the final built assets, minified styles, compiled HTML views, and processed JavaScript.
Data Flow and Interactions
• Lifecycle flow from source code to production: sources (app, components, assets, styles, js) → build system (gulp) → output (the _build folder and distribution files).
• Within the application layer, show that the Angular app configuration loads controllers and services, which interact with the views through data binding.
Architectural Patterns & Design Principles
• Follow the Model-View-Controller (MVC) or MVVM pattern common in Angular applications. Indicate clearly the “app” layer (controllers, services) and how the “views” present the data.
• The build process is separated from the runtime application; show the pipeline from source to the production bundle.
• Provide labels for third-party dependencies such as jQuery (which is slated for removal) and AngularJS, along with the legacy libraries in the “js/nonangular” folder.
Relevant Technologies
• AngularJS (with future upgrade in mind), JavaScript (both Angular and non-Angular parts).
• SCSS/CSS for styling (with a modular SCSS structure under “styles”).
• Gulp for build automation and dependency management (along with package.json for npm-managed dependencies).
• Rich multimedia/interactive prototypes that showcase project work.