|
By: Paul S Cilwa |
Posted: 3/17/2026 |
|
Page Views: 22 |
| NamtiraMyWeb wizard completed; platform-wide rename from Organica to Namtira; Namtira landing site created; NamtiraLib distribution packages; automatic site version numbering; section CSS cascade system added. |
| Estimated reading time: 3 minute(s) (706 words) |
NamtiraMyWeb Wizard Completed
Wizard pages completed in this session:
- Page 4: Fonts—heading, body, and code font selectors with live preview labels
- Page 5: Ownership—copyright year, holder name, and license type
- Page 6: Features—checkboxes for search, RSS, comments, sitemap, and analytics
- Page 7: Design—layout style, sidebar position, breadcrumbs, and footer toggles
- Page 8: Summary—read-only review of all settings with a Generate button
The application builds without errors. The Frame manages all pages and
Back/Next navigation. A status bar at the bottom of the frame displays the current
NamtiraLib version.
Platform-Wide Rename: Organica → Namtira
The entire Namtira platform was renamed from "Organica" to "Namtira" after the
organica.com domain was found to be held by a cybersquatter. Every occurrence
of the old name was updated: folder names, file names, namespaces, project names,
assembly names, code, and prose content across all projects and the website.
Scope of changes:
- Projects folder reorganized to Projects/(Namtira)/ with all sub-projects renamed
- 24 Namtira.ini navigation files renamed from the old name
- All NamtiraAudio.js script references updated site-wide
- All internal .vbproj references updated to the new paths and names
- All prose documentation on the site updated throughout the Namtira section
A blanket 301 redirect was added to Global.asax.vb: any incoming URL containing
"Organica" (but not already "Namtira") is redirected to the corrected URL via
Regex.Replace, preserving deep links from any old bookmarks or external
references.
Namtira Platform Naming
The umbrella name "OrganicaWeb" was retired. The full platform is now called
Namtira, consisting of three components: NamtiraWeb (the web
framework, currently active), NamtiraExplorer, and NamtiraDesktop.
NamtiraMyWeb is the creation and migration wizard for NamtiraWeb sites.
Namtira Landing Site
A new bare-minimum ASP.NET 4.8 web project was created at
Desktop 3/Websites/Namtira/ as a target for testing NamtiraMyWeb.
It consists of a single HTML landing page explaining the Namtira platform and the
name change from Organica, a Visual Studio solution file, and a .vbproj
matching the NamtiraWeb project structure. Publishing configuration was copied
from NamtiraWeb.
NamtiraLib Distribution Packages
Two downloadable zip archives were added to the NamtiraLib Getting Started page:
NamtiraLib-Source.zip (the full Visual Studio solution) and
NamtiraLib-Compiled.zip (just the DLL and debug symbols). The page includes
browser security warning guidance for each platform and step-by-step extraction
instructions.
Automatic Site Version Numbering
A new GetLibraryVersion() function was added to NamtiraLib, returning
the last-modified timestamp of the compiled assembly as a yyyy.MM.dd string.
The NamtiraLib Test Bed displays this in a status bar at the bottom of its main
window.
The SiteVersion constant in Site.Master.vb was replaced with a
read-only property that reads the last-write timestamp of the site's own compiled
assembly—updating automatically on every publish without any manual version
bump.
The NamtiraLib DLL cannot be directly referenced by a .NET Framework 4.8 web
application because NamtiraLib targets .NET 10. The shared utility
code—NamtiraDates.vb, NamtiraFiles.vb, and
NamtiraStrings.vb—is instead compiled directly into the site by
linking the source files in the project file.
Section CSS Cascade
A new GenerateSectionCSS() function was added to Site.Master.vb.
On every page request it walks up from the current page's directory to the site root,
collecting every Customize.css file found along the way. All matches are
emitted as cache-busted <link> tags in the <head>,
ordered from root to leaf so deeper files cascade over shallower ones.
This allows any section of the site to have its own visual identity—custom banner,
colors, fonts, or layout—simply by dropping a Customize.css into that
folder. Subsections can further refine the look by adding their own. Pages with no
ancestor Customize.css are unaffected. The first use of this feature is
Contents/Computers/35.Namtira/Customize.css, which applies a custom
background and banner image to the entire Namtira section.