Description: It would be nice to have the ability to link a bootstrap file to a document. And to have the option "Web Page" under File and in the Startcenter. And automatic use ".html" as default if working in Web Mode in Writer (not .odt). In short, more real single web-page edit features to edit single responsive webpages. Steps to Reproduce: There is a need to make single web pages. I know (and use) there are other tools for this. But this would be really nice for making LO the goto tool for all offline working. Actual Results: Produce better looking web pages with a consistency among the pages. Expected Results: More use off LO to make small static websites. Reproducible: Always User Profile Reset: No Additional Info: ==
Valid, but would not expect too much traction for this.
We have to consider that Google Workspace, has Sites. And Microsoft 365, SharePoint.
Why would we need to make LibreOffice a HTML editor, again? We provide an office suite and should focus on this functionality. For example we removed the HTML wizard for bug 105303 / bug 99967. But perhaps I got the request wrong. Microsoft SharePoint is about "Share and manage content, knowledge, and applications to empower teamwork, quickly find information, and seamlessly collaborate across the organization." and "Google Sites is a structured wiki and web page creation tool included as part of the free, web-based Google Docs Editors suite offered by Google." Can you elaborate on your workflow and find arguments why the feature is relevant for many users?
Heiko is probably right. Or you abandon the HTML export and HTML-open functionality, or you do a proper HTML static page editor job.
[Automated Action] NeedInfo-To-Unconfirmed
(In reply to Boudi from comment #4) > Heiko is probably right. So let's close the ticket. Unless you completely disagree and want to other users to comment on your idea.
Heiko, I have been Service Manager and Change Manager in projects. So I do understand your desire to close the ticket. But where do we have the strategic conversations? e.i. talks about functionality in relation with the market? Where do we collect functional opportunities from users other than copying the leading Office Suite suppliers? There are other projects (open source and closed source) having feed back collection separated from the ticket management.
(In reply to Boudi from comment #7) > But where do we have the strategic conversations? We have weekly design/UX meetings where I pick topics to discuss (me being "UX mentor" in the project with the task to support volunteers). If you want, I can add your idea and ask more people (and you are welcome to join the meeting, of course; the meeting is alternating on Wednesday 7pm or Thursday 1pm UTC). Besides, LibreOffice has a weekly call of the engineering steering committee (ESC). As an open source project we don't have strong strategic goals as known from business entities. Sure, you can pay for features. But other than that it's up to volunteers to implement ideas. As a more general note, requests become more striking if the idea is clear. A replicable use case, steps to reproduce, hurdles to manage, etc. make enhancement requests more convincing. In this particular case I struggle with the basic idea of advanced handling HTML in an office suite.
(In reply to Heiko Tietze from comment #8) > (In reply to Boudi from comment #7) > > But where do we have the strategic conversations? > We have weekly design/UX meetings where I pick topics to discuss (me being > "UX mentor" in the project with the task to support volunteers). If you > want, I can add your idea and ask more people (and you are welcome to join > the meeting, of course; the meeting is alternating on Wednesday 7pm or > Thursday 1pm UTC). > > Besides, LibreOffice has a weekly call of the engineering steering committee > (ESC). As an open source project we don't have strong strategic goals as > known from business entities. Sure, you can pay for features. But other than > that it's up to volunteers to implement ideas. > > As a more general note, requests become more striking if the idea is clear. > A replicable use case, steps to reproduce, hurdles to manage, etc. make > enhancement requests more convincing. In this particular case I struggle > with the basic idea of advanced handling HTML in an office suite. Hi Heiko, I do understand that you are struggling with the basic idea of advanced handling HTML. But currently it is neither fish nor fowl. What use case is really served by the current HTML functionality? If the use case is to publish in HTML it is not sufficient because far outdated. That was basically what I tried to get across. My examples (Sites / SharePoint) are out of the development scope, I understand. And also not really needed, I think. My suggestion is at least to include a linked bootstrap.css file in the published HTML (Save As) so that the HTML result at least looks the same as the source in LibreOffice. On the strategy part of our conversation. I notice that if I follow the Website to Enhancement requests (https://www.libreoffice.org/get-help/feedback/) I end up in a change request. My suggestion is to collect enhancement ideas from users in a separate bucked. I would like to contribute more to the team, but have too much add hand currently. My first thing is to be able to attend a future gathering to learn to know you all. Thanks for your time.