Sascha Haselhuhn

glanzlicht / MeinWeimar_APP

Official MeinWeimar App

Verified secure showcase
204 Files 2 MB Public size 14 Redacted Dart · PHP · XML · GITIGNORE · YAML · PLIST

Project overview

MeinWeimar_APP is a verified code showcase with 204 visible project entries across 2 top-level modules. The primary detected language is Dart; protected files remain visible in the structure while their contents stay private.

README

MeinWeimar — Flutter App & WordPress Plugin

> Working in Progress · Private portfolio repository · Active development

MeinWeimar is a location-based local platform for residents, students and visitors. This repository intentionally contains only two product parts:

  1. the Flutter consumer app;
  2. the meinweimar-core WordPress plugin that provides the editorial/admin

    3. layer and the REST contract consumed by the app.

The complete public website, WordPress core, databases, private infrastructure and unrelated platform modules are not part of this repository.

MeinWeimar consumer app preview

Why this project is interesting

MeinWeimar combines a mobile/web Flutter client with WordPress used as a structured content and administration backend. The goal is a maintainable product boundary: content, branding, navigation, categories, media and configuration are managed in WordPress and delivered through a versioned REST contract instead of being hardcoded in the Flutter UI.

The project demonstrates work across:

  • Flutter/Dart application architecture for iOS, Android and Web;
  • WordPress plugin architecture with custom post types, taxonomies, admin

    • settings and REST endpoints;

  • localized German/English UI and backend-controlled labels;
  • discovery/list/detail flows for places, services, events, classifieds, jobs

    • and real estate;

  • map, GPS, geocoding, marker and navigation contracts;
  • caching, ETag/config-version handling and offline-safe fallbacks;
  • role-aware account, claim, favorites, moderation and messaging boundaries;
  • automated Flutter tests, PHP/REST contract checks and release builds.

Repository structure

flutter-app/       Flutter consumer application
wordpress-plugin/  meinweimar-core WordPress plugin
screenshots/       Curated portfolio preview only

Current status

This is an active Working in Progress project. The core architecture and many end-to-end flows are implemented and continuously tested. Native device polish, production content, final legal/privacy review and further product modules are still being developed. The repository does not claim to be a finished production release.

Local development

Flutter app

cd flutter-app
flutter pub get
flutter analyze
flutter test
flutter run --dart-define=MW_API_BASE_URL=https://example.test/wp-json/meinweimar/v1

The API base URL and other environment-specific values are supplied at build or run time. No credentials are stored in the repository.

WordPress plugin

Copy wordpress-plugin into a WordPress installation's wp-content/plugins/meinweimar-core directory and activate it in the admin area. The plugin owns the MeinWeimar content types, editorial settings, permissions, REST responses, media/configuration contracts and frontend integration points.

Privacy and repository boundary

This repository is private and is prepared for controlled technical review. Secrets, production database exports, user data, WordPress uploads, private keys and infrastructure configuration must remain outside version control. The public-facing portfolio page uses a separate, redacted presentation layer and does not expose the private repository directly.

For technical reviewers

The most relevant entry points are:

  • flutter-app/lib/core — shared configuration, networking, localization,

    • theme and location contracts;

  • flutter-app/lib/features — consumer-facing product surfaces;
  • flutter-app/lib/repositories — API boundary and data access;
  • wordpress-plugin/includes — plugin services, REST, admin and contracts;
  • wordpress-plugin/assets — admin/frontend integration assets.

MeinWeimar is deliberately presented as an evolving product rather than a finished demo: the repository shows the architectural decisions, the working implementation and the remaining engineering work transparently.

flutter-app/web/index.htmlHTML
<!DOCTYPE html>
<html>
<head>
<!--
If you are serving your web app in a path other than the root, change the
href value below to reflect the base path you are serving from.
The path provided below has to start and end with a slash "/" in order for
it to work correctly.
For more details:
* https://developer.mozilla.org/en-US/docs/Web/HTML/Element/base
This is a placeholder for base href that will be replaced by the value of
the `--base-href` argument provided to `flutter build`.
-->
<base href="$FLUTTER_BASE_HREF">
<meta charset="UTF-8">
<meta content="IE=Edge" http-equiv="X-UA-Compatible">
<meta name="description" content="A new Flutter project.">
<!-- iOS meta tags & icons -->
<meta name="mobile-web-app-capable" content="yes">
<meta name="apple-mobile-web-app-status-bar-style" content="black">
<meta name="apple-mobile-web-app-title" content="consumer_app">
<link rel="apple-touch-icon" href="icons/Icon-192.png">
<!-- Favicon -->
<link rel="icon" type="image/png" href="favicon.png"/>
<title>consumer_app</title>
<link rel="manifest" href="manifest.json">
</head>
<body>
<script>
// Local previews must not keep serving an older Flutter bundle through a
// previously registered service worker. Production hosts keep their
// normal PWA policy; this recovery is deliberately limited to localhost.
//
// Important: load flutter_bootstrap only after the cleanup has completed.
// Loading both scripts in parallel races the unregister/cache deletion and
// can briefly paint an old, empty shell in a WebView.
(function () {
var isLocalPreview = /^(localhost|127\.0\.0\.1)$/.test(location.hostname);
var canUseServiceWorkers = 'serviceWorker' in navigator;
var canUseCaches = 'caches' in window;
// A browser can cache index.html itself before the cleanup script gets
// a chance to unregister an older Flutter worker. A one-time query
// parameter makes the local preview request the current index first;
// it is preserved for hash-based Flutter routes.
if (isLocalPreview && !/[?&]mw_refresh=/.test(location.search)) {
var refreshUrl = new URL(location.href);
refreshUrl.searchParams.set('mw_refresh', String(Date.now()));
location.replace(refreshUrl.toString());
return;
}
function loadFlutter() {
var script = document.createElement('script');
script.src = 'flutter_bootstrap.js';
script.async = true;
document.body.appendChild(script);
}
if (!isLocalPreview || !canUseServiceWorkers) {
loadFlutter();
return;
}
Promise.all([
navigator.serviceWorker.getRegistrations(),
canUseCaches ? caches.keys() : Promise.resolve([]),
]).then(function (result) {
var registrations = result[0];
var cacheKeys = result[1];
var hasStaleRuntime = registrations.length > 0 || cacheKeys.length > 0;
if (!hasStaleRuntime) {
loadFlutter();
return;
}
var unregister = Promise.all(registrations.map(function (registration) {
return registration.unregister();
}));
var clearCaches = canUseCaches
? Promise.all(cacheKeys.map(function (key) {
return caches.delete(key);
}))
: Promise.resolve([]);
return Promise.all([unregister, clearCaches]).then(function () {
location.reload();
});
}).catch(function () {
// A restricted WebView may expose the API but reject the cleanup.
// Starting Flutter is still preferable to leaving a blank document.
loadFlutter();
});
}());
</script>
<!-- MEINWEIMAR_GOOGLE_MAPS_SCRIPT -->
</body>
</html>

Architecture

High-level modules detected from the verified public snapshot. Protected implementation details are intentionally omitted.

flutter-appmodule
wordpress-pluginmodule

Technology stack

DartPHPJavaScriptARBLOCKPBXPROJFlutter / Dart
Dart56.1%
PHP29.4%
JavaScript4.0%
ARB2.9%
LOCK1.7%
PBXPROJ1.7%
CSS1.5%
Markdown0.4%