TYPO3's Built-in Rich Text Editor
TYPO3 ships with the CKEditor (ckeditor.com) as there sophisticated built-in rich text editor (RTE). This editor contains all of the features one would expect from an Enterprise CMS, and is highly configurable and extendable to fit every project out there.
Multicolumns
The most significant things we can think about, when we think about Apollo, is that it has opened for us, for us being the World, a challenge of the future. The door is now cracked, but the promise of that future lies in the young people, not just in America, but the young people all over the world. Learning to live and learning to work together. In order to remind all the peoples of the World, in so many countries throughout the world, that this is what we all are striving for in the future, Jack has picked up a very significant rock, typical of what we have here in the valley of Taurus Littrow.
It's a rock composed of many fragments, of many sizes, and many shapes, probably from all parts of the Moon, perhaps billions of years old. But a rock of all sizes and shapes, fragments of all sizes and shapes, and even colors that have grown together to become a cohesive rock outlasting the nature of Space, sort of living together in a very coherent, very peaceful manner. When we return this rock or some of the others like it to Houston, we'd like to share a piece of this rock with so many of the countries throughout the world. We hope that this will be a symbol of what our feelings are, what the feelings of the Apollo Program are, and a symbol of mankind that we can live in peace and harmony in the future.
Examples of Rich Text Content Elements
Continuous text: text, optional in bold.
Special characters can be used: @ © ® ¢ ¼ ½ ¾ § ± a² m³ Ω π µ γ β α H2O
Text alignment
Centered text
Text justified right
Blockquote
Spaceflight will never tolerate carelessness, incapacity, and neglect. Somewhere, somehow, we screwed up. It could have been in design, build, or test. Whatever it was, we should have caught it. We were too gung ho about the schedule and we locked out all of the problems we saw each day in our work.
Every element of the program was in trouble and so were we. The simulators were not working, Mission Control was behind in virtually every area, and the flight and test procedures changed daily. Nothing we did had any shelf life. Not one of us stood up and said, ‘Dammit, stop!’ I don’t know what Thompson’s committee will find as the cause, but I know what I find. We are the cause! We were not ready! We did not do our job. We were rolling the dice, hoping that things would come together by launch day, when in our hearts we knew it would take a miracle. We were pushing the schedule and betting that the Cape would slip before we did.
Spaceflight will never tolerate carelessness, incapacity, and neglect. Somewhere, somehow, we screwed up. It could have been in design, build, or test. Whatever it was, we should have caught it. We were too gung ho about the schedule and we locked out all of the problems we saw each day in our work.
Lists
Bulleted list:
- first level
- first level
- second level
- second level
- third level
- third level
Ordered list:
- first level
- first level
- second level
- second level
- third level
- third level
Tables
| # | FirstName | LastName | Username |
|---|---|---|---|
| 1 | Benjamin | Kott | @benjaminkott |
| 2 | John | Doe | - |
| 3 | Larry | the Bird |
Address
John Doe
Street 42
Zip & City
Telephone: +49 1234 456-7890
Fax: +49 1234 456-7891
Email: john.doe@example.com