{"action":"created","issue":{"url":"https://api.github.com/repos/OrchardCMS/Orchard/issues/6061","labels_url":"https://api.github.com/repos/OrchardCMS/Orchard/issues/6061/labels{/name}","comments_url":"https://api.github.com/repos/OrchardCMS/Orchard/issues/6061/comments","events_url":"https://api.github.com/repos/OrchardCMS/Orchard/issues/6061/events","html_url":"https://github.com/OrchardCMS/Orchard/issues/6061","id":118193303,"number":6061,"title":"There should be a default startup recipe without LayoutParts","user":{"login":"CSurieux","id":2103534,"avatar_url":"https://avatars.githubusercontent.com/u/2103534?v=3","gravatar_id":"","url":"https://api.github.com/users/CSurieux","html_url":"https://github.com/CSurieux","followers_url":"https://api.github.com/users/CSurieux/followers","following_url":"https://api.github.com/users/CSurieux/following{/other_user}","gists_url":"https://api.github.com/users/CSurieux/gists{/gist_id}","starred_url":"https://api.github.com/users/CSurieux/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/CSurieux/subscriptions","organizations_url":"https://api.github.com/users/CSurieux/orgs","repos_url":"https://api.github.com/users/CSurieux/repos","events_url":"https://api.github.com/users/CSurieux/events{/privacy}","received_events_url":"https://api.github.com/users/CSurieux/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-11-21T12:21:39Z","updated_at":"2015-11-21T19:03:19Z","closed_at":null,"body":"Layout parts are a great dev but I am not satisfied with it and I would prefer to be able to install Orchard without them everywhere: pages with body, etc.\r\nThe all drag and drop is not efficient for the kind of sites I build, I prefer being able to select my display type and write my shapes in my theme, to use alternates and wrappers and to use VS text editor to write my own razor/html with direct control, also because TinyMCE is still bogus with html - and it is not something easy to fix - and offers a very poor editor experience.\r\n\r\nMoreover the source code gets overcomplicated by layoutPart and special drivers constraints.\r\n\r\nI am not satisfied with the actual tendency/decision to put Layout Parts everywhere. Even if I know that the people behind this are solid dev and bringing huge effort to reach a stable version.\r\nI would appreciate to have layout parts totally swtchable.\r\n\r\nEDIT: this effort reminds me the start of asp.net webforms with all the custom controls: we were dragging them in a design view and spending lot of time to create our own custom controls (I remember the fabulous book made by this guy, Nikhil Khotari, now at Google's). I don't need all these elements as a mediation layer between html /css and me. This seems an outdated concept overcomplicating everything. I think Orchard is not taking the good direction. Using a part to drive layout is not good. My opinion. May be some others share it."},"comment":{"url":"https://api.github.com/repos/OrchardCMS/Orchard/issues/comments/158672675","html_url":"https://github.com/OrchardCMS/Orchard/issues/6061#issuecomment-158672675","issue_url":"https://api.github.com/repos/OrchardCMS/Orchard/issues/6061","id":158672675,"user":{"login":"sebastienros","id":1165805,"avatar_url":"https://avatars.githubusercontent.com/u/1165805?v=3","gravatar_id":"","url":"https://api.github.com/users/sebastienros","html_url":"https://github.com/sebastienros","followers_url":"https://api.github.com/users/sebastienros/followers","following_url":"https://api.github.com/users/sebastienros/following{/other_user}","gists_url":"https://api.github.com/users/sebastienros/gists{/gist_id}","starred_url":"https://api.github.com/users/sebastienros/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sebastienros/subscriptions","organizations_url":"https://api.github.com/users/sebastienros/orgs","repos_url":"https://api.github.com/users/sebastienros/repos","events_url":"https://api.github.com/users/sebastienros/events{/privacy}","received_events_url":"https://api.github.com/users/sebastienros/received_events","type":"User","site_admin":false},"created_at":"2015-11-21T19:03:19Z","updated_at":"2015-11-21T19:03:19Z","body":"The Layout Part is only added to Page by default, and Page itself is really that, a routable content representing some placed content, for which Layouts is the best fit. So your issue is just that you shouldn't use Page but create some specific content type with something else than Layout Part. The default configuration fits most web dev, and __it's up to you to delete this content type, create the one you want, with the parts you want__, and even define it as the default recipe. \r\n\r\nA single default recipe cannot suit everyone's needs, but still there is a single default recipe. There is absolutely no magical way to suit everyone's need but what we have done, making it completely configurable so everyone can customize it and make their own defaults.\r\n\r\n> Moreover the source code gets overcomplicated by layoutPart and special drivers constraints.\r\n\r\nYou don't have to use Layout Parts or elements if you don't want to. Nothing is forcing you, it's still a module that can be disabled and ignored.\r\n\r\nI will ask the question at the next meeting, who wants Layout by default on Pages, or BodyPart by default on Page. Though I think we already had this discussion which led into the current configuration."}}