I agree, the menu looks good - the search bar in particular is helpful. The content layout for each release (I see that you've filled out them all now) makes sense to me.
On Mon, Jul 27, 2020 at 11:16 AM Thomas Andraschko < [email protected]> wrote: > *quite good > > Am Mo., 27. Juli 2020 um 17:11 Uhr schrieb Thomas Andraschko < > [email protected]>: > >> Please checkout Core and 2.2 again :) >> I added all context params by modifying the WebContextParamsLogger >> >> I think also the menu structure is quite now. >> >> Am Mo., 27. Juli 2020 um 15:10 Uhr schrieb Paul Nicolucci < >> [email protected]>: >> >>> +1 for the link to javadoc.io, I think that would actually work very >>> nicely. >>> >>> Regards, >>> >>> Paul Nicolucci >>> >>> On Mon, Jul 27, 2020 at 8:59 AM Thomas Andraschko < >>> [email protected]> wrote: >>> >>>> Hi, >>>> >>>> i think we could still host the javadoc by ourself if we want. We can >>>> just generate the javadoc html (without the other site stuff) + copy it in >>>> a subfolder of the homepage. >>>> But in general i would i add a link to: https://javadoc.io/ >>>> >>>> WDYT? >>>> >>>> Best regards, >>>> Thomas >>>> >>>> >>>> Am Mo., 27. Juli 2020 um 14:42 Uhr schrieb Paul Nicolucci < >>>> [email protected]>: >>>> >>>>> Hi, >>>>> >>>>> Having had to update the site recently a few times I like the idea of >>>>> making this easier to do. >>>>> >>>>> One thing that comes to mind is would we still be able to generate and >>>>> deploy the docs? For example: >>>>> https://myfaces.apache.org/core23/javadoc.html >>>>> >>>>> Thanks, >>>>> >>>>> Paul Nicolucci >>>>> >>>>> On Mon, Jul 27, 2020 at 8:31 AM Bill Lucy <[email protected]> wrote: >>>>> >>>>>> I'm absolutely in favor of updating the site if we can improve the >>>>>> ease of maintainability. The current site has a lot of stale information >>>>>> which would be nice to update or get rid of. Markdown is great for >>>>>> lowering the barrier to making updates - I like the example you've come >>>>>> up >>>>>> with. I think losing the automatic context param configuration doc >>>>>> generation is a small downside - it won't be difficult to add the >>>>>> markdown >>>>>> for a new param in the rare event that we create a new one. >>>>>> >>>>>> Overall +1 from me for overhauling the site. I like the format of >>>>>> what you've gotten started with. >>>>>> >>>>>> Regards, >>>>>> Bill >>>>>> >>>>>> On Mon, Jul 27, 2020 at 5:21 AM Thomas Andraschko < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> up ;) >>>>>>> >>>>>>> Am Mi., 22. Juli 2020 um 14:48 Uhr schrieb Thomas Andraschko < >>>>>>> [email protected]>: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> as you all know, the MyFaces homepage is very old. I also tried to >>>>>>>> get the site plugin running for Core 2.3-next but i didn't get it >>>>>>>> working. >>>>>>>> >>>>>>>> I really would like to get rid of the whole maven generation site >>>>>>>> and just a something MUCH easier like asciidoctor or markdown. >>>>>>>> >>>>>>>> I setup something here: >>>>>>>> https://github.com/tandraschko/myfaces-homepage >>>>>>>> Preview: >>>>>>>> https://raw.githack.com/tandraschko/myfaces-homepage/master/ >>>>>>>> >>>>>>>> It uses markdown and docsify! This makes the maintenance very very >>>>>>>> easy for the future. >>>>>>>> >>>>>>>> What needs to be done: >>>>>>>> - Transfer content >>>>>>>> - Styling >>>>>>>> >>>>>>>> Whats the downside of it? >>>>>>>> We cant use our maven plugins to generate the "context param >>>>>>>> config" page, it needs to be done manually. >>>>>>>> >>>>>>>> WDYT? >>>>>>>> >>>>>>>> Best regards, >>>>>>>> Thomas >>>>>>>> >>>>>>>
