PHPackages itplusx/flexible-news - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. itplusx/flexible-news ActiveTypo3-cms-extension[Utility & Helpers](/categories/utility) itplusx/flexible-news ===================== Flexible news extension to use pages as news articles v2.0.0(4y ago)061MITHTML Since Aug 14Pushed 4y ago2 watchersCompare [ Source](https://github.com/itplusx/flexible_news)[ Packagist](https://packagist.org/packages/itplusx/flexible-news)[ Docs](https://itplusx.de)[ RSS](/packages/itplusx-flexible-news/feed)WikiDiscussions main Synced today READMEChangelog (5)Dependencies (2)Versions (6)Used By (0) [ ![TYPO3 EXT:flexible_news](https://raw.githubusercontent.com/itplusx/flexible_news/master/Resources/Public/Icons/Logo.png) ](https://github.com/itplusx/flexible_news) TYPO3 Extension `flexible_news` =============================== [](#typo3-extension-flexible_news) [![License: MIT](https://camo.githubusercontent.com/fdf2982b9f5d7489dcf44570e714e3a15fce6253e0cc6b5aa61a075aac2ff71b/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f4c6963656e73652d4d49542d79656c6c6f772e737667)](https://opensource.org/licenses/MIT) Create **news articles based on normal pages** in TYPO3 and display them as a list in the frontend. Using pages instead of records has the following advantages: - **No extra TCA required** Since this extension uses the default pages of TYPO3 and it's TCA fields, it's not necessary to have extra TCA field declarations. (unless you need additional fields) - **No extra database tables** This extension only uses the `pages` table and therefore no extra tables are needed. This prevents bloating the database with additional tables and fields. - **No `routeEnhancers` hassle** The url of the news article will be representing the page tree and will work out of the box. No need to add `routeEnhancers`. The slug of every article can be changed with the `slug` field and is not bound to the article title. - **Construct flexible articles with available content elements without being bound to a pre-defined markup** When using records as news articles the markup for every article is pre-defined in the templates. While with pages as news, every article can be build differently with content elements without being bound to a fixed template. This extension utilizes [EXT:flexible\_pages](https://github.com/itplusx/flexible_pages) to create a custom "News" pageType and a template for the list content element. Installation ------------ [](#installation) ### Extension installation [](#extension-installation) #### Installation with [`composer`](https://getcomposer.org/) (recommended) [](#installation-with-composer-recommended) ``` composer require itplusx/flexible_news ``` #### Installation with the [TYPO3 Extension Manager](https://docs.typo3.org/typo3cms/GettingStartedTutorial/ExtensionManager/Index.html#installing-a-new-extension) [](#installation-with-the-typo3-extension-manager) Use the Extension Key `flexible_news` in the [TYPO3 Extension Manager](https://docs.typo3.org/m/typo3/guide-installation/master/en-us/ExtensionInstallation/Index.html#extension-installation). **NOTE: This extension requires [EXT:flexible\_pages](https://github.com/itplusx/flexible_pages) to be installed.** ### Include TypoScript [](#include-typoscript) #### Base TypoScript [](#base-typoscript) After a successful install just [include the TypoScript](https://docs.typo3.org/m/typo3/reference-typoscript/master/en-us/UsingSetting/Entering.html#include-typoscript-files)for the News List CE and you are all set. #### CSS TypoScript (optional) [](#css-typoscript-optional) If you want to use the CSS for the News List CE that is shipped with this extension you have to include the *Flexible News CSS (optional)* TypoScript as well. Usage ----- [](#usage) When everything is installed correctly you should see a new page icon above your page tree in the TYPO3 backend. From there you could just pull it down into the page tree like with every other page. **NOTE: If you don't see that icon at first, try to clear the cache and reload the entire page.** ### List View [](#list-view) You can add the *"Pages of selected doktypes"* content element to every page to render a list of articles by doktype in the frontend. The content element already comes with a "News" template to render the list accordingly. #### Override List Template [](#override-list-template) You can override the List CE template. To do that you have to extend the FLUIDTEMPLATE rootPaths. You can either do this in your own extension by extending the `lib.contentElement` TypoScript (as described [HERE](https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/ApiOverview/ContentElements/AddingYourOwnContentElements.html#configure-the-frontend-template)) or you could use the constants provided by flexible\_news: - `plugin.tx_flexiblenews.templateRootPath` - `plugin.tx_flexiblenews.partialRootPath` - `plugin.tx_flexiblenews.layoutRootPath` #### Extend List Templates [](#extend-list-templates) When more News List Templates are required (e.g News List without images) the template select can be extended. Please have a look at the documentation of [EXT:flexible\_pages](https://github.com/itplusx/flexible_pages) or see [how it's done in flexible\_news for the "News" template](https://github.com/itplusx/flexible_news/blob/master/ext_localconf.php). ### Detail View [](#detail-view) The detail view is just a view of the page (with the default page template). However sometimes it might be quite useful to have a special page template for just the news articles (e.g to show specific content on every news article). #### Adding News Article Page Template [](#adding-news-article-page-template) Assuming you want to add social media share buttons to every news article you have to do the following. - Add TypoScript for special dokType to override FLUIDTEMPLATE: ``` [page["doktype"] == 87] page.10 { templateName > templateName = News variables { socialMediaShare =< lib.socialMediaShare } } [GLOBAL] ``` - Add the previously defined variable to the template file wherever the share buttons should appear: `{socialMediaShare}` Contribution ------------ [](#contribution) Any help on this project is very welcome! May it be as code contribution or just an idea for improvement. But we would like to ask you to follow some rules: - **Issues:** When adding issues please always describe the bug/feature/task as detailed as possible. Only providing a title is not enough. Please use issue templates. - **Commits:** Our team is following the [Conventional Commits](https://www.conventionalcommits.org/). We would like ask you stick to these rules whenever you want to contribute. - **Pull Requests:** Before you submit a PR please create an issue first and link it to the pull request or at least add a PR description with detailed information about what this PR does. Otherwise we are not able to decide if this PR is worth going into the main branch. --- [ ![ITplusX - Internetagentur & Systemhaus](https://camo.githubusercontent.com/14e12de38879bb59be4344f31f58fc5bc6e048280cb75884751c46491af79afa/68747470733a2f2f6974706c7573782e64652f62616e6e6572732f637265617465642d62792d582d776974682d70617373696f6e2e737667) ](https://itplusx.de) --- ### Health Score 27 — LowBetter than 47% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity8 Limited adoption so far Community11 Small or concentrated contributor base Maturity59 Maturing project, gaining track record Bus Factor1 Top contributor holds 95.2% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~114 days Total 5 Last Release 1691d ago Major Versions v1.0.3 → v2.0.02021-11-15 ### Community Maintainers ![](https://avatars.githubusercontent.com/u/13196174?v=4)[Ramón](/maintainers/schloram)[@schloram](https://github.com/schloram) ![](https://www.gravatar.com/avatar/2969ab0a2fbae7ce85cc02be57237e3c99ba41c1e748c23aa710bab18f6a3417?d=identicon)[vjanoch](/maintainers/vjanoch) --- Top Contributors [![schloram](https://avatars.githubusercontent.com/u/13196174?v=4)](https://github.com/schloram "schloram (20 commits)")[![vacijj](https://avatars.githubusercontent.com/u/2101914?v=4)](https://github.com/vacijj "vacijj (1 commits)") --- Tags typo3extension newsTYPO3 CMStypo3pages as news ### Embed Badge ![Health badge](/badges/itplusx-flexible-news/health.svg) ``` [![Health](https://phpackages.com/badges/itplusx-flexible-news/health.svg)](https://phpackages.com/packages/itplusx-flexible-news) ``` ### Alternatives [georgringer/news News system - Versatile news system based on Extbase & Fluid and using the latest technologies provided by TYPO3 CMS. 2985.3M123](/packages/georgringer-news)[friendsoftypo3/visual-editor TYPO3 CMS Visual Editor - Brings a modern WYSIWYG editing experience to TYPO3 CMS. 576.1k2](/packages/friendsoftypo3-visual-editor)[wazum/sluggi TYPO3 extension for URL slug management with inline editing, auto-sync, locking, access control, and redirects 40529.5k](/packages/wazum-sluggi)[georgringer/eventnews Extend EXT:news with event and calendar functionality 31626.5k4](/packages/georgringer-eventnews)[jweiland/events2 Events 2 - Create single and recurring events 2166.7k3](/packages/jweiland-events2)[rupertgermann/tt_news News - Website news with front page teasers and article handling inside. 2256.1k](/packages/rupertgermann-tt-news) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)