Skip to content

Instantly share code, notes, and snippets.

@dcomartin
Created April 7, 2021 22:08
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save dcomartin/a18af85940785a001556a46b52477961 to your computer and use it in GitHub Desktop.
Save dcomartin/a18af85940785a001556a46b52477961 to your computer and use it in GitHub Desktop.
<form method="post" action="/mvc/save?Sku=abc123">
<div class="mb-3">
<label class="form-label">SKU</label>
<div class="row">
<label class="form-label"><strong><a href="/mvc/images?Sku=abc123">abc123</a></strong></label>
</div>
</div>
<div class="mb-3">
<label class="form-label">Name</label>
<input name="name" type="text" class="form-control" value="Domain-Driven Design: Tackling Complexity in the Heart of Software">
</div>
<div class="mb-3">
<label class="form-label">Description</label>
<textarea name="description" class="form-control">Leading software designers have recognized domain modeling and design as critical topics for at least twenty years, yet surprisingly little has been written about what needs to be done or how to do it. Although it has never been clearly formulated, a philosophy has developed as an undercurrent in the object community, which I call domain-driven design.</textarea>
</div>
<button type="submit" class="btn btn-primary">Save Product Info</button>
</form>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment