doc:wrap

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
doc:wrap [2026/04/04 19:14] – [Used on the site already] Simon Grantdoc:wrap [2026/08/19 00:24] (current) – external edit 127.0.0.1
Line 5: Line 5:
 //Try out all these techniques below in the [[playground:playground]].// //Try out all these techniques below in the [[playground:playground]].//
  
-What WRAP is doing is essentially importing some HTML functionality (and as you might also see, following HTML syntax) for a few things that aren't easy in a [[wp>lightweight markup language]] (LML). This kind of thing is a common feature of wikis and related systems. HTML is, for sure, more complex and less straightforward than a LML, but much much richer in what it can do. So many wiki systems allow embedding of HTML in one way or another. +What WRAP does is essentially sneaking in some HTML functionality (and as you might also see, following HTML syntax) for a few things that aren't easy in a [[wp>lightweight markup language]] (LML). This kind of thing is a common feature of wikis and related systems. HTML is, for sure, more complex and less straightforward than a LML, but much much richer in what it can do. So many wiki systems allow embedding of HTML in one way or another. 
  
 It's part of the same challenge that people have been struggling with for decades. How do you give people control over what's in a document and how it appears, without making it too difficult to write, edit, or code? Some people these days say AI is the way to go — personally I'm not so sure; I prefer the idea of people supporting each other to learn the skills they need, in a learning commons ^_^ It's part of the same challenge that people have been struggling with for decades. How do you give people control over what's in a document and how it appears, without making it too difficult to write, edit, or code? Some people these days say AI is the way to go — personally I'm not so sure; I prefer the idea of people supporting each other to learn the skills they need, in a learning commons ^_^
Line 27: Line 27:
 <WRAP center centeralign>  <WRAP center centeralign> 
 <figure> <figure>
-{{url>https://www.youtube.com/embed/7bQiBcd7mBc 560,315}}+{{url>https://www.youtube.com/embed/7bQiBcd7mBc}}
 <caption> <caption>
 _How does the commons work? From the [Next System Project](https://thenextsystem.org/)._ _How does the commons work? From the [Next System Project](https://thenextsystem.org/)._
Line 38: Line 38:
 <WRAP center centeralign>  <WRAP center centeralign> 
 <figure> <figure>
-{{url>https://www.youtube.com/embed/7bQiBcd7mBc 560,315}}+{{url>https://www.youtube.com/embed/7bQiBcd7mBc}}
 <caption> <caption>
 _How does the commons work? From the [Next System Project](https://thenextsystem.org/)._ _How does the commons work? From the [Next System Project](https://thenextsystem.org/)._
Line 45: Line 45:
 </WRAP> </WRAP>
  
-This illustrates centering and captions, as well as an embedded video. It's essentially the same with still images.+The above illustrates centering and captions, as well as an embedded video.  
 + 
 +It's essentially the same with still images, as reproduced below.
 Here we have used Markdown syntax.  Here we have used Markdown syntax. 
  
Line 71: Line 73:
 ---- ----
  
-There are many many more examples on almost every topic page. You get the general idea — you can always look at the lightweight markup language on each page, even if you don'have permission to edit it.+There are many many more examples on almost every topic page. You get the general idea — you can always look at the lightweight markup language on any page that you have permission to edit.
  
 ===== See also ===== ===== See also =====
  • doc/wrap.1775330056.txt.gz
  • Last modified: 2026/07/23 08:54
  • (external edit)